We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
With large amounts of test cases and resource usage, there is a possibility of the runner randomly get a SIGKILL signal...
The text was updated successfully, but these errors were encountered:
reminder to myself try using the data race detector: https://golang.org/doc/articles/race_detector.html
Sorry, something went wrong.
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...
No branches or pull requests
With large amounts of test cases and resource usage, there is a possibility of the runner randomly get a SIGKILL signal...
The text was updated successfully, but these errors were encountered: