Test suite fails on MacOS
See original GitHub issueDescribe the Bug
On the current master
branch, npm run all
fails on MacOS
I first thought it would be a problem with my setup, but actually it is reproducible when we configure mac os in our GitHub Action, cf. to this build to get more information.
Steps to Reproduce
Steps to reproduce the behavior:
git checkout master
npm install
npm run all
Expected Behavior
Everything works fine on MacOS.
Environment
Please complete the following information:
- OS: macOS 10.15.7
- Library version: current
master
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
test suite fails on MacOS 11.4 BigSur · Issue #5575 - GitHub
Application or Package Used nteract desktop. Describe the bug 3 test suite failures. To Reproduce follow build steps from contributing page ...
Read more >Slow framework unit test failure (~5s) - Apple Developer
Takes 4.356 seconds to execute on my 2019 MacBook Pro: Test Case '-[FrameworkTests.FrameworkTests testExampleFailure]' failed (4.356 seconds).
Read more >TestNG ant task fails on Mac OS X with error: No test suite found
The issue happened due to a ReportNG dependency being downloading using the maven ant task which also declares a dependency on an ancient ......
Read more >Testing tools in Visual Studio for Mac - Microsoft Learn
As tests are running, a Test Results window appears so you can review successful or failed tests, and the output from running those...
Read more >Failing Tests while Compiling Swift on Xcode 12 with MacOS ...
I am trying to compile Swift for a while now. The compilation goes perfectly but some test case fails which results in the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Same here:
On develop:
Closed via 3180fa9