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

[api-minor] Re-factor how the useWorkerFetch option is used internally #19537

Merged
merged 2 commits into from
Feb 22, 2025

Conversation

Snuffleupagus
Copy link
Collaborator

With the recently added OpenJPEG no-wasm fallback we need to send the wasmUrl option to the worker-thread regardless of the value of the useWorkerFetch option, since the fallback won't work if we don't have a URL to import it from.
For consistency the code is re-factored to always send the factory-urls to the worker-thread, and simply check the useWorkerFetch option there instead.

Also, as a follow-up to PR #19525, introduce a new useWasm option that can be used in e.g. browser-tests to forcibly disable WebAssembly usage.

@Snuffleupagus Snuffleupagus added image-jpx release-blocker Blocker for the upcoming release labels Feb 22, 2025
With the recently added OpenJPEG no-wasm fallback we need to send the `wasmUrl` option to the worker-thread *regardless* of the value of the `useWorkerFetch` option, since the fallback won't work if we don't have a URL to `import` it from.
For consistency the code is re-factored to always send the factory-urls to the worker-thread, and simply check the `useWorkerFetch` option there instead.

Also, as a follow-up to PR 19525, introduce a new `useWasm` option that can be used in e.g. browser-tests to forcibly disable WebAssembly usage.
@Snuffleupagus
Copy link
Collaborator Author

/botio unittest

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Linux m4)


Received

Command cmd_unittest from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.241.84.105:8877/e78f9edd3ce2607/output.txt

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Windows)


Received

Command cmd_unittest from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.193.163.58:8877/c6dfd3a7c1abf8e/output.txt

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Linux m4)


Success

Full output at http://54.241.84.105:8877/e78f9edd3ce2607/output.txt

Total script time: 2.35 mins

  • Unit Tests: Passed

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Windows)


Failed

Full output at http://54.193.163.58:8877/c6dfd3a7c1abf8e/output.txt

Total script time: 7.60 mins

  • Unit Tests: FAILED

@Snuffleupagus
Copy link
Collaborator Author

/botio browsertest

@Snuffleupagus
Copy link
Collaborator Author

/botio integrationtest

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Windows)


Received

Command cmd_integrationtest from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.193.163.58:8877/41fc9d8a1bae7e9/output.txt

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Linux m4)


Received

Command cmd_integrationtest from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.241.84.105:8877/158a78cc4ee1853/output.txt

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Linux m4)


Failed

Full output at http://54.241.84.105:8877/158a78cc4ee1853/output.txt

Total script time: 11.74 mins

  • Integration Tests: FAILED

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Windows)


Failed

Full output at http://54.193.163.58:8877/41fc9d8a1bae7e9/output.txt

Total script time: 28.62 mins

  • Integration Tests: FAILED

After PR 19392 we're only invoking this method *once* per document, hence the early-return branch shouldn't be necessary any more.
@mozilla mozilla deleted a comment from moz-tools-bot Feb 22, 2025
@mozilla mozilla deleted a comment from moz-tools-bot Feb 22, 2025
@mozilla mozilla deleted a comment from moz-tools-bot Feb 22, 2025
@mozilla mozilla deleted a comment from moz-tools-bot Feb 22, 2025
@Snuffleupagus
Copy link
Collaborator Author

/botio browsertest

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Windows)


Received

Command cmd_browsertest from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.193.163.58:8877/4ca3ccdd208991b/output.txt

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Linux m4)


Received

Command cmd_browsertest from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.241.84.105:8877/c7bdb9d3b1c73a2/output.txt

Copy link
Contributor

@calixteman calixteman left a comment

Choose a reason for hiding this comment

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

LGTM. Thank you.

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Linux m4)


Success

Full output at http://54.241.84.105:8877/c7bdb9d3b1c73a2/output.txt

Total script time: 17.19 mins

  • Regression tests: Passed

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Windows)


Success

Full output at http://54.193.163.58:8877/4ca3ccdd208991b/output.txt

Total script time: 29.96 mins

  • Regression tests: Passed

@Snuffleupagus Snuffleupagus merged commit a648e1e into mozilla:master Feb 22, 2025
9 checks passed
@Snuffleupagus Snuffleupagus deleted the api-useWasm branch February 22, 2025 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
image-jpx release-blocker Blocker for the upcoming release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants