legion: Regent: binary corruption in separate_compilation.rg in CI
Seems to be a new variation on #1478. Recent CI failure in control_replication: https://gitlab.com/StanfordLegion/legion/-/jobs/4710863839
And on a feature branch: https://gitlab.com/StanfordLegion/legion/-/jobs/4730355599
Failure mode:
/usr/bin/ld: warning: /tmp/lua_oLdpZC.d//libseparate_compilation_tasks_part1.so has a corrupt section with a size (100000004) larger than the file size
/usr/bin/ld: warning: /tmp/lua_oLdpZC.d//libseparate_compilation_tasks_part1.so has a corrupt section with a size (100000004) larger than the file size
/usr/bin/ld: warning: /tmp/lua_oLdpZC.d//libseparate_compilation_tasks_part1.so has a corrupt section with a size (1500000003) larger than the file size
/usr/bin/ld: warning: /tmp/lua_oLdpZC.d//libseparate_compilation_tasks_part1.so has a corrupt section with a size (330000001a) larger than the file size
/usr/bin/ld: warning: /tmp/lua_oLdpZC.d//libseparate_compilation_tasks_part1.so has a corrupt string table index - ignoring
/usr/bin/ld: error: /tmp/lua_oLdpZC.d//libseparate_compilation_tasks_part1.so: ELF section name out of range
collect2: error: ld returned 1 exit status
The error doesn’t make any sense to me unless somehow we’re seeing a race in the creation of temporary directories.
Tracking the issue here so we can watch for it reoccurring.
About this issue
- Original URL
- State: open
- Created 3 years ago
- Comments: 18 (18 by maintainers)
Pushed https://gitlab.com/StanfordLegion/legion/-/commit/a700430522e01e718b8f61ae3ab86095fbd9b54e, hopefully we get better output now.