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

Integration test on Shippable runs into timeout #16745

Closed
Christoph-D opened this issue Jul 18, 2016 · 2 comments
Closed

Integration test on Shippable runs into timeout #16745

Christoph-D opened this issue Jul 18, 2016 · 2 comments
Assignees
Labels
bug This issue/PR relates to a bug.

Comments

@Christoph-D
Copy link
Contributor

ISSUE TYPE
  • Bug Report
ANSIBLE VERSION

Current devel branch.

SUMMARY

The 5th integration test (destructive opensuseleap) on Shippable reproducibly fails with TIMEOUT. For examples, see the pull requests #16723, #16735, #16736, #16739, #16741.

The Shippable status page for ansible doesn't load for me, so I cannot check if this only affects pull requests. The page not loading could also indicate that the problem is with Shippable.

STEPS TO REPRODUCE

Create a pull request.

EXPECTED RESULTS

All tests passed.

ACTUAL RESULTS

TIMEOUT for

TEST=integration TARGET=destructive IMAGE=ansible/ansible:opensuseleap
@robinro
Copy link
Contributor

robinro commented Jul 19, 2016

Could this be a docker hub issue? I had trouble pulling some images lately.

If it's something related to the opensuse image itself I'm happy to help, but so far I think it's not.

@mattclay
Copy link
Member

mattclay commented Aug 2, 2016

Closing this issue as opensuseleap integration tests are no longer regularly timing out.

@mattclay mattclay closed this as completed Aug 2, 2016
@ansibot ansibot added bug This issue/PR relates to a bug. and removed bug_report labels Mar 7, 2018
@ansible ansible locked and limited conversation to collaborators Apr 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug This issue/PR relates to a bug.
Projects
None yet
Development

No branches or pull requests

5 participants