Closed greenkeeper[bot] closed 7 years ago
After pinning to 3.4.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are still failing with this version. Compare the changes π¨
xit
export for "require" interface (@solodynamo)--compilers
coverage (@ScottFreeCode)The new version differs by 14 commits.
4070a44
Release v3.5.1
466ba73
update CHANGELOG.md for v3.5.1 [ci skip]
1cc0fc0
import/require xit, fixes #2972
74fa66f
update nyc to latest; remove workaround in travis script
aa52933
update coveralls strategy; closes #2984
73a5338
Spelling (#2981)
9f403bf
Add utils.escape
tests and fix unicode escaping
800acbc
whitelist "developer-experience" tag for stalebot [ci skip]
5895671
Added issue, pull request templates. (#2869)
075bd51
Merge pull request #2918 from mochajs/no-shell-test
8710438
Work around Node 0.10 Windows flake when testing
13b8340
Ensure that compiler lookup works and not just that transpilation works (#2922)
26d337a
Add tests for double-star behavior
c0e6b68
Eliminate glob.sh
See the full diff
Your tests are still failing with this version. Compare the changes π¨
The new version differs by 5 commits.
72622ab
Release v3.5.2
ac4c39f
fix version in CHANGELOG.md [ci skip]
f06d969
update CHANGELOG for 3.5.2 [ci skip]
9a3ddeb
fix AMD bundle by hacking around check in he
module; closes #3000
337d317
fix broken links in CHANGELOG.md [ci skip]
See the full diff
Your tests are still failing with this version. Compare the changes π¨
Version 3.5.0 of mocha just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As mocha is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this :muscle:
Status Details
- β **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/npms-io/npms-analyzer/builds/259532405?utm_source=github_status&utm_medium=notification)Release Notes
free-as-in-freezing3.5.0 / 2017-07-31
--forbid-only
and--forbid-pending
flags. Use these in CI or hooks to ensure tests aren't accidentally being skipped! (@charlierudolph)--napi-modules
flag (@jupp0r)Commits
The new version differs by 34 commits.
82d879f
Release v3.5.0
bf687ce
update mocha.js for v3.5.0
ec73c9a
update date for release of v3.5.0 in CHANGELOG [ci skip]
1ba2cfc
update CHANGELOG.md for v3.5.0 [ci skip]
065e14e
remove custom install script from travis (no longer needed)
4e87046
update karma-sauce-launcher URL for npm@5
6886ccc
increase timeout for slow-grepping test
2408d90
Make dependencies use older version of readable-stream to work around incompatibilities introduced by 2.3.0 on June 19th
68a1466
Try not clearing the env for debug in the integration test and see if that fixes Node 0.10 on AppVeyor; if need be, some other fix/workaround can be applied to handle whatever was up with debug without causing this issue
958fbb4
Update new tests to work in browser per test hierarchy reorganization
1df7c94
Merge pull request #2704 from seppevs/increase_test_coverage_of_mocha_js
1f270cd
Stop timing out (#2889)
27c7496
upgrade to debug@2.6.8; closes #2859 (#2860)
50fc47d
fix CI; closes #2867 (#2868)
1b1377c
Add test for ignoreLeaks and fix descriptions
There are 34 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: