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 uncaught TypeError if error occurs on next tick, closes #2315 #2439

Merged

Conversation

1999
Copy link
Contributor

@1999 1999 commented Aug 14, 2016

No description provided.

@boneskull boneskull added the status: needs review a maintainer should (re-)review this pull request label Sep 18, 2016
@boneskull boneskull self-assigned this Sep 18, 2016
@boneskull boneskull modified the milestone: v3.1.0 Sep 19, 2016
@1999 1999 force-pushed the fix/cannot-read-property-currentretry branch from 880bdd9 to 7a81a4f Compare September 19, 2016 07:58
@1999
Copy link
Contributor Author

1999 commented Sep 19, 2016

Just merged from upstream/master + rebased

@ljharb
Copy link

ljharb commented Sep 19, 2016

Getting this merged and released would help avoid hundreds of flaky test failures in our codebase every day - any update on getting this in?

@boneskull
Copy link
Contributor

@ljharb it'll go in the next release, assuming it's OK, but I need to review it.

@boneskull
Copy link
Contributor

@1999 lgtm, thanks!

@boneskull boneskull removed the status: needs review a maintainer should (re-)review this pull request label Sep 22, 2016
@boneskull
Copy link
Contributor

ugh, n/m, let me look into this further. I'm so used to the appveyor failures being false alarms.

@boneskull boneskull added the status: needs review a maintainer should (re-)review this pull request label Sep 22, 2016
@boneskull
Copy link
Contributor

I'm not really convinced this is the "right" way to fix the issue, but after some experimentation it seems to have the least amount of friction.

Main problem seems to be a flaky fixture which can evidently pass on Windows due to timing issues. I have an experimental change in 4e88243 with build here. If that has better results, I'll merge this and commit my change on top of it.

@boneskull boneskull merged commit f1ac548 into mochajs:master Sep 22, 2016
@1999 1999 deleted the fix/cannot-read-property-currentretry branch September 22, 2016 15:01
1999 pushed a commit to 1999/mocha that referenced this pull request Sep 22, 2016
…-files-cache

* upstream/master:
  attempt windows-friendly reproducible case for mochajs#2315
  fix: fix uncaught TypeError if error occurs on next tick, closes mochajs#2315 (mochajs#2439)
  helpful error when necessary suite callback omitted; closes mochajs#1744
  Fix an issue and add relevant tests when describe and xdescribe fail when not supplied with a callback (issue mochajs#1744).
  rename more fixtures; closes mochajs#2383
  Report non-match to STDERR and exit if no files are matched (mochajs#2450)
  Exit process with correct error codes (mochajs#2445)
  fix test files not using .spec suffix fix test fixtures not using .fixture suffix
  always halt execution when async skip() called; closes mochajs#2465 (mochajs#2479)
  avoid test flake in "delay" test; closes mochajs#2469 (mochajs#2470)
  revert accidental change to bin paths
  disregard function names when testing under Node.js 6.5.0; closes mochajs#2467 (mochajs#2477)
  lints more files; add more files to lint check; closes mochajs#2457
  adds *.orig to .gitignore
  Exclude the --inspect flag
  fix check-leaks to catch a leak whose name begins with 'd'
@boneskull boneskull removed the status: needs review a maintainer should (re-)review this pull request label Dec 12, 2017
@boneskull boneskull removed their assignment Dec 12, 2017
sgilroy pushed a commit to TwineHealth/mocha that referenced this pull request Feb 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants