[BUG] Dashboards 2.x failed to build on Windows Agent
See original GitHub issue+ yarn build-platform --all-platforms --skip-os-packages --version-qualifier=
yarn run v1.22.19
$ node scripts/build --all-platforms --skip-os-packages --version-qualifier=
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
info [ global ] Verifying environment meets requirements
│ succ Node.js version verified
│ succ ✓ 0 sec
info [ global ] Cleaning artifacts from previous builds
│ debg Deleting patterns: [
│ 'C:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\tmpr_kd6u__\\OpenSearch-Dashboards\\build',
│ 'C:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\tmpr_kd6u__\\OpenSearch-Dashboards\\target',
│ 'C:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\tmpr_kd6u__\\OpenSearch-Dashboards\\.node_binaries'
│ ]
│ debg Deleted 1 files/directories
│ succ ✓ 0 sec
info [ global ] Downloading node.js builds for all platforms
│ debg Downloading shasum values for node version 14.20.0 from https://nodejs.org/dist/v14.20.0/SHASUMS256.txt
│ debg Attempting download of https://nodejs.org/dist/v14.20.0/node-v14.20.0-linux-x64.tar.gz 921680e244b813d6ffe06a4c22f87f05f39be635973c79486b2ded12a946cb37
│ debg Attempting download of https://nodejs.org/dist/v14.20.0/node-v14.20.0-darwin-x64.tar.gz 4471111f666f1d1ec549b002e0d416a7222c0fd416aa62c90b19ff3930b07dba
│ debg Attempting download of https://nodejs.org/dist/v14.20.0/node-v14.20.0-linux-arm64.tar.gz d2d15363a2f3a0446983d51a90af7942fe8b1dd4a7f16128dfe718b3bf56dc07
│ debg Attempting download of https://nodejs.org/dist/v14.20.0/win-x64/node.exe ac38e3cc6ba00d9209b1890da4e224e6ae819e681a25cc933770c253d40cab46
│ debg Downloaded https://nodejs.org/dist/v14.20.0/node-v14.20.0-darwin-x64.tar.gz and verified checksum
│ debg Downloaded https://nodejs.org/dist/v14.20.0/node-v14.20.0-linux-x64.tar.gz and verified checksum
│ debg Downloaded https://nodejs.org/dist/v14.20.0/node-v14.20.0-linux-arm64.tar.gz and verified checksum
│ debg Downloaded https://nodejs.org/dist/v14.20.0/win-x64/node.exe and verified checksum
│ succ ✓ 1 sec
info [ global ] Extracting node.js builds for all platforms
│ succ ✓ 17 sec
info [ opensearch-dashboards ] Copying source into platform-generic build directory
│ERROR failure 14 sec
│ERROR Error: EINVAL: invalid argument, utime 'C:\Users\ADMINI~1\AppData\Local\Temp\tmpr_kd6u__\OpenSearch-Dashboards\build\opensearch-dashboards\yarn.lock'
Running on Windows 2019 with nodejs 14.20.0 installed. Able to run on Ubuntu with no issues.
Thanks.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Troubleshoot pipeline runs - Azure DevOps - Microsoft Learn
It is helpful to narrow whether a build or release failure is the result of an Azure Pipelines/TFS product issue (agent or tasks)....
Read more >Nessus Agent Troubleshooting for the Agent Deployment Guide
This provides troubleshooting steps when issues arise with deploying agents and linking them to Tenable.io or Nessus Manager.
Read more >Agent Troubleshooting - Datadog Docs
Agent Troubleshooting. If you have not yet installed the Datadog Agent, go to the dedicated Agent integration page for installation instructions.
Read more >Error: ' CWinHttpSocket::Request failed - N-able
N-sight RMM Troubleshooting. N-sight RMM Troubleshooting. > Error: ' CWinHttpSocket::Request failed:: 0x00002ee2 ' when agent connects to ...
Read more >What is the meaning of "Failed building wheel for X" in pip ...
@hoefling I have wheels (0.32.2) so that is not the problem. But maybe the pycparser package doesn't have a wheel ( *.whl )...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@AMoo-Miki is looking at this and will respond with LOE by EOD Monday.
Thanks Peter for confirming. This is fixed by #2601.