On 2015/06/01 11:31:42, Jakob wrote:
On 2015/05/28 17:59:54, noordhuis wrote:
> On 2015/05/27 15:42:46, noordhuis wrote:
> > On 2015/05/27 14:05:25, Michael Achenbach wrote:
> > > Created Revert of Use CLOCK_REALTIME_COARSE when available.
> >
> > Okay, so what's the next step? The necessary changes landed upstream
so
it
> > sounds like the CI is still using an old version of the sandbox;
either
that
> or
> > it's using a more restricted blacklist.
> >
> > Should I resubmit my CL a week or two from now or is there someone I
can
prod
> > about the CI infrastructure?
>
> Ping. Can I get some pointers, please?
From the failings bots' output, you can see what revision they used, so
you
can
verify whether your patch was in there. If it was, it's obviously not
working
or
not enough or whatever -> fix it. If it wasn't, then obviously waiting
(and
maybe checking what revisions passing try jobs are currently using) is a
valid
strategy.
TL;DR: figure out what went wrong and fix it. As always.
You make it sound easy. The reason I bring it up is that last time there
was
talk of needing to manually update the sandbox.
For the record, the patch is there but I can't glean from the output what
sandbox policy the failing build bots are using. The fact that the other
linux
build bots work suggests that it's at least working some of the time.
Some guidance would be appreciated. Remember I'm not a Googler; what may be
crystal clear to you, is mostly opaque and byzantine to me.
https://codereview.chromium.org/1154783003/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
