As seen on https://github.com/aegir-project/tests some builds are in an ERROR state :(

The problem seems to be somewhere in the testing setup .... it keeps waiting for sudo while that should continue without a password.

[sudo] password for aegir: 

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

This has been a problem for a while now ... but with #2859549: Deprecate or move Jenkins around the corner this is becoming more important.

Comments

helmo created an issue. See original summary.

helmo’s picture

helmo commented

I tried editign the docker compose file recently ... but no luck. https://travis-ci.org/aegir-project/tests/builds/214378236

helmo’s picture

helmo commented

Jon fixed it for the dockerfiles repo in https://github.com/aegir-project/dockerfiles/pull/35

We still have to fix the other repo's to get all icons on https://github.com/aegir-project/tests green.

Would it be enough to empty the travis/prepare-docker.sh file from the tests repo?

helmo’s picture

helmo commented

The provision tests were green a while back.

Last green: https://travis-ci.org/aegir-project/provision/builds/342415018
First red: https://travis-ci.org/aegir-project/provision/builds/351475860#L1359

What is causing the The command "sudo docker-compose -f docker-compose-provision.yml run -T -e TERM=xterm hostmaster" exited with 1. error?

The file_put_contents(./composer.lock): failed to open stream: Permission denied error is also shown in the last green one ... safe to ignore?