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

[RISC-V,QEMU] Disable execution of two corefx tests on QEMU #105689

Merged
merged 1 commit into from
Jul 31, 2024

Conversation

rzsc
Copy link
Contributor

@rzsc rzsc commented Jul 30, 2024

Disable execution of two corefx tests on QEMU

System.Diagnostics.Tests.ProcessTests.TestMaxWorkingSet()
System.Diagnostics.Tests.ProcessTests.TestMinWorkingSet()

These two corefx tests fail because on QEMU the file /proc/pid/stat contains incorrect values.

See issue #105686 for details.

Part of #84834, cc @dotnet/samsung

System.Diagnostics.Tests.ProcessTests.TestMaxWorkingSet()
System.Diagnostics.Tests.ProcessTests.TestMinWorkingSet()

These two corefx tests fail because on QEMU the file /proc/pid/stat
contains incorrect values.

See issue dotnet#105686 for details.
@dotnet-policy-service dotnet-policy-service bot added the community-contribution Indicates that the PR has been added by a community member label Jul 30, 2024
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-system-diagnostics-process
See info in area-owners.md if you want to be subscribed.

@rzsc rzsc changed the title [RISCV,QEMU] Disable execution of two corefx tests on QEMU [RISC-V,QEMU] Disable execution of two corefx tests on QEMU Jul 30, 2024
Copy link
Member

@adamsitnik adamsitnik left a comment

Choose a reason for hiding this comment

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

LGTM, thank you @rzsc !

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Diagnostics.Process community-contribution Indicates that the PR has been added by a community member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants