Closed Bug 1952403 Opened 6 months ago Closed 3 months ago

Intermittent FileNotFoundError: [Errno 2] No such file or directory: 'callgraph.txt.tmp1' -> 'callgraph.txt'

Categories

(Core :: JavaScript: GC, defect, P5)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure)

Filed by: csabou [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=497937759&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/ZUvUcOP_Qkq8sJ7NZ81qMw/runs/1/artifacts/public/logs/live_backing.log


[task 2025-03-06T21:42:38.119Z] Collected 79396 objects
[task 2025-03-06T21:42:38.119Z] Final transaction received, finishing...
[task 2025-03-06T21:43:19.958Z] Waiting for manager to finish (build status 0)...
[task 2025-03-06T21:43:19.958Z] Exiting with status 0
[task 2025-03-06T21:43:19.959Z] build finished (status 0): Thu Mar  6 21:43:19 2025
[task 2025-03-06T21:43:19.959Z] Exiting run_complete with status 0
[task 2025-03-06T21:43:20.036Z] + /builds/worker/checkouts/gecko/mach hazards analyze --project=browser --shell-objdir=/builds/worker/workspace/obj-haz-shell --work-dir=/builds/worker/workspace/haz-browser
[task 2025-03-06T21:43:20.642Z] /builds/worker/checkouts/gecko/js/src/devtools/rootAnalysis/analyze.py --js /builds/worker/workspace/obj-haz-shell/dist/bin/js
[task 2025-03-06T21:43:20.687Z] Running gcTypes to generate ['gcTypes.txt', 'typeInfo.txt']
[task 2025-03-06T21:43:20.688Z]   XDB="$HOME/fetches/sixgill/usr/bin/xdb.so" SOURCE="$HOME/checkouts/gecko" ~/workspace/obj-haz-shell/dist/bin/js ~/checkouts/gecko/js/src/devtools/rootAnalysis/computeGCTypes.js gcTypes.txt typeInfo.txt
[task 2025-03-06T21:43:55.344Z] Running rawcalls to generate ['rawcalls.{i}.of.{n}']
[task 2025-03-06T21:43:55.372Z]   XDB="$HOME/fetches/sixgill/usr/bin/xdb.so" SOURCE="$HOME/checkouts/gecko" ~/workspace/obj-haz-shell/dist/bin/js ~/checkouts/gecko/js/src/devtools/rootAnalysis/computeCallgraph.js typeInfo.txt rawcalls.1.of.1 1 1
[task 2025-03-06T21:47:18.619Z] Running gcFunctions to generate ['callgraph.txt', 'gcFunctions.txt', 'gcFunctions.lst', 'limitedFunctions.lst']
[task 2025-03-06T21:47:18.620Z]   XDB="$HOME/fetches/sixgill/usr/bin/xdb.so" SOURCE="$HOME/checkouts/gecko" ~/workspace/obj-haz-shell/dist/bin/js ~/checkouts/gecko/js/src/devtools/rootAnalysis/computeGCFunctions.js rawcalls.1.of.1 --outputs callgraph.txt gcFunctions.txt gcFunctions.lst limitedFunctions.lst
[task 2025-03-06T21:51:11.385Z] /builds/worker/checkouts/gecko/js/src/devtools/rootAnalysis/loadCallgraph.js:380:13 uncaught exception: out of memory
[task 2025-03-06T21:51:11.385Z] Stack:
[task 2025-03-06T21:51:11.385Z]   loadCallgraph@/builds/worker/checkouts/gecko/js/src/devtools/rootAnalysis/loadCallgraph.js:380:13
[task 2025-03-06T21:51:11.385Z]   @/builds/worker/checkouts/gecko/js/src/devtools/rootAnalysis/computeGCFunctions.js:73:18
[task 2025-03-06T21:51:15.230Z] Error renaming callgraph.txt.tmp1 -> callgraph.txt
[task 2025-03-06T21:51:15.230Z] Traceback (most recent call last):
[task 2025-03-06T21:51:15.230Z]   File "/builds/worker/checkouts/gecko/js/src/devtools/rootAnalysis/analyze.py", line 462, in <module>
[task 2025-03-06T21:51:15.230Z]     run_job(step, data)
[task 2025-03-06T21:51:15.230Z]   File "/builds/worker/checkouts/gecko/js/src/devtools/rootAnalysis/analyze.py", line 263, in run_job
[task 2025-03-06T21:51:15.230Z]     os.rename(temp, final)
[task 2025-03-06T21:51:15.230Z] FileNotFoundError: [Errno 2] No such file or directory: 'callgraph.txt.tmp1' -> 'callgraph.txt'
[task 2025-03-06T21:51:15.239Z] Error running mach:
[task 2025-03-06T21:51:15.239Z] 
[task 2025-03-06T21:51:15.239Z]     mach hazards analyze --project=browser --shell-objdir=/builds/worker/workspace/obj-haz-shell --work-dir=/builds/worker/workspace/haz-browser
[task 2025-03-06T21:51:15.239Z] 
[task 2025-03-06T21:51:15.239Z] The error occurred in code that was called by the mach command. This is either
[task 2025-03-06T21:51:15.239Z] a bug in the called code itself or in the way that mach is calling it.
[task 2025-03-06T21:51:15.239Z] You can invoke ``./mach busted`` to check if this issue is already on file. If it
[task 2025-03-06T21:51:15.239Z] isn't, please use ``./mach busted file hazards`` to report it. If ``./mach busted`` is
[task 2025-03-06T21:51:15.239Z] misbehaving, you can also inspect the dependencies of bug 1543241.
[task 2025-03-06T21:51:15.239Z] 
[task 2025-03-06T21:51:15.239Z] If filing a bug, please include the full output of mach, including this error
[task 2025-03-06T21:51:15.239Z] message.
[task 2025-03-06T21:51:15.239Z] 
[task 2025-03-06T21:51:15.239Z] The details of the failure are as follows:
[task 2025-03-06T21:51:15.239Z] 
[task 2025-03-06T21:51:15.239Z] Exception: Process executed with non-0 exit code 1: /builds/worker/checkouts/gecko/js/src/devtools/rootAnalysis/analyze.py --js /builds/worker/workspace/obj-haz-shell/dist/bin/js
[task 2025-03-06T21:51:15.239Z] 
[task 2025-03-06T21:51:15.239Z]   File "/builds/worker/checkouts/gecko/js/src/devtools/rootAnalysis/mach_commands.py", line 498, in analyze
[task 2025-03-06T21:51:15.239Z]     return command_context.run_process(args=args, cwd=work_dir, pass_thru=True)
[task 2025-03-06T21:51:15.239Z]   File "/builds/worker/checkouts/gecko/python/mach/mach/mixin/process.py", line 194, in run_process
[task 2025-03-06T21:51:15.239Z]     raise Exception(
[task 2025-03-06T21:51:15.294Z] + grab_artifacts
[task 2025-03-06T21:51:15.294Z] + local artifacts
[task 2025-03-06T21:51:15.294Z] + artifacts=/builds/worker/artifacts
[task 2025-03-06T21:51:15.294Z] + '[' -d /builds/worker/workspace/haz-browser ']'
[task 2025-03-06T21:51:15.295Z] + cd /builds/worker/workspace/haz-browser
[task 2025-03-06T21:51:15.295Z] + ls -lah
[task 2025-03-06T21:51:15.297Z] total 11G
Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → INCOMPLETE

The real bug here is that I should format the error messages to pick up the correct error. The message that's getting keyed on is sort of a "something went wrong earlier" message.

You need to log in before you can comment on or make changes to this bug.