Skip to content

Conversation

@marcdumais-work
Copy link
Contributor

@marcdumais-work marcdumais-work commented Jan 31, 2024

When running the tests locally, the current 'html' reporter is fine. But I've been confused with it in CI logs where there was a failure, presumably a silent retry and finally a report of the tests passing.

I think in CI we would have more clarity with an alternate reporter. Let's try 'list'. If it does not work well we can fall-back on the simple 'dot'.

When running the tests locally, the current 'html' reporter is fine.
But I've been confused with it in CI logs where there was a failure,
presumably a silent retry and finally a report of the tests passing.

I think in CI we would have more clarity with an alternate reporter.
Let's try 'list'. If it does not work well we can fall-back on the
simple 'dot'.

Signed-off-by: Marc Dumais <[email protected]>
@marcdumais-work
Copy link
Contributor Author

marcdumais-work commented Feb 1, 2024

We got lucky: we got the case I was trying to improve in the latest CI run (a testcase failure followed by a report of overall success):

With the new reporter, we can see just above a report of the test running, aiding in interpreting what has happened exactly:
https://github.com/eclipse-cdt-cloud/vscode-trace-extension/actions/runs/7742470139/job/21111681510?pr=198#step:14:15

@marcdumais-work
Copy link
Contributor Author

I think maybe the (default?) timeout of 5000ms might be a little short

@marcdumais-work marcdumais-work changed the title [CI] Use 'list' Playwright reporter [CI] Use 'list' Playwright reporter, use longer timeout Feb 1, 2024
Timeouts with the default, rather short 5000ms timeout can be observed
semi-regularly.

Signed-off-by: Marc Dumais <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants