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
On 9/12/2014 7:52 AM, Gijs Kruitbosch wrote:
Because I've been working on a few of them and here's what I think would
make them a lot easier to fix, and therefore improve our test coverage
and make sheriffs much happier
When I look at oranges, I typically push some diagnostics to try and
retri
Thanks Andrew.
Gijs, if you'd like to see the notes we took in PDX on this topic,
they're here: https://etherpad.mozilla.org/ateam-pdx-intermittent-oranges
Feel free to add more ideas and comments. We're currently working on
our Q1 plan and will see how many of these things we can fit in the
We had a session on intermittents in PDX. Additionally we (the ateam)
have had several brainstorming sessions prior to the work week. I'll try
to summarize what we talked about and answer your questions at the same
time in-line.
On 08/12/14 03:52 PM, Gijs Kruitbosch wrote:
1) make it easier t
Because I've been working on a few of them and here's what I think would
make them a lot easier to fix, and therefore improve our test coverage
and make sheriffs much happier
1) make it easier to figure out from bugzilla/treeherder when and where
the failure first occurred
- I don't want to k
6 matches
Mail list logo
