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

Activity

1. pavelsavara

   added

   arch-wasmWebAssembly architectureWebAssembly architecture

   blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'

   Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tab

   perf-pipelineIssues with dotnet-runtime-perf, or runtime-wasm-perf pipelinesIssues with dotnet-runtime-perf, or runtime-wasm-perf pipelines

   os-browserBrowser variant of arch-wasmBrowser variant of arch-wasm

   on Apr 11, 2024
2. ghost added

   needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area ownersAn area label is needed to ensure this gets routed to the appropriate area owners

   on Apr 11, 2024
3. dotnet-policy-service commented on Apr 11, 2024

   

   dotnet-policy-servicebot

   on Apr 11, 2024 – with Dotnet Policy Service

   Contributor

   More actions

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

   added

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Apr 11, 2024
5. pavelsavara commented on Apr 11, 2024

   

   pavelsavara

   on Apr 11, 2024

   MemberAuthor

   More actions

   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
   

   👍React with 👍1Reacted by Parker Bibus
6. vcsjones

   added

   area-Infrastructure

   and removed

   needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area ownersAn area label is needed to ensure this gets routed to the appropriate area owners

   on Apr 12, 2024
7. lewing

   added this to the 9.0.0 milestone on Apr 13, 2024
8. lewing

   removed

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Apr 13, 2024
9. agocke

   added this to Runtime Infraon Jul 8, 2024
10. lewing

    removed

    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'

    arch-wasmWebAssembly architectureWebAssembly architecture

    os-browserBrowser variant of arch-wasmBrowser variant of arch-wasm

    on Jul 29, 2024
11. lewing commented on Jul 30, 2024

    

    lewing

    on Jul 30, 2024

    Member

    More actions

    this is failing more places than wasm
12. am11 commented on Aug 22, 2024

    

    am11

    on Aug 22, 2024

    Last edited by am11

    Member

    More actions

    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
13. agocke

    modified the milestones: 9.0.0, 10.0.0 on Aug 22, 2024
14. agocke

    closed this as completedon Aug 4, 2025
15. github-project-automation

    moved this to Done in Runtime Infraon Aug 4, 2025
16. github-actions

    locked and limited conversation to collaborators on Sep 4, 2025