-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Kill testing processes if the test takes too long #5174
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5174 +/- ##
=========================================
Coverage ? 37.52%
=========================================
Files ? 309
Lines ? 45820
Branches ? 0
=========================================
Hits ? 17195
Misses ? 26163
Partials ? 2462 Continue to review full report at Codecov.
|
aa86ddd
to
e36ab79
Compare
@typeless please resolve the conflict |
@lunny Done. |
Could you reenable test-sqlite3 on this PR? |
@lunny Sure. |
I restarted the CI 3 times and everytime CI passed and there is no timeout. |
And the killing maybe unnecessary. |
@lunny If there are no concerns, I would like to keep it longer or even apply to all the database tests in the hope that some mysterious, sporadic hanging bug can be spotted (which could be very hard to reproduce). |
Yes, ten minutes maybe too short. |
When timeout, Send ABRT signal to print backtraces for diagnosis. The timeout value is set to 1200s (20mins) for now.
A temporary band-aid to avoid resource-wasting CI build.
It prints the backtrace in case of timeout.
For #5172