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] perftiger v8 - Failed to install prerequisites #100910

Open
pavelsavara opened this issue Apr 11, 2024 · 4 comments
Open

[wasm] perftiger v8 - Failed to install prerequisites #100910

pavelsavara opened this issue Apr 11, 2024 · 4 comments
Labels
area-Infrastructure Known Build Error Use this to report build issues in the .NET Helix tab perf-pipeline Issues with dotnet-runtime-perf, or runtime-wasm-perf pipelines
Milestone

Comments

@pavelsavara
Copy link
Member

pavelsavara commented Apr 11, 2024

Log

Preparing to unpack .../nodejs_18.20.2-1nodesource1_amd64.deb ...
Unpacking nodejs (18.20.2-1nodesource1) ...
dpkg: error processing archive /var/cache/apt/archives/nodejs_18.20.2-1nodesource1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/systemtap/tapset/node.stp', which is also in package libnode72:amd64 12.22.9~dfsg-1ubuntu3.4
Errors were encountered while processing:
 /var/cache/apt/archives/nodejs_18.20.2-1nodesource1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
+ export PERF_PREREQS_INSTALL_FAILED=1
+ test x1 = x1
+ echo ** Error: Failed to install prerequites **
** Error: Failed to install prerequites **

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=639255
Build error leg or test failing:

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "Failed to install prerequisites",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=639255
Error message validated: [Failed to install prerequisites]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 4/11/2024 12:51:04 PM UTC

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0
@pavelsavara pavelsavara added arch-wasm WebAssembly architecture blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab perf-pipeline Issues with dotnet-runtime-perf, or runtime-wasm-perf pipelines os-browser Browser variant of arch-wasm labels Apr 11, 2024
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Apr 11, 2024
Copy link
Contributor

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

@pavelsavara
Copy link
Member Author

cc @LoopedBard3

we also noticed

The following packages were automatically installed and are no longer required:
  apport-symptoms libc-ares2 libjs-highlight.js libnode72 moby-tini
  python3-apport python3-problem-report python3-systemd

@vcsjones vcsjones added area-Infrastructure and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Apr 12, 2024
@lewing lewing added this to the 9.0.0 milestone Apr 13, 2024
@lewing lewing removed the untriaged New issue has not been triaged by the area owner label Apr 13, 2024
@lewing lewing removed blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' arch-wasm WebAssembly architecture os-browser Browser variant of arch-wasm labels Jul 29, 2024
@lewing
Copy link
Member

lewing commented Jul 30, 2024

this is failing more places than wasm

@am11
Copy link
Member

am11 commented Aug 22, 2024

Probably reliable fix is to skip the package manager and download node binaries from https://nodejs.org/dist/latest-v18.x/. e.g.

$ mkdir -p /tmp/node
$ curl -sSL https://nodejs.org/dist/latest-v18.x/node-v18.20.4-linux-x64.tar.xz | \
    tar -Jxf - --strip-components=1 -C /tmp/node

$ ls /tmp/node/bin
corepack	node		npm		npx

# export PATH=/tmp/node/bin:$PATH

@agocke agocke modified the milestones: 9.0.0, 10.0.0 Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Infrastructure Known Build Error Use this to report build issues in the .NET Helix tab perf-pipeline Issues with dotnet-runtime-perf, or runtime-wasm-perf pipelines
Projects
Status: No status
Development

No branches or pull requests

5 participants