You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Brian Hulette (JIRA)" <ji...@apache.org> on 2019/02/27 15:55:00 UTC
[jira] [Created] (ARROW-4695) [JS] Tests timing out on Travis
Brian Hulette created ARROW-4695:
------------------------------------
Summary: [JS] Tests timing out on Travis
Key: ARROW-4695
URL: https://issues.apache.org/jira/browse/ARROW-4695
Project: Apache Arrow
Issue Type: Improvement
Components: JavaScript
Affects Versions: JS-0.4.0
Reporter: Brian Hulette
Example build: https://travis-ci.org/apache/arrow/jobs/498967250
JS tests sometimes fail with the following message:
{noformat}
> 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
{noformat}
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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)