-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
September infra rollout - continued CoreCLR / Mono test cleanup (minimal) #40345
Conversation
Tagging subscribers to this area: @ViktorHofer |
Hello everyone! As I'm already three days past the originally planned roll-out date and there's been no progress on this review so far, I treat this as an indication that we're not inclined to risk destabilizing testing at this point and this change (and the related work item) should be postponed to the next monthly roll-out on September 7th. Please let me know if you think otherwise. Thanks Tomas |
a141889
to
6f4c937
Compare
6f4c937
to
ef04c92
Compare
Merging in as I believe that the CovariantReturn test failures are seen in other outerloop runs and unrelated to my change. |
Similar to the previous occasion, I have identified this set as the minimum meaningful set of scripts to move without causing too much disruption apart from purely mechanical renames. This change moves the developer-facing test-related CoreCLR scripts under the
src/tests
folder in accordance with the previous move of the tests themselves:src/coreclr/build-test.cmd
tosrc/tests/build.cmd
src/coreclr/build-test.sh
tosrc/tests/build.sh
src/coreclr/tests/build.proj
tosrc/tests/build.proj
src/coreclr/tests/runtest.cmd
tosrc/tests/run.cmd
src/coreclr/tests/runtest.sh
tosrc/tests/run.sh
src/coreclr/tests/src/runtest.proj
tosrc/tests/run.proj
src/coreclr/tests/issues.targets
tosrc/tests/issues.targets
The rest of the change constitutes mere path adjustments to match the primary rename.
Move of the rest of the
src/coreclr/tests
folder undersrc/tests
including unification of the variousprops
andtargets
file that I originally proposed is extremely complicated and most of it doesn't affect normal developers' daily life at all so I believe that at least some of these cleanups can be made out-of-band, not waiting on the monthly infra roll-out cadence.Fixes: #38919
(I'll triage the remaining changes I originally proposed in the work item, I'll send out "normal" PR's for non-disruptive ones and I'll create a new follow-up September roll-out change for the rest.)
Thanks
Tomas
/cc: @dotnet/runtime-infrastructure