Saturday, July 5, 2025
1 change · saas-18.3
Resolved issues and error corrections
A frequently failing automated test for editing chatter messages has been temporarily skipped to reduce false failures in Odoo's test pipeline. This does not change customer-facing behavior, but helps keep build results reliable while a deeper technical race condition is investigated.
Original PR description
The test "Can edit message comment in chatter" fails often non-determinically on runbot. This happens because this test heavily uses the edit message feature, which has client-side code receiving…
The test "Can edit message comment in chatter" fails often non-determinically on runbot. This happens because this test heavily uses the edit message feature, which has client-side code receiving store data from both RPC returns and bus notifications. When CPU load is high which happens frequently on runbot, test shows race-condition where bus notifications are received much later than RPC return part and thus discuss state becomes wrong by having outdated data. This is an architectural issue that takes time to solve, so this test is skipped in the meantime. Note that while the problem occurs quite a lot on runbot in HOOT tests, in practice this happens quite rarely: bus notifications should be heavily throttled. Also HOOT test fails because of unfortunately case of receiving exactly outdated message body data before starting message edition. When message is being edited, any following store data with change of message body is ignored because the text in composer is intended to not change while editing the message. Kinda fixes runbot 227618 Forward-Port-Of: odoo/odoo#217501