-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
Remove the Firefox-specific 'read with streaming' unit-test #10668
Remove the Firefox-specific 'read with streaming' unit-test #10668
Conversation
From: Bot.io (Linux m4)ReceivedCommand cmd_unittest from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.67.70.0:8877/5db9aba65358dbe/output.txt |
From: Bot.io (Windows)ReceivedCommand cmd_unittest from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.215.176.217:8877/48270e71d5b43c9/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.67.70.0:8877/5db9aba65358dbe/output.txt Total script time: 2.77 mins
|
From: Bot.io (Windows)SuccessFull output at http://54.215.176.217:8877/48270e71d5b43c9/output.txt Total script time: 5.33 mins
|
Support for the non-standard `moz-chunked-arraybuffer` response type is in the process of being removed from Firefox; see e.g. https://bugzilla.mozilla.org/show_bug.cgi?id=1411865 For the time being, you probably want to keep support for this in the general PDF.js library given that feature detection is used. However, removing the unit-test immediately seems reasonable, since it will otherwise start failing once the platform support for `moz-chunked-arraybuffer` is gone. Fixes 8851; please note that if unit-tests for the code in `fetch_stream.js` are wanted, which I'm assuming they are, those should live in their own file rather than being lumped into `network_spec.js` anyway.
b6e5ef7
to
234c1d2
Compare
From: Bot.io (Linux m4)ReceivedCommand cmd_unittest from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.67.70.0:8877/12a71de75009098/output.txt |
From: Bot.io (Windows)ReceivedCommand cmd_unittest from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.215.176.217:8877/60e034a12bf2d2a/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.67.70.0:8877/12a71de75009098/output.txt Total script time: 2.71 mins
|
From: Bot.io (Windows)SuccessFull output at http://54.215.176.217:8877/60e034a12bf2d2a/output.txt Total script time: 5.30 mins
|
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.
I'll make a follow-up ticket for introducing proper unit tests for streaming again. Thanks!
Support for the non-standard
moz-chunked-arraybuffer
response type is in the process of being removed from Firefox; see e.g. https://bugzilla.mozilla.org/show_bug.cgi?id=1411865For the time being, you probably want to keep support for this in the general PDF.js library given that feature detection is used. However, removing the unit-test immediately seems reasonable, since it will otherwise start failing once the platform support for
moz-chunked-arraybuffer
is gone.Fixes #8851; please note that if unit-tests for the code in
fetch_stream.js
are wanted, which I'm assuming they are, those should live in their own file rather than being lumped intonetwork_spec.js
anyway.