-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Enable support for running the test harness in Safari. #25499
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
Open
juj
wants to merge
10
commits into
emscripten-core:main
Choose a base branch
from
juj:safari_harness
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+100
−29
Open
Changes from 9 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
5d0adb5
Enable support for running the multithreaded test harness in Safari.
juj 66a595d
Add Safari version parsing to gate hacks to older versions
juj 8d9b47a
Add comment
juj 0da91d1
Update cutoff
juj fa3de84
Update hack
juj 30b2eeb
Address review
juj 2b41554
Make browser test suite pass on Safari
juj f0c11e7
Add one more
juj a827fc0
Merge branch 'main' into safari_harness
juj 5165a1b
Remove get_safari_version
juj 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
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
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
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.
How about
get_version_from_macos_app_dir(or something like that?)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.
Oh wait.. this function looks like it not actually used?
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.
Err, I was hoping you wouldn't notice :)
I used this function in the initial version of this PR. Initially I couldn't figure out why old Safari was failing some random tests. And it amounted to being that missing HTTP caching header
Vary: *that was causing the failures.So I could then remove the use of the version check.
But I have plans to use that Safari version check soon more once I get to test more coverage of the tests in different Safari versions. Instead of a
@no_safari('reason')annotation, I would like to annotate tests with@no_safari_older_than(XXYYZZ, 'reason')so that the test skips are not that blunt and oblivious to the version. That way they can naturally evolve out when minimum supported Safari version evolves.If you'd like, I can also reintroduce that function in a later PR that actually adds uses of such pattern. (I am planning to introduce a symmetric
get_firefox_version()function as well, and instead of@no_firefox, to have@no_firefox_older_thanchecks)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.
Can maybe run something like
browser-binary --versionin all cases? Then the same code work everywhere?Lets remove this PR since it also introduces that new plist import thing.
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.
Its a shame the new
vulturecheck isn't able to be sure about this code being dead so it doesn't fail in the CI step :(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.
ok, removed