On 04/03/2013 06:33 PM, Ehsan Akhgari wrote:
On 2013-04-03 9:10 PM, Clint Talbert wrote:
On 4/3/2013 4:28 PM, Joshua Cranmer 🐧 wrote:
On 4/3/2013 4:31 PM, Kartikaya Gupta wrote:
For what it's worth, I do recall there being release engineering talk
about some sort of "autoland" feature (which would automatically land
any patch that passed try or something), and I recall (my memory may
just be playing tricks on me) that it got to the prototyping phase but
was shelved because the "merge" part was too difficult/impossible. A
comment from anyone who worked on this would be helpful.
Actually, the issues I am aware of were around a security issue and a
person-resource issue to complete the work. The security issue has been
fixed, and this current quarter (Q2), Release Engineering and the
Bugzilla team are planning to team up to finish the work here.
One of the really nice things we can do with autoland is schedule
non-time-sensitive patches for landing when the tree is quieter, like
1AM pacific.
But my point is that autoland is coming back and we hope to have it on a
BMO instance near you soon.
\o/
Do you know who's going to work on this? I'd like us to avoid this
work if it's intended for anything more than pushing to try unless we
have a solution to the two problems I mentioned in my other email.
Thanks!
Ehsan
So I'm not sure I understand:
> 1. This will incur a significant increase in our infra resource usage
since all of these patches have to do a full try run. We simply cannot
afford that in today's world where we're struggling against wait times
and infrastructure overload.
If we push to e.g. inbound, we still run all the tests + builds. My
understanding was the whole point was to avoid the double run (running
all/most tests/builds on try and then landing on e.g. inbound where
they're all run again). Is the concern the overhead pushing to try?
autoland or no, that is a problem indeed. If not, I don't really
understand the concern here.
2., all of our damn intermittent, is indeed a concern :( And of course
not just for this reason: tons of human and often machine time is lost
to them. I can imagine this being addressed for autoland, but will
leave ctalbert or others to comment as to plans there since I'm sure
they've thought of everything I could propose right now (and then some).
Obviously the best solution is to kill all the orange, but ... yeah
Jeff
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
