Skip to content

Separate Helix and XHarness testing#8255

Merged
michellemcdaniel merged 4 commits intodotnet:mainfrom
michellemcdaniel:xHarnessTestsYaml
Dec 10, 2021
Merged

Separate Helix and XHarness testing#8255
michellemcdaniel merged 4 commits intodotnet:mainfrom
michellemcdaniel:xHarnessTestsYaml

Conversation

@michellemcdaniel
Copy link
Copy Markdown
Contributor

@michellemcdaniel michellemcdaniel commented Dec 10, 2021

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:

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.
@MattGal
Copy link
Copy Markdown
Member

MattGal commented Dec 10, 2021

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.

@michellemcdaniel michellemcdaniel merged commit 18adc5b into dotnet:main Dec 10, 2021
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Make XHarness tests run in parallel with other arcade testing

2 participants