Closed Bug 1816208 Opened 2 years ago Closed 5 months ago

docker-image-updatebot-3rdp is failing with fsevents not accessible from chokidar

Categories

(Developer Infrastructure :: Mach Vendor & Updatebot, defect)

Product:
Developer Infrastructure
Component:
Mach Vendor & Updatebot
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: CosminS, Assigned: tjr)

Details

(Keywords: intermittent-failure)

Log: https://firefox-ci-tc.services.mozilla.com/tasks/O8rvSsDoTS25wqRN-7-rAw/runs/3/logs/public/logs/live.log#L5700

Treeherder task here.

remote: Compressing objects: 100% (53/53), done.        
remote: Total 88285 (delta 50), reused 79 (delta 41), pack-reused 88191        
Receiving objects: 100% (88285/88285), 130.78 MiB | 40.87 MiB/s, done.
Resolving deltas: 100% (63062/63062), done.
cd /builds/worker/pdf.js
+ cd /builds/worker/pdf.js
npm ci
+ npm ci
npm WARN npm npm does not support Node.js v10.24.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/
..................] - : info using node@v10.24.0
[..................] / : info using node@v10.24.0
npm ERR! fsevents not accessible from chokidar
npm ERR! A complete log of this run can be found in:
npm ERR!     /builds/worker/.npm/_logs/2023-02-10T23_30_18_353Z-debug.log
error building image: error building stage: failed to execute command: waiting for process to exit: exit status 1
Error: Could not build image.
[taskcluster 2023-02-10 23:30:19.015Z] === Task Finished ===
[taskcluster 2023-02-10 23:30:19.034Z] Artifact "public/image.tar.zst" not found at "/workspace/image.tar.zst": (HTTP code 404) no such container - Could not find the file /workspace/image.tar.zst in container 1617757b45fe4d3d0e12aa5b77b87ec8f1f25ea4c4fcc540b105ab2c7f57ecf1 
[taskcluster 2023-02-10 23:30:19.124Z] Unsuccessful task run with exit code: 1 completed in 262.065 seconds

I'm kinda wondering why we even run this on trees other than m-c since updatebot only runs there anyway. At least this doesn't appear to have any dependent jobs, so it's probably safe enough to ignore.

(In reply to Ryan VanderMeulen [:RyanVM] from comment #1)

I'm kinda wondering why we even run this on trees other than m-c since updatebot only runs there anyway. At least this doesn't appear to have any dependent jobs, so it's probably safe enough to ignore.

Very true. This might be the canary in the coal mine, and it is broken on m-c also.

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.

Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.