I wonder if we could make a single link in orangefactor that would give you the range of TEST-UNEXPECTED-FAIL messages to help with this. I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1339937 to track this, Please do offer suggestions/use cases for that specific bug.
On Tue, Feb 14, 2017 at 5:24 PM, L. David Baron <[email protected]> wrote: > On Tuesday 2017-02-07 21:33 -0800, Bill McCloskey wrote: > > I spent about an hour tonight trying to debug a test failure, and I'm > > writing this email in frustration at how difficult it is. It seems like > the > > process has actually gotten a lot worse over the last few years (although > > it was never good). Here's the situation I ran into: > > Another aspect of debugging test failures that has gotten worse > recently: > > * If you have an intermittent that's actually affecting the tree, > it's become harder to see the range of TEST-UNEXPECTED-FAIL > messages that are occurring. These used to be present in the > comments that tbplbot made on bugs, but now it requires following > a link for each log in the orangefactor interface. (Having this > range was useful to me today in fixing 1159532, although clicking > through to 6 logs was sufficient to help understand the problem.) > > This also makes it much harder to tell if bugs are being > mis-classified (e.g., two different problems being starred into > one bug). > > (I thought the point of structured logging was to make it easier to > get this sort of data.) > > -David > > -- > 𝄞 L. David Baron http://dbaron.org/ 𝄂 > 𝄢 Mozilla https://www.mozilla.org/ 𝄂 > Before I built a wall I'd ask to know > What I was walling in or walling out, > And to whom I was like to give offense. > - Robert Frost, Mending Wall (1914) > _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
