-
Notifications
You must be signed in to change notification settings - Fork 5k
[browser] Expanding timeouts for long running test projects #85313
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
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 |
---|---|---|
|
@@ -231,6 +231,14 @@ | |
<PayloadArchive>%(Identity)</PayloadArchive> | ||
<Command>$(HelixCommand)</Command> | ||
<Timeout>$(_workItemTimeout)</Timeout> | ||
<!-- | ||
These WASM tests are problematic and slow right now, in this section it's about nodejs and chrome. | ||
Below is same section for V8. There is also Xharness timeout override in the test project. | ||
--> | ||
<Timeout Condition="'%(FileName)' == 'System.Text.Json.Tests'">01:20:00</Timeout> | ||
<Timeout Condition="'%(FileName)' == 'System.Collections.Immutable.Tests'">01:20:00</Timeout> | ||
<Timeout Condition="'%(FileName)' == 'System.Net.WebSockets.Client.Tests'">01:20:00</Timeout> | ||
<Timeout Condition="'%(FileName)' == 'System.Net.Http.Functional.Tests'">01:20:00</Timeout> | ||
Comment on lines
+238
to
+241
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 is this needed? A lot of work was done here to separate the project specific from these helix targets. And more is coming. 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. These specific projects needs extended timeout, at least at the moment. Do we have other options? Or should we extend the timeout to all jobs? 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. hmm keep this here for now. I will move the whole thing out for library tests. 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. The problem is that here we don't have individual projects loaded in MSBuild, we only have zip files in folders. |
||
</HelixWorkItem> | ||
</ItemGroup> | ||
|
||
|
@@ -253,7 +261,13 @@ | |
<PayloadArchive>%(Identity)</PayloadArchive> | ||
<Command>$(HelixCommand)</Command> | ||
<Timeout>$(_workItemTimeout)</Timeout> | ||
<!-- These WASM tests are problematic and slow right now, in this section it's about V8. Above is same section for nodejs and chrome --> | ||
<Timeout Condition="'%(FileName)' == 'System.Text.Json.Tests'">01:20:00</Timeout> | ||
<Timeout Condition="'%(FileName)' == 'System.Collections.Immutable.Tests'">01:20:00</Timeout> | ||
<Timeout Condition="'%(FileName)' == 'System.Net.WebSockets.Client.Tests'">01:20:00</Timeout> | ||
<Timeout Condition="'%(FileName)' == 'System.Net.Http.Functional.Tests'">01:20:00</Timeout> | ||
</HelixWorkItem> | ||
|
||
</ItemGroup> | ||
</Target> | ||
|
||
|
Uh oh!
There was an error while loading. Please reload this page.