[Tests] Fix functional tests Turbo (Chrome 137 & dev-tools) #2873
Conversation
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
Kocal
force-pushed
the
turbo/fix-tests-provided-cwd
branch
from
27044a4 to
8f26f14
Compare
Kocal
force-pushed
the
turbo/fix-tests-provided-cwd
branch
2 times, most recently
from
8c96593 to
36b43a6
Compare
Kocal
changed the title
Kocal
force-pushed
the
turbo/fix-tests-provided-cwd
branch
from
4b28494 to
9b42f13
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Maybe I went to quick on #2867, maybe using
<server>instead of<env>matters...EDIT: it seems that Turbo functional tests were broken since few weeks / months now, because of Chrome 137, see symfony/panther#675.
Passing
PANTHER_DEVTOOLS=0worked like a charm.