Extend Timeout of Regressions Again #15580
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Core nightly testing is facing a timeout issue.
Right now. We have the following:
Which means that the
core
regression tests are just running longer and longer as we move more packages to track 2.Couple of things we can do here:
core
into each service folder. If you take a dep on core, you will get a core regression test.Or some other combination. Either way, let's get the immediate concern out of the way.