This message was deleted.

Could you please provide a specific example? The only limitation here is that Build Failure Analytics only indexes exceptions and messages, not full console logs of builds. Otherwise, it should match unless there are subtle differences in the message where you may need to add a wildcard

*

(like globbing)

Hi Eric! Sure, I can provide a more specific example 🙂 I didn’t want to be verbose for the problem declaration. Indexing just the error messages makes sense. In this case I believe they keyword it’s part of it. And yes, I am using the wildcards. The common error message that appears consistently in all of these builds is

Structure needs cleaning

and I am querying simply for

*cleaning*

(see first screenshot for the search results). Second screenshot is a failed build that it appears in the search (is the first result in previous screenshot). It reported different failures, and the 10th is the one that interest us with the text as part of it. The 3rd screenshot is one of the reports that we detected not appearing in the search. The keyword appears there as part of the failure message. It also appears further down as part of the stacktrace (it didn’t fit in one screen, so sharing a 4th screenshot as continuation of this report). Let me know if you need also a support bundle of any of these.

Hey Roldan. I'm not sure if a support bundle will help, but if you provide scan-dumps for both build scans we could try to reproduce the issue locally. (A scan-dump lets us upload the scan to our internal GE instance).

Sent! Thank you very much! 😊

Got it, thanks. We'll let you know if we can reproduce what you're seeing.

awesome!

Thank you for the additional details Roldan. There is a limitation I failed to mention: the search functionality only indexes the first 1000 chars of exceptions+messages to prevent very large exceptions from inhibiting performance. I'm afraid this is not tunable in Gradle Enterprise at the moment, so I cannot offer an easy solution to allow you to search patterns which would match middle/end of long messages.

Ah! That’s definitively the issue! In the report that doesn’t apear in the search, the keyword appears in the character 2060 of the error message