Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
JS-0.4.0
-
None
Description
Example build: https://travis-ci.org/apache/arrow/jobs/498967250
JS tests sometimes fail with the following message:
> apache-arrow@ test /home/travis/build/apache/arrow/js > NODE_NO_WARNINGS=1 gulp test [22:14:01] Using gulpfile ~/build/apache/arrow/js/gulpfile.js [22:14:01] Starting 'test'... [22:14:01] Starting 'test:ts'... [22:14:49] Finished 'test:ts' after 47 s [22:14:49] Starting 'test:src'... [22:15:27] Finished 'test:src' after 38 s [22:15:27] Starting 'test:apache-arrow'... No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself. Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received The build has been terminated
I thought maybe we were just running up against some time limit, but that particular build was terminated at 22:25:27, exactly ten minutes after the last output, at 22:15:27. So it does seem like the build is somehow stalling.