-
Notifications
You must be signed in to change notification settings - Fork 26
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
Debug hangs in CI #423
Debug hangs in CI #423
Changes from 4 commits
5dae14a
0588bc0
38ee164
ba4156e
c0b50f6
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 |
---|---|---|
|
@@ -109,7 +109,7 @@ async Task RunAsync() | |
|
||
var tests = new List<(string, Task)>(); | ||
|
||
foreach ((string name, Task task) in scenarios.StartAllScenarios(includeTimers: true, includeLarge: true)) | ||
foreach ((string name, Task task) in scenarios.StartAllScenarios(includeTimers: false, includeLarge: 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. why did 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 saw timer tests failing spuriously (because of large time delays leading to unexpected results) so I did not think it was worth keeping them in there. 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. If I understand correctly, you're seeing that timers make creating a testing spec difficult (as in it's difficult to assert what exactly will happen when). Ok, that makes sense |
||
{ | ||
Trace.WriteLine($"TestProgress: Adding {name}"); | ||
tests.Add((name, task)); | ||
|
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.
I think this is a good place to elaborate a bit more on the significance of
src.Val
being null. Is this a bug in FASTER, or expected, or something else? Can you please add a small blurb about that here?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.
That's sort of what the comment on line 2084 is supposed to be.
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.
I'm not sure that gives me enough context though. The way the comment is phrased ("we have observed...sometimes") makes me thing it is not expected that
src.Val
would be null, and if that's true then I think that's worth calling out explicitly. It would tell me whether or not there's something weird that FASTER is doing hereThere 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.
Yeah I actually also don't know. I can add a bit more text to say more explicitly that I don't really know what is supposed to be happening.