-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
cms-bot and fake AddOn test failures #29415
Comments
assign core |
New categories assigned: core @Dr15Jones,@smuzaffar,@makortel you have been requested to review this Pull request/Issue and eventually sign? Thanks |
A new Issue was created by @silviodonato Silvio Donato. @Dr15Jones, @silviodonato, @dpiparo, @smuzaffar, @makortel can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
looks like addOn tests were timeout after 2 hours. I think there was some network issues at CERN that is why these tests were timing out . This also happened for IBs few days back. Things looks better now. I will update cms-bot to properly report is addOnTests were timeout. |
thanks @smuzaffar , feel free to close the ticket then |
I will close it after fixing cms-bot to properly report the timeouts. |
cms-bot change cms-sw/cms-bot@9969c92 should properly indicate if addOnTest was not properly finished (main reason is timeout). |
We observed some fake AddOn test failures in at least two recent PRs (#29347 two times, #29387 )
eg.
Surprising, cms-bot does not show which AddOn tests are failing.
As a reference in #28936 , on March 6, cms-bot caught correctly the AddOn test failures, showing the failing tests.
Eg.
#28936
The text was updated successfully, but these errors were encountered: