Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Runner randomly gets killed #15

Open
espidev opened this issue Nov 15, 2020 · 2 comments
Open

Runner randomly gets killed #15

espidev opened this issue Nov 15, 2020 · 2 comments
Labels
bug Something isn't working

Comments

@espidev
Copy link
Member

espidev commented Nov 15, 2020

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

image
@espidev espidev added the bug Something isn't working label Nov 15, 2020
@espidev
Copy link
Member Author

espidev commented Nov 16, 2020

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

@espidev
Copy link
Member Author

espidev commented Nov 23, 2020 

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@espidev