Home → Problems →

Slow build tends fail because of test timeout

• Edit

Gyandeep Singh

22 Jul, 2015 12:30 AM

Since yesterday, the builds are failing due to timeout in tests.
Link: https://ci.appveyor.com/project/nzakas/eslint/build/332

I have windows 7 machine and when I run it on my machine everything works fine and tests take around 10 secons.
For reference check the travis CI builds: https://travis-ci.org/eslint/eslint

But in here it takes 2-3 mins and some of the tests timeout. All those tests which show timeout failure are actually synchronous tests.

Need help. Thanks

1. Support Staff 1 Posted by Feodor Fitsner on 22 Jul, 2015 01:15 AM

   

   I've migrated "nzakas" account to a new faster environment. See if that helps.

   • Edit

2. 2 Posted by Gyandeep Singh on 22 Jul, 2015 01:38 AM

   

   Awesome. Thanks a lot.
   That did fix the issue.
   https://ci.appveyor.com/project/nzakas/eslint/build/337

   They are faster then the old ones.

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 22 Jul, 2015 01:52 AM

   

   Nice!

   • Edit

4. 4 Posted by Gyandeep Singh on 22 Jul, 2015 02:13 AM

   

   This happened again: https://ci.appveyor.com/project/nzakas/eslint/build/340/job/wcyiakop38wwofxl

   I guess it behaves differently from build to build.

   • Edit

5. Support Staff 5 Posted by Feodor Fitsner on 22 Jul, 2015 02:25 AM

   

   Do those tests have any external dependencies (i.e. do http requests to some resources)?

   • Edit

6. 6 Posted by Gyandeep Singh on 22 Jul, 2015 02:29 AM

   

   Nope but they do have average amount of file operation going on like creating directory or file, delete file/directory etc.

   If you look here: https://ci.appveyor.com/project/nzakas/eslint/history
   Same code built 2 times, it worked one time and failed the other time. look at the one with the title "Build: Check commit message format at end of tests.. "

   • Edit

7. Support Staff 7 Posted by Feodor Fitsner on 22 Jul, 2015 02:30 AM

   

   Is there any way to get more detailed error than just:

   Validating Makefile.js
   npm ERR! Test failed.  See above for more details.
   Command exited with code 1
   

   • Edit

8. 8 Posted by Gyandeep Singh on 22 Jul, 2015 02:34 AM

   

   I am not sure how to get it as its only happening here. it doesn't happen on travis or on our local machines including windows machine.
   Our Makefile rarely gets updated and it works sometime and it doesnt sometime. Timeout errors are definitely happening because of slowness. That i realised after you made the first change. travis takes 10 seconds and now even the faster environment here is taking 45 seconds.

   • Edit

9. Support Staff 9 Posted by Feodor Fitsner on 22 Jul, 2015 02:37 AM

   

   What operation does take 45 seconds?

   Is is possible to have a tiny project reproducing the issue?

   • Edit

10. 10 Posted by Gyandeep Singh on 22 Jul, 2015 02:43 AM

    

    On latest builds you can see this for unit test runs
    ```
    [92m 5349 passing (47s)
    ```
    Please feel free to compare it against travis runs.

    You can personally checkout the project from here: https://github.com/eslint/eslint
    Run these commands
    ```sh
    npm install
    npm test
    ```

    • Edit

11. Support Staff 11 Posted by Feodor Fitsner on 22 Jul, 2015 04:05 AM

    

    Oh, I've got "EBADF": https://ci.appveyor.com/project/FeodorFitsner/eslint/build/5/job/ie...

    There is definitely something wrong with disk (which could potentially explain intermittent nature of failing builds). I'm checking the disk now.

    • Edit

12. 12 Posted by Gyandeep Singh on 22 Jul, 2015 03:22 PM

    

    Guys, any update on this. The problem still continues.
    With intermittent failure on different environments.
    History: https://ci.appveyor.com/project/nzakas/eslint/history

    For more details please look inside each build.

    • Edit

13. Support Staff 13 Posted by Feodor Fitsner on 22 Jul, 2015 03:23 PM

    

    Working on that.

    - Feodor

    • Edit

14. Support Staff 14 Posted by Feodor Fitsner on 30 Jul, 2015 02:44 AM

    

    We changed VMs to have 2 CPU cores. Apparently, with 2 cores the build is more stable.

    Let me know about the results.

    • Edit

15. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:58 AM.