Build baron log analyzer failed to extract unittest failures

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • DevProd Services & Integrations
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The build baron log analyzer failed to extract log lines related to unit test failure.

      E.g. for this BFG I would have expected the log analyzer to extract the log line starting with: 

      [2025/10/09 02:33:41.173] {"t":{"$date":"2025-10-09T06:27:19.392+00:00"},"s":"I",  "c":"TEST",     "id":4680100, "ctx":"main","msg":"FAIL","attr":{"test":"TestMultipleStreamsFast","type":"TestAssertionFailureException","error":"Expected: !(_executor->hasTasks()) @src/mongo/db/modules/atlas/src/disagg_storage/log_server_manager_test.cpp:424","extra":"BACKTRACE: ...

      This is a serious problem because without a proper log failure message we can't create auto-closing rules that match the specific error.

      This has a direct impact on developer productivity.

            Assignee:
            Unassigned
            Reporter:
            Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: