-
Notifications
You must be signed in to change notification settings - Fork 1k
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.
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
Mitigate long running job for truffleruby in CI by workaround #1292
Conversation
I'd rather have it fail than hide the failure. |
f83f42f
to
b0adbd3
Compare
b0adbd3
to
77b8b73
Compare
I've simplified it. |
It's interesting, it looks like it succeed but then get stuck on exit? Weird. |
When I tried the test in my local machine, it was reproduced. It seems that there were three processes for the test and they were waiting for some kind of lock.
|
I found the following test cases occur the weird behavior in TruffleRuby. redis-rb/test/redis/ssl_test.rb Lines 15 to 20 in 6afa62b
redis-rb/test/redis/ssl_test.rb Lines 40 to 45 in 6afa62b
|
This is just a workaround. I'm not understanding the root cause, sorry. I'd say that it's a pain in the neck because we are made to wait to fail the job with meaningless timeout every time.