Runner randomly gets killed

[espidev]

With large amounts of test cases and resource usage, there is a possibility of the runner randomly get a SIGKILL signal...

[espidev]

reminder to myself try using the data race detector: https://golang.org/doc/articles/race_detector.html

[espidev]

2020-11-23 03:04:06 [INFO] Worker 1 has picked up job for 5fbb24acf4e3816a0cd019c8 in java11.
2020-11-23 03:04:06 [INFO] Compiling request in java11 for testing-sessions/butid9hdtf5oifllka6g.
2020-11-23 03:04:07 [INFO] Compile complete for testing-sessions/butid9hdtf5oifllka6g.
2020-11-23 03:04:07 [DEBUG] Batch #0
2020-11-23 03:04:07 [DEBUG] Judging case #0
2020-11-23 03:04:07 [WARN] child: bad file descriptor
2020-11-23 03:04:07 [WARN] forkexec execread: errno 11415968
Killed

Apparently uploading faulty test data can get the runner to consistently get "Killed" by the kernel, maybe this is related...