tahoe-lafs/trac-2024-07-25

Sometimes the test suite times out on CircleCI #2994

New issue

Open

opened 2019-03-11 15:16:24 +00:00 by exarkun · 1 comment

exarkun commented

2019-03-11 15:16:24 +00:00

Owner

For example, this build - https://circleci.com/gh/tahoe-lafs/tahoe-lafs/3992 - ran tests for 24:17 and then killed the job because of a CircleCI 20 minute timeout (with no output).

It's not clear if the test suite has hung or if it is just taking long enough that it trips the no-output timeout.

For example, this build - <https://circleci.com/gh/tahoe-lafs/tahoe-lafs/3992> - ran tests for 24:17 and then killed the job because of a CircleCI 20 minute timeout (with no output). It's not clear if the test suite has hung or if it is just taking long enough that it trips the no-output timeout.

tahoe-lafs added the

labels 2019-03-11 15:16:24 +00:00

tahoe-lafs added this to the undecided milestone 2019-03-11 15:16:24 +00:00

exarkun commented

2019-03-11 15:19:12 +00:00

Author

Owner

The test.log for that build - https://3992-3007569-gh.circle-artifacts.com/0/tmp/project/_trial_temp/test.log - is a little confusing.

It looks to me like the test run began at

2019-03-11 13:18:00+0000

and ended at

2019-03-11 13:26:46.241Z

(side-note: awesome change in timestamp format in that log file).

This seems to be about 8m46s. Perhaps this suggests the test run is hanging at the end? The suite is done but the process fails to exit (or CircleCI fails to notice it exit? ick).

The test.log for that build - <https://3992-3007569-gh.circle-artifacts.com/0/tmp/project/_trial_temp/test.log> - is a little confusing. It looks to me like the test run began at 2019-03-11 13:18:00+0000 and ended at 2019-03-11 13:26:46.241Z (side-note: awesome change in timestamp format in that log file). This seems to be about 8m46s. Perhaps this suggests the test run is _hanging_ at the end? The suite is done but the process fails to exit (or CircleCI fails to _notice_ it exit? ick).

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#2994

No description provided.