Revert of Use CLOCK_REALTIME_COARSE when available.

Revert of Use CLOCK_REALTIME_COARSE when available. (patchset #1 id:1 of https://codereview.chromium.org/1151283005/)

Reason for revert:
[Sheriff] This leads to several failures in chromium and blocks our roll:
https://codereview.chromium.org/1154363002/

Bisect (https://codereview.chromium.org/1152553004/) points to this CL.

Please add the failing chromium trybot on a reland of this CL.

Original issue's description:
> Use CLOCK_REALTIME_COARSE when available.
>
> On systems that have CLOCK_REALTIME_COARSE with good enough resolution,
> we can avoid making a system call to get the current time; it's serviced
> from the vDSO.
>
> This is v2 of the patch.  v1 can be found at [0] but was reverted in [1]
> because of Chromium sandbox restrictions.  The necessary changes have
> been applied upstream in [2].
>
> [0] https://codereview.chromium.org/1125003002
> [1] https://codereview.chromium.org/1130083003
> [2] https://codereview.chromium.org/1133653002
>
> BUG=
> LOG=N
>
> Committed: https://crrev.com/28cea2b749f24ba33e6e0c8e343dd0d6258ee302
> Cr-Commit-Position: refs/heads/master@{#28639}

TBR=jochen@chromium.org,bmeurer@chromium.org,ben@strongloop.com
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=

Committed: https://crrev.com/9cc183d8996948d71660a8b1dbddfeaee2f79ada
Cr-Commit-Position: refs/heads/master@{#28656}

[Michael Achenbach, 2015-05-27 14:05:25]

Created Revert of Use CLOCK_REALTIME_COARSE when available.

[commit-bot: I haz the power, 2015-05-27 14:05:39]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1154783003/1

[commit-bot: I haz the power, 2015-05-27 14:05:54]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-05-27 14:06:10]

Patchset 1 (id:??) landed as
https://crrev.com/9cc183d8996948d71660a8b1dbddfeaee2f79ada
Cr-Commit-Position: refs/heads/master@{#28656}

[noordhuis, 2015-05-27 15:42:46]

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?

[noordhuis, 2015-05-28 17:59:54]

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?

[Jakob Kummerow, 2015-06-01 11:30:58]

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 fi

[Jakob Kummerow, 2015-06-01 11:31:42]

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.

[noordhuis, 2015-06-01 12:20:19]

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.

[Michael Achenbach, 2015-07-02 13:55:33]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1217543005/ by machenbach@chromium.org.

The reason for reverting is: Experimental reland.