Hi,
We have recently been working hard to separate the buildbot logic that
runs our talos jobs on tbpl to its own separate script (using
mozharness). [1][2]
This has the advantage of permitting anyone (specially the a-team) to
adjust how our harnesses run talos inside of our infrastructure without
having to set up buildbot (which is what currently runs our talos jobs).
This also permits anyone to run the jobs locally in the same manner as
Releng's infrastructure. This also allows for further development and
flexibility on how we configure the jobs we run.
Initially, we will enable it on the try server today to see
production-like load. So far, it's been looking great on Cedar. [3]
The only gotcha is that there will be a small performance hit for the ts
tests that we are willing to take. [4]
There's one thing to do on your part if you want to not have failing
*talos* jobs on the try server, make sure that the changeset
3d1c2ca7efe8 is in your local checkout [5][6]. If you have updated your
repo from m-i by Friday 12th at 10:19AM PDT you should be good to go.
Once we get a couple of days worth of load on the try server and see
nothing new we will go ahead and enable it for every m-c based repository.
If you have any questions/concerns please write a comment on bug 713055.
Best regards,
Jason & Armen
Release Engineering
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=713055
[2] https://developer.mozilla.org/en-US/docs/Mozharness_FAQ
[3] https://tbpl.mozilla.org/?tree=Cedar&jobname=talos
[4] https://bugzilla.mozilla.org/show_bug.cgi?id=802801#c10
[5] http://hg.mozilla.org/integration/mozilla-inbound/rev/3d1c2ca7efe8
[6] http://hg.mozilla.org/mozilla-central/rev/3d1c2ca7efe8
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
