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
From https://cirrus-ci.com/task/4730167113809920 (when testing #3825):
not ok 64 events oom # (in test file tests/integration/events.bats, line 101) # `grep -q '{"type":"oom","id":"test_busybox"}' events.log' failed # runc spec (status=0): # # runc run -d --console-socket /tmp/bats-run-0YPqCy/runc.OcyGHv/tty/sock test_busybox (status=0): # # Command "grep -q oom events.log" failed 10 times. Output:
Creating this issue to see if this ever happens again. If yes, my only guess is, we could increase the waiting time.
The text was updated successfully, but these errors were encountered:
Happened again in https://cirrus-ci.com/task/6367846062620672
not ok 64 events oom # (in test file tests/integration/events.bats, line 101) # `grep -q '{"type":"oom","id":"test_busybox"}' events.log' failed # runc spec (status=0): # # runc run -d --console-socket /tmp/bats-run-sZp6NW/runc.oxo6eR/tty/sock test_busybox (status=0): # # Command "grep -q oom events.log" failed 10 times. Output:
Sorry, something went wrong.
And here: https://cirrus-ci.com/task/5060911505866752
Opened #3874 with a workaround
Successfully merging a pull request may close this issue.
From https://cirrus-ci.com/task/4730167113809920 (when testing #3825):
Creating this issue to see if this ever happens again. If yes, my only guess is, we could increase the waiting time.
The text was updated successfully, but these errors were encountered: