[PATCH] Loosen the limits of time/tst-cpuclock1.

[Florian Weimer]

* Stefan Liebler via Libc-alpha:

> Starting with the commit 04deeaa9ea74b0679dfc9d9155a37b6425f19a9f "Fix
> time/tst-cpuclock1 intermitent failures" (2020-07-11), this test fails
> quite often on s390x/s390 with one/multiple of those: "before - after"
> / "nanosleep time" / "dead - after" ourside reasonable range.

How much value do these cpuclock tests actually have?  Maybe we should
just remove them, given that their test objective is so difficult to
model in current execution environments.

Maybe we could measure clock discontinuities on the CPU-burning thread
and detect CPU stealing this way.  But I'm not sure if this would be
worth it.

Thanks,
Florian