[PERF] Fix runtime-wasm-perf pipeline prereq install failure #107317
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…conflict between node and libnode72:amd64 12.22.9~dfsg-1ubuntu3.6. This is fixed by running sudo apt autoremove -y before installing nodejs to remove the libnode72 package.
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
akoeplinger
approved these changes
Sep 3, 2024
Closed
caaavik-msft
approved these changes
Sep 3, 2024
radekdoulik
pushed a commit
to radekdoulik/runtime
that referenced
this pull request
Sep 6, 2024
…ckage conflict (dotnet#107317) Fix runtime-wasm-perf pipeline runs that are failing due to a package conflict between node and libnode72:amd64 12.22.9~dfsg-1ubuntu3.6. This is fixed by running sudo apt autoremove -y before installing nodejs to remove the libnode72 package.
jtschuster
pushed a commit
to jtschuster/runtime
that referenced
this pull request
Sep 17, 2024
…ckage conflict (dotnet#107317) Fix runtime-wasm-perf pipeline runs that are failing due to a package conflict between node and libnode72:amd64 12.22.9~dfsg-1ubuntu3.6. This is fixed by running sudo apt autoremove -y before installing nodejs to remove the libnode72 package.
sirntar
pushed a commit
to sirntar/runtime
that referenced
this pull request
Sep 30, 2024
…ckage conflict (dotnet#107317) Fix runtime-wasm-perf pipeline runs that are failing due to a package conflict between node and libnode72:amd64 12.22.9~dfsg-1ubuntu3.6. This is fixed by running sudo apt autoremove -y before installing nodejs to remove the libnode72 package.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix runtime-wasm-perf pipeline runs that are failing due to a package conflict between node and libnode72:amd64 12.22.9~dfsg-1ubuntu3.6. This is fixed by running sudo apt autoremove -y before installing nodejs to remove the libnode72 package.
Run with example failure: https://dev.azure.com/dnceng-public/public/_build/results?buildId=795729&view=results
Example failure: