-
Notifications
You must be signed in to change notification settings - Fork 64
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
11 failing tests due to mocha timeout of 2000ms #284
Comments
Here's the docker build log of the
|
What is this? I am trying to build this inside a docker image as a sub-dep of my project. Can it be automated? And how do i get to the installer menu? |
is anyone going to tell me what the download is? |
why is this in a dropbox and not like a gcc.org or something. what does this "fix"? @seeronline ? |
It's bot spam (potentially harmful), please don't click on any suspicious links. Removed all these comments but they may add more |
Thanks, glad i was sus. Any idea how to increase the timeout? I’m not sure what package uses buble in my project because i’m a dotnet dev and very amateur with JS frameworks (only a couple of years in, i can code it but setups etc are new to me). My next steps are to try to reduce the version numbers of the parent packages (i just did an ncu -u recently which brought all packages to their latest) until i can get a successful build. funny thing is it builds and runs on my machine with |
on a whim I decided to try building for AMD64 arch, and it works fine. so it's got something to do with the 2s timeout on ARM64. or perhaps the code for 1buble1 isn't ARM64 compatible?? |
I have written an angular application that has your package as a dependency. it uses source code to build your package, which forces your tests to run. 11 tests fail due to the 2000ms timeout, which I cannot find a way to alter.
I have tried using the karma config to change the mocha timeout, as well as the package.json file of all places, to configure mocha's timeout.
perhaps you could provide us with a way to alter that?
The text was updated successfully, but these errors were encountered: