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

e2e tests are failing on travis #793

Closed
lburgazzoli opened this issue Jul 2, 2019 · 6 comments · Fixed by #802
Closed

e2e tests are failing on travis #793

lburgazzoli opened this issue Jul 2, 2019 · 6 comments · Fixed by #802
Assignees

Comments

@lburgazzoli
Copy link
Contributor

No description provided.

@lburgazzoli
Copy link
Contributor Author

because of that we have removed them with #787

@jamesnetherton
Copy link
Contributor

I've run over 30 test builds and not had any failures since Tuesday when Travis was super flaky (all kinds of random failures were occurring).

Wondering if we just reinstate the tests and see how things go?

@lburgazzoli
Copy link
Contributor Author

let's try

jamesnetherton added a commit to jamesnetherton/camel-k that referenced this issue Jul 4, 2019
@jamesnetherton
Copy link
Contributor

Since the Travis debug option isn't available on the main build, I was thinking it might be nice to enhance the e2e tests to try and capture the operator logs and any other useful stuff at the end of each test.

Might help to make debugging CI issues a bit easier.

@lburgazzoli
Copy link
Contributor Author

I've added a bunch of them here https://github.com/lburgazzoli/apache-camel-k/commits/e2e-timeout, if it can help. But they were just attempt, not a very clear solution

lburgazzoli pushed a commit that referenced this issue Jul 4, 2019
@lburgazzoli lburgazzoli reopened this Jul 4, 2019
@lburgazzoli
Copy link
Contributor Author

ipolyzos pushed a commit to ipolyzos/camel-k that referenced this issue Jul 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants