Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Mark GcCollect test as incompatible with GcStress#17390

Merged
AndyAyersMS merged 1 commit intodotnet:masterfrom
AndyAyersMS:MarkGcCollectTestAsGcStressIncompatible
Apr 3, 2018
Merged

Mark GcCollect test as incompatible with GcStress#17390
AndyAyersMS merged 1 commit intodotnet:masterfrom
AndyAyersMS:MarkGcCollectTestAsGcStressIncompatible

Conversation

@AndyAyersMS
Copy link
Member

Extends changes in #17319 to cover stress tests run via the normal
msbuild/xunit test harness.

Extends changes in dotnet#17319 to cover stress tests run via the normal
msbuild/xunit test harness.
@AndyAyersMS
Copy link
Member Author

@janvorli @BruceForstall PTAL
cc @dotnet/jit-contrib

Related to failures seen in #17027 / #17330.

@AndyAyersMS
Copy link
Member Author

@dotnet-bot test Windows_NT x64 Checked gcstress0xc_jitstress2

@AndyAyersMS
Copy link
Member Author

x64 gc stress failure is known issue #17389.

The OSX and ARM64 failures are jenkins remoting problems.

Don't see any point in retrying these as this change will only impact GC stress runs.

@AndyAyersMS AndyAyersMS merged commit 03356bc into dotnet:master Apr 3, 2018
@AndyAyersMS AndyAyersMS deleted the MarkGcCollectTestAsGcStressIncompatible branch April 3, 2018 06:04
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.

2 participants