-
Notifications
You must be signed in to change notification settings - Fork 635
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
don't execute the setup method for NodeManipulatorExtensionTests tests twice #15768
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -28,7 +28,7 @@ protected override IEnumerable<IGizmo> GetGizmos(bool createOrUpdate) | |
public class NodeManipulatorExtensionTests : DynamoTestUIBase | ||
{ | ||
[SetUp] | ||
public virtual void Start() | ||
public override void Start() | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nice!. DId you try to turn on the dispatrcher ops waiting after this change ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I did not, will give it a shot, were you able to repro the helix crash locally? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. on second thought, there's no reason for this method to exist if we're flushing the dispatcher. Also, I think theres something weird with the way we increment the dispatcher ops when this flag is true... There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I did manage to reproduce the crash locally |
||
{ | ||
// Forcing the dispatcher to execute all of its tasks within these tests causes crashes in Helix. | ||
// For now just skip it. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we remove the handler only after the DoEventsLoop ?
I wonder if operations can still post other operations..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
interesting...