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

Use a list for tests in src/tests/run.py #78463

Merged
merged 1 commit into from
Nov 19, 2022

Conversation

jakobbotsch
Copy link
Member

Fix #78462

Otherwise we may problems due to multiple test assemblies having tests
of the same name (e.g. due to _r, _ro versions of the same tests).

Fix dotnet#78462
@ghost
Copy link

ghost commented Nov 16, 2022

Tagging subscribers to this area: @hoyosjs
See info in area-owners.md if you want to be subscribed.

Issue Details

Fix #78462

Author: jakobbotsch
Assignees: jakobbotsch
Labels:

area-Infrastructure-coreclr

Milestone: -

@jakobbotsch
Copy link
Member Author

Not sure that this is the best fix. It works for other tests already without this change because they disambiguate via the name attribute which HardwareIntrinsics tests don't (see #78462 (comment)). Maybe they should, but given that we already have the assembly name that has the _r/_ro suffix, I assume it's probably not necessary to do.

My main concern is then whether we see the _r/_ro distinction anywhere in AzDO, but I think so, since the assembly name does include that.

@BrianBohe
Copy link
Member

Can we change the test names and leave this as a check for future problems?

@jakobbotsch
Copy link
Member Author

Can we change the test names and leave this as a check for future problems?

It's like I said above – I don't think it matters.

@jakobbotsch
Copy link
Member Author

For example, here's one of these test failures:
https://dev.azure.com/dnceng-public/public/_build/results?buildId=81571&view=ms.vss-test-web.build-test-results-tab&runId=1704060&resultId=110825&paneView=dotnet-dnceng.dnceng-anon-build-release-tasks.helix-anon-test-information-tab

You can see both HardwareIntrinsics_r as the work item name and when you look at the console log:

BEGIN EXECUTION
/datadisks/disk1/work/B5A409B3/p/corerun -p System.Reflection.Metadata.MetadataUpdater.IsSupported=false HardwareIntrinsics_r.dll ''
23:16:14.616 Running test: global::JIT.HardwareIntrinsics.Arm._AdvSimd.Arm64.Program.Abs_Vector128_Double()
Supported ISAs:

Anyway, I will leave it up to @trylek and @davidwrighton whether they think this fix is ok, or if we should try to disambiguate the hardware intrinsics test names by assembly also. I'm not sure where to do the latter after #74886.

Copy link
Member

@BruceForstall BruceForstall left a comment

Choose a reason for hiding this comment

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

LGTM, but feel free to wait for @trylek and/or @davidwrighton for more context

Copy link
Member

@trylek trylek left a comment

Choose a reason for hiding this comment

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

Nice, thanks for fixing this!

@davidwrighton
Copy link
Member

I think this change is fine, but I'll admit I with the testresults.xml file had the distinction in it itself.

@jakobbotsch jakobbotsch merged commit 0f3a88b into dotnet:main Nov 19, 2022
@jakobbotsch jakobbotsch deleted the test-analysis branch November 19, 2022 12:25
@ghost ghost locked as resolved and limited conversation to collaborators Dec 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Local test run fails to analyze HardwareIntrinsics test results
5 participants