Over in bug 480413, Alice has implemented a Tshutdown test so that we
can know about things which make shutdown terrible, and a happy side
effect of this is that we would no longer be counting on a timer to
guess about shutdown, we'd actually be watching and measuring it, so
the orange should go away.
That patch is reviewed and ready, but it means scheduled downtime to
push it to production. Obviously no one wants scheduled downtime
during a freeze. But no one wants almost perma-orange trees either.
Right now, comments in the bug suggest Alice and John are waiting
until post-freeze to push it, which is probably prudent. But I wanted
to bring it up here in case anyone wanted to make an impassioned plea
to have it happen sooner. Because I sort of want it to, but can grit
my teeth through a week more orange if that's going to be safest for
the tree.
How does it make YOU feel?
Johnathan
---
Johnathan Nightingale
Human Shield
joh...@mozilla.com
cheers,
mike
> _______________________________________________
> dev-tree-management mailing list
> dev-tree-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-tree-management
Cheers,
Shawn
I also hacked into the Tshutdown patch that if a single test fails it
should continue on with the rest of the tests. So if the Ts failure
persists (and I hope that it doesn't) we would still get Tp/Tdhtml/etc
test results from that build.
I would expect this to take on the order or 3-4 hours to land, just to
be sure that everything is looking good and we haven't introduced any
regressions.
alice.
Yeah, I'm on board here too. Let's do it Monday, as early as we can?
Mike