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

Offline npm build failures in aspnetcore #4129

Closed
MichaelSimons opened this issue Feb 14, 2024 · 3 comments
Closed

Offline npm build failures in aspnetcore #4129

MichaelSimons opened this issue Feb 14, 2024 · 3 comments
Assignees
Labels
area-upstream-fix Needs a change in a contributing repo ops-monitor Issues created/handled by the source build monitor role

Comments

@MichaelSimons
Copy link
Member

All offline CI legs are failing with npm build failures in aspnetcore.

Microsoft internal build link

    Checking node version...
    v20.9.0
    Checking npm version...
    10.1.0
    npm ERR! code 1
    npm ERR! path /vmr/src/aspnetcore/node_modules/puppeteer
    npm ERR! command failed
    npm ERR! command sh -c node install.mjs
  EXEC : npm ERR! error : Failed to set up Chrome r119.0.6045.105! Set "PUPPETEER_SKIP_DOWNLOAD" env variable to skip download. [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]EXEC(0,0): error : Failed to set up Chrome r119.0.6045.105! Set "PUPPETEER_SKIP_DOWNLOAD" env variable to skip download.
  EXEC : npm ERR! error : getaddrinfo ENOTFOUND edgedl.me.gvt1.com [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]EXEC(0,0): error : getaddrinfo ENOTFOUND edgedl.me.gvt1.com
    npm ERR!     at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26) {
    npm ERR!   errno: -3008,
    npm ERR!   code: 'ENOTFOUND',
    npm ERR!   syscall: 'getaddrinfo',
    npm ERR!   hostname: 'edgedl.me.gvt1.com'
    npm ERR! }

This appears to be a regression caused by dotnet/aspnetcore#53975

@wtgodbe
Copy link
Member

wtgodbe commented Feb 14, 2024

@javiercn should we just skip the chrome download? I'm assuming we'll have to skip those tests in offline source build

@wtgodbe
Copy link
Member

wtgodbe commented Feb 14, 2024

Never mind, I see we already have dotnet/aspnetcore#54036

@MichaelSimons MichaelSimons added area-upstream-fix Needs a change in a contributing repo and removed area-testing Improvements in CI and testing untriaged labels Feb 15, 2024
@MichaelSimons
Copy link
Member Author

[Triage] This was fixed in aspnetcore, waiting for it to flow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-upstream-fix Needs a change in a contributing repo ops-monitor Issues created/handled by the source build monitor role
Projects
Archived in project
Development

No branches or pull requests

3 participants