Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Playwright] Problem with playwright trace #11648

Closed
amrita-shrestha opened this issue Sep 25, 2024 · 4 comments · Fixed by #11659
Closed

[Playwright] Problem with playwright trace #11648

amrita-shrestha opened this issue Sep 25, 2024 · 4 comments · Fixed by #11659
Assignees

Comments

@amrita-shrestha
Copy link
Contributor

Describe the bug

Traces generated when test scenarios fail on retry should give the proper file name.
Build : https://drone.owncloud.com/owncloud/web/47874/14/16
Due to some reason trace file named as *.zip. Recent changes done on this PR #11640

npx playwright show-trace https://cache.owncloud.com/public/owncloud/web/47874/tracing/\*.zip

Screenshot from 2024-09-25 13-13-03

@amrita-shrestha amrita-shrestha self-assigned this Sep 25, 2024
@amrita-shrestha amrita-shrestha changed the title [Playwright] Generate trace with proper name [Playwright] Problem with playwright trace Sep 26, 2024
@amrita-shrestha
Copy link
Contributor Author

amrita-shrestha commented Sep 26, 2024

Finding
Failed because trace build on retry stored on different location changes done on this PR bring that changes #11640
image

actually, it should be
Screenshot from 2024-09-26 10-11-35

@saw-jan
Copy link
Member

saw-jan commented Sep 26, 2024

Failed because trace build on retry stored on different location changes done on this PR bring that changes #11640

storing tracing reports in different location is expected. But the problem here is that the reportTracing config changes to false and the moving of failed tracing reports to the actual folder doesn't occur.

@saw-jan
Copy link
Member

saw-jan commented Sep 26, 2024

I will fix this in PR #11659 if your PR is not ready

@saw-jan
Copy link
Member

saw-jan commented Sep 26, 2024

The problem was not in PR #11640 but in the first PR #11571 where I tried to collect only the reports of failing tests. In the PR, the reports were not filtered correctly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants