action #157543
Updated by okurz about 2 months ago
## Observation
https://app.circleci.com/pipelines/github/os-autoinst/openQA/13196/workflows/ddb935c7-31dd-4beb-877c-25ef1e703b4d/jobs/123228
```
[14:08:28] t/ui/23-audit-log.t ........................ 12/?
# Failed test 'most rows filtered out when searching for table create events'
# at t/ui/23-audit-log.t line 40.
# got: '8'
# expected: '3'
# Looks like you failed 1 test of 22.
[14:08:28] t/ui/23-audit-log.t ........................ 13/?
# Failed test 'clickable events'
# at t/ui/23-audit-log.t line 152.
[14:08:28] t/ui/23-audit-log.t ........................ 14/? # Looks like you failed 1 test of 14.
[14:08:28] t/ui/23-audit-log.t ........................ Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/14 subtests
```
## Acceptance criteria
* **AC1:** Statistically significant stable test execution of t/ui/23-audit-log.t
## Suggestions
* DONE: ~~Find out current error rate locally~~ not reproducible
* Find out current error rate locally with coverage enabled as this is possibly more likely to reproduce problems we see in circleCI
* Consider recent javascript stack related updates which might impact that
* Identify the specific point of sporadic failure source by debugging the unit test and executed code itself
* Apply changes to the test code to make it more robust. Possibly similar as in other UI tests in the past with some means of synchronization
* Verify that the test is stable again