[CI] Use dotnet-test-slicer in nightly tests#8154
Merged
Conversation
pjcollins
force-pushed
the
dev/pjc/nightly-retry
branch
2 times, most recently
from
1d0e12e to
d74fc45
Compare
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
force-pushed
the
dev/pjc/nightly-retry
branch
from
d74fc45 to
9b11f87
Compare
Member
Author
pjcollins
requested review from
dellis1972,
jonathanpeppers and
jonpryor
as code owners
jpobst
approved these changes
Jun 29, 2023
Contributor
jpobst
left a comment
jpobst
left a comment
There was a problem hiding this comment.
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.
dellis1972
approved these changes
Jun 29, 2023
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)
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Updates the
TimeZoneInfoandLocalizationtest stages to use thedotnet-test-slicertool 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:Runfor every iteration. The tests will attemptto reinstall the app if it is not present as a fallback.