Re: [dev-servo] mac3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/07/2015 11:40 AM, Ms2ger wrote: > Hi all, > > The last mac3 run > () took 1 hrs, 13 > mins, 57 secs, of which it spent 45 minutes compiling. As long as > we have test-css running on linux (where c

Re: [dev-servo] mac3

I’d prefer that we only move things to nightly that will not cause a tree closure in the event of failure. e.g., performance tests, valgrind runs, fuzzing, etc. If we also put CSS / layout tests or other things we decide are “too slow” onto nightly builders, we’ll have the worst of both worlds

Re: [dev-servo] mac3

I think we should be removing mac3 builds as well. I'll repeat what I proposed in IRC: We can instead have a "nightly" set of builds, for stuff like this which would be too much to run every build. This can include testing release builds, mac3, and future valgrind/android tests. If something break

[dev-servo] mac3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, The last mac3 run () took 1 hrs, 13 mins, 57 secs, of which it spent 45 minutes compiling. As long as we have test-css running on linux (where css and wpt together don't make to 30 minutes), doe

[dev-servo] Allowing occasional rollups?

What's our stance on rollups? I know they mess up history, but should it be okay to do them when the queue is backed up? At the moment our build rate and PR rates are roughly equal -- fine for most situations, but if the queue gets backed up it stays that way. IMO having an occasionally less line