Closed DonggeLiu closed 4 years ago
I am not too sure if this error occurred in the competition, as the result HTML file from the competition is different from the one I generated. They look alike, but mine does not have coverage scores.
I recall that we had two HTML files for each experiment, one before validation and one after. I think mine is the former and the competition only released the latter.
I don't know if this OSError
can get propagated to the latter HTML, I can only confirm that the latter HTML from the competition did report this error on the same benchmarks, it reported OUT OF MEMORY
instead.
Solved by calling ulimit -n N
where N should be large enough to allow tons of binary executions but smaller than the local hard limit (from ulimit -n -H
)
Every benchmark quickly encounters the following error when running inside
BenchExec
:This is strange and troublesome because:
BenchExec
, this error can be mitigated by settingulimit -Sn 10000
orulimit -n unlimited
, but not sure how to do it insideBenchExec
subprocess
after the version we submitted.os.system("ulimit -n unlimited")
at the beginning of Legion, the same error occurredinstr.stdout.close()
,instr.stdin.close()
,instr.stderr.close()
) and kill the subporcess (instr.kill()
), none of them worked.--filesCountLimit 1024
flag toBenchExec
, caused the following error: