The minimum values don't reflect our detection capabilities, leading to undercount. In addition, the times recorded are also incorrect.
$ w3m -dump -cols 200 'https://search.ci.openshift.org/?search=sig-api-machinery.*should+be+available&maxAge=336h&context=1&type=junit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job' | grep -E 'ms| 0s '
No results found.
Per PR changes, from above search results, no longer see any time representation at the millisecond level and zero second in CI test results in past 13 days, so move the bug VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.