Justin Wood wrote:
We also have had developer confusion around this change (and some relatively
minor unforseen problems with the patch, detailed in bug) that caused sheriffs
to ask for this to be backed out.
If you omit part of the try syntax then you get a default set of
options, but as
Thanks John, this looks like it strikes a good balance between reducing
tegra load and getting false-positives in try runs.
Just for anybody following along though, it looks like bug 915465 (which
deployed this change) is still in flux so things may have not completely
settled yet. See also
hi kats (cross-posting to dev-b2g);
tl:dr; we think all is ok again, details below. To avoid this happening
again this week, we're changing tryserver to reduce the number of
Android-tests-run-on-tegra-by-default. If you specifically want tegra
testing on tryserver, you will need to state
Earlier today the backlog on Android build jobs was on the order of
1300. It seems to be coming down a little now but for a while there I
was worried it was going to grow unboundedly. Try jobs from over 10
hours ago still have pending jobs - as I'm sure you all know, having a
10-hour
Do we know why it's that much backed up? I started noticing
it yesterday. Is it because of lots of inbound pushes? lots
of try pushes? Lots of clobbering? Lots of tests?
Jim
On 9/11/13 5:31 PM, Kartikaya Gupta wrote:
Earlier today the backlog on Android build jobs was on the
order of 1300. It
quite possibly we don't need all those jobs running on tegras. I don't know of
a bug in the product that has broken on either the tegra or panda platform but
not the other.
Joel
___
dev-platform mailing list
dev-platform@lists.mozilla.org
On Wed, Sep 11, 2013 at 04:39:37PM -0700, jmaher wrote:
quite possibly we don't need all those jobs running on tegras. I
don't know of a bug in the product that has broken on either the tegra
or panda platform but not the other.
Off the top of my head:
- I have broken one but not the other
Fixing bugs like bug 884972 would probably help quite a bit. Also posting
patches with checkin info and marking the bug with checkin-needed so the
work lands with other patches. I always try to do this with simple front end
patches.
Jim
Kartikaya Gupta kgu...@mozilla.com wrote in message
2013/9/11 Mike Hommey m...@glandium.org
On Wed, Sep 11, 2013 at 04:39:37PM -0700, jmaher wrote:
quite possibly we don't need all those jobs running on tegras. I
don't know of a bug in the product that has broken on either the tegra
or panda platform but not the other.
Off the top of my
hi kats (cross-posting to dev-b2g);
tl:dr; we think all is ok again, details below. To avoid this happening
again this week, we're changing tryserver to reduce the number of
Android-tests-run-on-tegra-by-default. If you specifically want tegra
testing on tryserver, you will need to state that
10 matches
Mail list logo
