Hello again,
I'm wrapping up some high priority work from Q4 and I should be able to start
looking into this.
regards,
Armen
On Wednesday, 23 December 2015 11:15:07 UTC-5, Kartikaya Gupta wrote:
> For the record it seems like even if adding new jobs via TH fails, the
> old try-extender tool at
Mark, this was added as one of the use cases:
https://mozilla-ci-tools.readthedocs.org/en/latest/use_cases.html#case-scenario-3-retrigger-an-intermittent-job-on-a-changeset-until-hit
It requires adding monitoring of jobs through Pulse and being able to inspect
the structure log for matching the t
Hi Gijs,
I worked last quarter on a project that allows us to trigger jobs accross
revision ranges in various ways, trigger jobs multiple times or even create the
missing builds to trigger a test job.
https://mozilla-ci-tools.readthedocs.org/en/latest
Some of the use cases:
https://mozilla-ci-to
Re-sending due to bug https://bugzilla.mozilla.org/show_bug.cgi?id=1108698
My apologies if you're getting this many times!
tl; dr; if you want to test mozharness changes on try you can do so by
modifying testing/mozharness/mozharness.json [1] and pointing it to your
own repository. This currently
Hello all,
After disabling the Win7 tests on those b2g18 trees, I was told by the
sheriffs that the MacOS X testing is redundant.
Again:
* these are repositories where only security fixes are being landed
* this is not about b2g26
* we have testing coverage through Linux, Linux64, Android Noion +
5 matches
Mail list logo
