Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI timeout during package upgrade in xenial staging scenario #4220

Closed
emkll opened this issue Mar 4, 2019 · 0 comments · Fixed by #4218
Closed

CI timeout during package upgrade in xenial staging scenario #4220

emkll opened this issue Mar 4, 2019 · 0 comments · Fixed by #4218

Comments

@emkll
Copy link
Contributor

emkll commented Mar 4, 2019

Description

When upgrading distribution packages in staging, the CI run times out due to lack of output. This is likely due to a large amount of packages on the both app and mon due to nested virt

Steps to Reproduce

Observe CI output of these runs

    TASK [common : Perform safe upgrade to ensure all the packages are updated.] ***
make: *** [ci-go-xenial] Terminated
Warning: Permanently added '35.230.112.0' (ECDSA) to the list of known hosts.

scp: /home/sdci/securedrop-source/junit/*xml: No such file or directory
Too long with no output (exceeded 10m0s)

Expected Behavior

Packages should be updated, no timeouts out

Actual Behavior

Very often there is a timeout when upgrading packages, resulting in a failed xenial-staging-with-rebase step.

Comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant