[FIX] core: improve ready code warning timeout #33478
Conversation
The ready code warning timeout of 2 seconds can be confusing since it is triggered just after the 2 seconds. We can log this message at the end in order to give the real timeout.
|
@robodoo r+ |
|
Staging failed: ci/runbot on e07de51d34d5557371c1d0781e2d3c7a1fd485fe (view more at http://runbot.odoo.com/runbot/build/522867) |
The ready code warning timeout of 2 seconds can be confusing since it is triggered just after the 2 seconds. We can log this message at the end in order to give the real timeout. closes odoo#33478 Signed-off-by: Christophe Monniez (moc) <moc@odoo.com>
|
Looks like the default cpu-limit of test all was a little to low for enterprise. Changed it from 3600 to 5000. |
|
Staging failed: timed out (>120 minutes) |
|
seems that the CLA status was not sent to the mergebot ! |
|
@robodoo retry |
The staging branches have the config "Default no run". I added the cla check to this config. I hope it will be taken into the current build since step all is not finished. |
|
Unfortunately the community build was already finished. I'm trying a manual rebuild but if the mergebot timeout before the end we may need anoter retry. |
|
Staging failed: timed out (>120 minutes) |
|
@robodoo retry |
robodoo
added
CI 🤖
|
Merged, thanks! |
|
Finally! |
The ready code warning timeout of 2 seconds can be confusing since
it is triggered just after the 2 seconds. We can log this message
at the end in order to give the real timeout.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr