Skip to content
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

[CI] Use dotnet-test-slicer in nightly tests #8154

Merged
merged 1 commit into from
Jun 29, 2023
Merged

Conversation

pjcollins
Copy link
Member

Updates the TimeZoneInfo and Localization test stages to use the
dotnet-test-slicer tool used by other MSBuild test runs.

These test jobs have a pretty high frequency of failing and timing out,
and a few changes have been made to try to reduce the points of failure.

SetUp and TearDown functions have been trimmed down and made standard
across the two fixtures. OneTimeSetup will prepare the device and
install the project, and we will only attempt to attach log files during
TearDown.

The tests will launch the app activity directly with ADB, rather than
using dotnet build -t:Run for every iteration. The tests will attempt
to reinstall the app if it is not present as a fallback.

@pjcollins pjcollins force-pushed the dev/pjc/nightly-retry branch 2 times, most recently from 1d0e12e to d74fc45 Compare June 28, 2023 23:58
Updates the `TimeZoneInfo` and `Localization` test stages to use the
`dotnet-test-slicer` tool used by other MSBuild test runs.

These test jobs have a pretty high frequency of failing and timing out,
and a few changes have been made to try to reduce the points of failure.

SetUp and TearDown functions have been trimmed down and made standard
across the two fixtures.  OneTimeSetup will prepare the device and
install the project, and we will only attempt to attach log files during
TearDown.

The tests will launch the app activity directly with ADB, rather than
using `dotnet build -t:Run` for every iteration.  The tests will attempt
to reinstall the app if it is not present as a fallback.
@pjcollins pjcollins force-pushed the dev/pjc/nightly-retry branch from d74fc45 to 9b11f87 Compare June 29, 2023 00:05
@pjcollins
Copy link
Member Author

@pjcollins pjcollins marked this pull request as ready for review June 29, 2023 16:57
@pjcollins pjcollins requested a review from jpobst June 29, 2023 16:57
Copy link
Contributor

@jpobst jpobst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love how much simpler the .yaml is. 😍

Note that using [OneTimeSetup] with dotnet-test-slicer auto-retry may currently cause the retries to fail. Fixing that is still a work in progress.

@pjcollins pjcollins merged commit 69b4ab0 into main Jun 29, 2023
@pjcollins pjcollins deleted the dev/pjc/nightly-retry branch June 29, 2023 21:48
grendello added a commit to grendello/xamarin-android that referenced this pull request Jun 30, 2023
* main:
  [CI] Use dotnet test slicer in nightly tests (dotnet#8154)
grendello added a commit to grendello/xamarin-android that referenced this pull request Jul 6, 2023
* main:
  Bump to dotnet/installer@28d4a6b4be 8.0.100-preview.7.23330.16 (dotnet#8162)
  [Xamarin.Android.Build.Tasks] Move MonoAndroidAssetsDirIntermediate (dotnet#8166)
  [xaprepare] update Debian dependencies for current unstable (trixie) (dotnet#8169)
  [CI] Use dotnet test slicer in nightly tests (dotnet#8154)
  [Xamarin.Android.Build.Tasks] MarshalMethodsAssemblyRewriter+new file (dotnet#8151)
  Bump to dotnet/installer@d2a244f560 8.0.100-preview.7.23325.5 (dotnet#8142)
@github-actions github-actions bot locked and limited conversation to collaborators Jan 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants