Separate Helix and XHarness testing#8255
Merged
michellemcdaniel merged 4 commits intodotnet:mainfrom Dec 10, 2021
Merged
Conversation
There are frequently intermittent failures in the XHarness testing that need to be retried due to timeouts or xharness flakiness. Because the XHarness tests are in the same job as the regular helix tests, we have rerun all of the testing just to rerun the xharness tests. This wastes resources and is frustrating for devs. This change splits out the xharness tests into their own jobs so that when xharness reruns need to happen, we only have to rerun the xharness legs.
Member
|
This looks great but if you're willing, we could separate it even more, since "XHarness Apple Simulator Helix Testing", "XHarness Apple Device Helix Testing", and "XHarness Android Helix Testing (Linux)" are independent. |
MattGal
approved these changes
Dec 10, 2021
1 task
MattGal
added a commit
to MattGal/arcade
that referenced
this pull request
Jul 5, 2022
* Separate Helix and XHarness testing There are frequently intermittent failures in the XHarness testing that need to be retried due to timeouts or xharness flakiness. Because the XHarness tests are in the same job as the regular helix tests, we have rerun all of the testing just to rerun the xharness tests. This wastes resources and is frustrating for devs. This change splits out the xharness tests into their own jobs so that when xharness reruns need to happen, we only have to rerun the xharness legs. * Fix publishing logs * And there * Fix yaml syntax, separate even further
MattGal
added a commit
that referenced
this pull request
Jul 6, 2022
* Remove (EOL 6/30/2022) Debian 9 usage. * Add FailOnMissingTargetQueue property usage so we can only fail when we have <1 queue to send to. * Cherry pick: Separate Helix and XHarness testing (#8255) * Separate Helix and XHarness testing There are frequently intermittent failures in the XHarness testing that need to be retried due to timeouts or xharness flakiness. Because the XHarness tests are in the same job as the regular helix tests, we have rerun all of the testing just to rerun the xharness tests. This wastes resources and is frustrating for devs. This change splits out the xharness tests into their own jobs so that when xharness reruns need to happen, we only have to rerun the xharness legs. * Fix publishing logs * And there * Fix yaml syntax, separate even further
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There are frequently intermittent failures in the XHarness testing that need to be retried due to timeouts or xharness flakiness. Because the XHarness tests are in the same job as the regular helix tests, we have rerun all of the testing just to rerun the xharness tests. This wastes resources and is frustrating for devs.
This change splits out the xharness tests into their own jobs so that when xharness reruns need to happen, we only have to rerun the xharness legs.
Fixes #8252.
To double check: