mirror of
https://github.com/opnsense/src.git
synced 2026-02-11 23:06:12 -05:00
0599d2a1c5
I very occasionally see test failures caused by the total CPU time being several milliseconds under 3s. The test runs "limits -t 3 time <busy loop>" and verifies that the reported time elapsed is at least 3s (and not too much more). In particular, any time spent executing time(1) itself is counted against the limit but not recorded in the output. I think it makes more sense to reverse the order, so that the CPU time limit is not applied to time(1) itself. This also resolves the test failures I was seeing, which were reproducible only under load (i.e., running many tests in parallel). MFC after: 2 weeks Sponsored by: Klara, Inc. (cherry picked from commit 0f63c4af5e4761680550b0aa08cc96f52076c08c) |
||
|---|---|---|
| .. | ||
| tests | ||
| limits.1 | ||
| limits.c | ||
| Makefile | ||
| Makefile.depend | ||