-
Notifications
You must be signed in to change notification settings - Fork 742
tests: use the same browser instance across tests and better use explicit resource management #2901
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
fe24c7b
test: use the same browser instance across tests
iuioiua 72c973e
work
iuioiua 3049b2f
tweak
iuioiua a3c24a1
work
iuioiua 8364d95
tweak
iuioiua 8a62637
Merge branch 'main' into browser-instance
iuioiua beaeea3
fix
iuioiua 754bed1
Merge branch 'main' into browser-instance
iuioiua ccc4286
Merge branch 'main' into browser-instance
iuioiua 52c3a53
Merge branch 'main' into browser-instance
marvinhagemeister File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://github.com/lino-levan/astral?tab=readme-ov-file#no-usable-sandbox-with-user-namespace-cloning-enabled
I would recommend removing app armor instead of enabling --no-sandbox
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the advantage? Genuine question.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or do you think that's the issue here?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The biggest reason is it cleans up the codebase. I've heard of really obscure bugs not being caught in CI because of
--no-sandbox, but I've never seen one myself so take that with a grain of salt.