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

[wasm] Use correct current runtime pack version for Wasm.Build.Tests #109836

Merged
merged 1 commit into from
Nov 15, 2024

Conversation

maraf
Copy link
Member

@maraf maraf commented Nov 14, 2024

Wasm.Build.Tests are not a shipping project, PackageVersion will have a version suffix even for release branch, where actual runtime pack version doesn't have version suffix. Use ProductVersion in that case, based on StabilizePackageVersion value.

Forwardport of #109820

@maraf maraf added arch-wasm WebAssembly architecture area-Infrastructure-mono labels Nov 14, 2024
@maraf maraf added this to the 10.0.0 milestone Nov 14, 2024
@maraf maraf self-assigned this Nov 14, 2024
<ItemGroup>
<_RuntimePackVersions Include="$(PackageVersion)" EnvVarName="RUNTIME_PACK_VER9" />
<_RuntimePackVersions Include="$(_RuntimePackCurrentVersion)" EnvVarName="RUNTIME_PACK_VER9" />
Copy link
Member

Choose a reason for hiding this comment

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

we need to update this to RUNTIME_PACK_VER10 at some point right? do you know if we have a tracking issue somewhere?

Copy link
Member Author

@maraf maraf Nov 15, 2024

Choose a reason for hiding this comment

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

We don't. Maybe be better than tracking issue is to write it down to some wiki "All wasm steps for new TFM"™️.

@maraf
Copy link
Member Author

maraf commented Nov 15, 2024

This test shouldn't have failed https://helix.dot.net/api/2019-06-17/jobs/42eee7bb-58b1-4b33-ace4-35a44ee56d6b/workitems/NoWorkload-ST-Wasm.Build.Tests/console. Also, the required sub-string is visible in the output...

@akoeplinger
Copy link
Member

@maraf I've seen this happening a couple times, there is some race condition where the stdout doesn't get read completely before we're checking for the substring. I bet it will pass when you rerun tests.

@maraf maraf merged commit 55eee32 into dotnet:main Nov 15, 2024
22 of 24 checks passed
@maraf maraf deleted the WbtRuntimePackVersionMain branch November 15, 2024 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants