This bug seems to be accumulating stars for random unrelated `TEST-UNEXPECTED-TIMEOUT` failures for TSAN runs on esr115, e.g. in comment 127 and comment 135. CosminS, do you know why that's happening, and could you adjust things such that we stop starring these sorts of failures as being this bug? This bug here wasn't about timeouts; it was specifically about random aborts where we were hitting `ThreadSanitizer failed to allocate [giant number] bytes at address [something]` in the log. This bug was is fixed in 113 and beyond, so any failures in ESR115 would be surprising (which is why these reports caught my attention). (One of the failures from comment 135 seems to have really been bug 1836972; I didn't look at the other one there or the ones from comment 135, but presumably we want to re-annotate those with their correct bugs, or file new bugs if appropriate.)
Bug 1770595 Comment 136 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This bug seems to be accumulating stars for random unrelated `TEST-UNEXPECTED-TIMEOUT` failures for TSAN runs on esr115, e.g. in comment 127 and comment 135. CosminS, do you know why that's happening, and could you adjust things such that we stop starring these sorts of failures as being this bug? This bug here wasn't about timeouts; it was specifically about random aborts where we were hitting `ThreadSanitizer failed to allocate [giant number] bytes at address [something]` in the log. This bug was is fixed in 113 and beyond, so any failures in ESR115 would be surprising (which is why these reports caught my attention). (One of the failures from comment 135 seems to have really been bug 1836972; I didn't look at the other one there or the ones from comment 127, but presumably we want to re-annotate those with their correct bugs, or file new bugs if appropriate.)
This bug seems to be accumulating stars for random unrelated `TEST-UNEXPECTED-TIMEOUT` failures for TSAN runs on esr115, e.g. in comment 127 and comment 135. CosminS, do you know why that's happening, and could you adjust things such that we stop starring these sorts of failures as being this bug? This bug here wasn't about timeouts; it was specifically about random aborts where we were hitting `ThreadSanitizer failed to allocate [giant number] bytes at address [something]` in the log. This bug was is fixed in 113 and beyond, so any failures in ESR115 would be surprising (which is why these reports caught my attention). (One of the two failures from comment 135 seems to have really been bug 1836972; I fixed that annotation, but I didn't look in detail at the other one from comment 135, or at the ones from comment 127, except to check that they don't have `failed to allocate` in their log to be sure they're not this issue here. Presumably we want to re-annotate those with their correct bugs, or file new bugs if appropriate.)