Build timeout but actually succeeded

[Last-Order]

https://travis-ci.org/Last-Order/Monita/jobs/509885403

The build status is failed due to timeout but it actually has finished all the procedures. How to solve this problem?
Thanks in advance.

[BanzaiMan]

Looks like a variation of

Timeout after build finished (and succeeded)

Happened in this build: https://travis-ci.org/FormAPI/craco-less/jobs/465718673 Done. Your build exited with 0. 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 The timeout also happened in this build: https://trav…

[ranih]

It’s related to yarn GPG. This solution worked for me:

Timeout after build finished (and succeeded)

Container stays up because of the yarn installation running gpg. see: # Build doesn't finish after completing tests to workaround, add this to .travis.yml: env: - YARN_GPG=no

[igagis]

recently I started getting this error:
https://travis-ci.org/igagis/utki/jobs/638886761

I did not change anything which could cause that, so it looks like something has changed in the environment, either in travis windows image or in msys2 chocolatey package or somewhere else.

Already tried YARN_GPG=no, did not help.

does anybody see this as well? Any idea what could cause that?

[native-api]

Windows build timeout after success, ps shows "gpg-agent"

Any background process that’s still running would cause that. Need to see the diff with a previous process snapshot to pinpoint the culprit, but your process list and earlier commands suggest bash background jobs.