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

Fix the link for issue5939.pdf #19545

Merged
merged 1 commit into from
Feb 24, 2025

Conversation

hecerinc
Copy link
Contributor

Web archive no longer has the revision for the saved PDF referenced in that test case, so this updates that link to a more recent revision to enable the tests to run on a clean clone.

Web archive no longer has the revision for the saved PDF referenced in
that test case, so this updates that link to a more recent revision to
enable the tests to run on a clean clone.
Copy link
Collaborator

@Snuffleupagus Snuffleupagus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that this can't be (easily) tested on the bots, since they already have the file cached.
Hence I've done the following locally, with this patch applied:

  • Temporarily moved the issue5939.pdf file to another folder, to trigger re-downloading.
  • Ran gulp browsertest --noChrome -t issue5939, to trigger downloading of the file and run reference tests.
  • Ensured that the test passed and there were no warnings/errors about hash mismatches, confirming that the "new" file is identical to the previous one.

r=me, thank you.

@Snuffleupagus Snuffleupagus merged commit c478483 into mozilla:master Feb 24, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants