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

Update packages #9576

Merged
merged 1 commit into from Mar 25, 2018
Merged

Update packages #9576

merged 1 commit into from Mar 25, 2018

Conversation

timvandermeij
Copy link
Contributor

@timvandermeij timvandermeij commented Mar 17, 2018

Jasmine had a major version bump and required a few minor changes in our booting code. Most notably, using pending in a describe block is no longer supported, so we can only return early there. On the positive side, the unit tests now run in a random order by default, which eliminates any dependencies between unit tests.

Note that upgrading to Webpack 4 is out of scope for this patch since the bots cannot work well with the newly generated bundles (both browsers on both bots do not react within 120 seconds). Webpack 4 is not faster for us than Webpack 3, so for now there is no need to upgrade.

true : catchingExceptions);
var stoppingOnSpecFailure = queryString.getParam('failFast');
env.stopOnSpecFailure(typeof stoppingOnSpecFailure === 'undefined' ?
true : stoppingOnSpecFailure);
Copy link
Collaborator

Choose a reason for hiding this comment

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

From a cursory look at jasmine/jasmine@e15f273, which necessitated this change, shouldn't the default now be false instead here?

Edit: Or do we perhaps not want to maintain the old behaviour here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have fixed these comments in the new commit. Good catch!

true : catchingExceptions);
var stoppingOnSpecFailure = queryString.getParam('failFast');
env.stopOnSpecFailure(typeof stoppingOnSpecFailure === 'undefined' ?
true : stoppingOnSpecFailure);
Copy link
Collaborator

Choose a reason for hiding this comment

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

From a cursory look at jasmine/jasmine@e15f273, which necessitated this change, shouldn't the default now be false instead here?

Edit: Or do we perhaps not want to maintain the old behaviour here?

queryString.navigateWithNewParam('catch', !env.catchingExceptions());
onStopExecutionClick() {
queryString.navigateWithNewParam('failFast',
!env.stoppingOnSpecFailure());
Copy link
Collaborator

Choose a reason for hiding this comment

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

Re above, shouldn't this also be inverted?

queryString.navigateWithNewParam('catch', !env.catchingExceptions());
onStopExecutionClick() {
queryString.navigateWithNewParam('failFast',
!env.stoppingOnSpecFailure());
Copy link
Collaborator

Choose a reason for hiding this comment

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

Re above, shouldn't this also be inverted?

@timvandermeij timvandermeij changed the title Upgrade packages to their latest versions Update packages Mar 18, 2018
@timvandermeij
Copy link
Contributor Author

/botio-linux preview

@timvandermeij
Copy link
Contributor Author

/botio test

1 similar comment
@timvandermeij
Copy link
Contributor Author

/botio test

@mozilla mozilla deleted a comment from pdfjsbot Mar 18, 2018
@mozilla mozilla deleted a comment from pdfjsbot Mar 18, 2018
@mozilla mozilla deleted a comment from pdfjsbot Mar 18, 2018
@mozilla mozilla deleted a comment from pdfjsbot Mar 18, 2018
@mozilla mozilla deleted a comment from pdfjsbot Mar 18, 2018
@mozilla mozilla deleted a comment from pdfjsbot Mar 18, 2018
@mozilla mozilla deleted a comment from pdfjsbot Mar 18, 2018
@mozilla mozilla deleted a comment from pdfjsbot Mar 18, 2018
@mozilla mozilla deleted a comment from pdfjsbot Mar 18, 2018
@mozilla mozilla deleted a comment from pdfjsbot Mar 18, 2018
@timvandermeij
Copy link
Contributor Author

/botio-linux preview

@timvandermeij
Copy link
Contributor Author

/botio test

@Snuffleupagus
Copy link
Collaborator

Snuffleupagus commented Mar 18, 2018

Most notably, using pending in a describe block is no longer supported, so we can only return early there.

In that case, I wonder if the best solution wouldn't be to move those pending instances into each of the affected it blocks instead?
Obviously having to do that is a bit unfortunate, but I think it's conceptually the "right" solution since just returning doesn't provide a good indication that tests were skipped.

@@ -1192,7 +1193,8 @@ describe('api', function() {
});
describe('Multiple PDFJS instances', function() {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Also while you're here, let's update the name to Multiple getDocument instances (which I overlooked when removing the global PDFJS object).

package.json Outdated
"eslint-plugin-mozilla": "^0.9.0",
"escodegen": "^1.9.1",
"eslint": "^4.19.0",
"eslint-plugin-mozilla": "^0.9.1",
Copy link
Collaborator

Choose a reason for hiding this comment

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

There's apparently an even newer version, 0.10.0, of this package now.

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.

Looks good to me with the final comments, especially #9576 (comment), addressed; thank you!

Jasmine had a major version bump and required a few minor changes in our
booting code. Most notably, using `pending` in a `describe` block is no
longer supported, so we can only return early there. On the positive
side, the unit tests now run in a random order by default, which
eliminates any dependencies between unit tests.

Note that upgrading to Webpack 4 is out of scope for this patch since
the bots cannot work well with the newly generated bundles (both
browsers on both bots do not react within 120 seconds). Webpack 4 is not
faster for us than Webpack 3, so for now there is no need to upgrade.
@mozilla mozilla deleted a comment from pdfjsbot Mar 25, 2018
@mozilla mozilla deleted a comment from pdfjsbot Mar 25, 2018
@mozilla mozilla deleted a comment from pdfjsbot Mar 25, 2018
@mozilla mozilla deleted a comment from pdfjsbot Mar 25, 2018
@mozilla mozilla deleted a comment from pdfjsbot Mar 25, 2018
@mozilla mozilla deleted a comment from pdfjsbot Mar 25, 2018
@timvandermeij
Copy link
Contributor Author

/botio-linux preview

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Received

Command cmd_preview from @timvandermeij received. Current queue size: 0

Live output at: http://54.67.70.0:8877/146030089d003af/output.txt

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Success

Full output at http://54.67.70.0:8877/146030089d003af/output.txt

Total script time: 2.65 mins

Published

@timvandermeij
Copy link
Contributor Author

/botio test

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Received

Command cmd_test from @timvandermeij received. Current queue size: 0

Live output at: http://54.67.70.0:8877/8b04c985d647ad1/output.txt

@pdfjsbot
Copy link

From: Bot.io (Windows)


Received

Command cmd_test from @timvandermeij received. Current queue size: 0

Live output at: http://54.215.176.217:8877/af9ae44db84dcfd/output.txt

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Failed

Full output at http://54.67.70.0:8877/8b04c985d647ad1/output.txt

Total script time: 18.24 mins

  • Font tests: Passed
  • Unit tests: Passed
  • Regression tests: FAILED

Image differences available at: http://54.67.70.0:8877/8b04c985d647ad1/reftest-analyzer.html#web=eq.log

@pdfjsbot
Copy link

From: Bot.io (Windows)


Success

Full output at http://54.215.176.217:8877/af9ae44db84dcfd/output.txt

Total script time: 24.15 mins

  • Font tests: Passed
  • Unit tests: Passed
  • Regression tests: Passed

@timvandermeij
Copy link
Contributor Author

Firefox on Linux had an update, but there are no visual differences.

/botio-linux makeref

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Received

Command cmd_makeref from @timvandermeij received. Current queue size: 0

Live output at: http://54.67.70.0:8877/24a94fef5939c08/output.txt

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Success

Full output at http://54.67.70.0:8877/24a94fef5939c08/output.txt

Total script time: 16.97 mins

  • Lint: Passed
  • Make references: Passed
  • Check references: Passed

@timvandermeij timvandermeij merged commit 6cc0efe into mozilla:master Mar 25, 2018
@timvandermeij timvandermeij deleted the versions branch March 25, 2018 15:52
movsb pushed a commit to movsb/pdf.js that referenced this pull request Jul 14, 2018
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.

None yet

3 participants