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 core.sh: executing 'oc logs dc/failing-dc' expecting success #17721

Closed
sjenning opened this issue Dec 12, 2017 · 3 comments
Closed

e2e core.sh: executing 'oc logs dc/failing-dc' expecting success #17721

sjenning opened this issue Dec 12, 2017 · 3 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1

Comments

@sjenning
Copy link
Contributor

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/17479/test_pull_request_origin_end_to_end/6613/

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/17553/test_pull_request_origin_end_to_end/6603/

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/17479/test_pull_request_origin_end_to_end/6606/

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/17719/test_pull_request_origin_end_to_end/6610/

=== BEGIN TEST CASE ===
test/end-to-end/core.sh:422: executing 'oc logs dc/failing-dc-mid' expecting success and text 'test mid hook executed'
FAILURE after 0.248s: test/end-to-end/core.sh:422: executing 'oc logs dc/failing-dc-mid' expecting success and text 'test mid hook executed': the output content test failed
Standard output from the command:
error: update acceptor rejected failing-dc-mid-1: pods for rc 'test/failing-dc-mid-1' took longer than 20 seconds to become available

There was no error output from the command.
=== END TEST CASE ===
=== BEGIN TEST CASE ===
test/end-to-end/core.sh:408: executing 'oc logs dc/failing-dc' expecting success and text 'test pre hook executed'
FAILURE after 0.278s: test/end-to-end/core.sh:408: executing 'oc logs dc/failing-dc' expecting success and text 'test pre hook executed': the output content test failed
There was no output from the command.
There was no error output from the command.
=== END TEST CASE ===
@sjenning sjenning added the kind/test-flake Categorizes issue or PR as related to test flakes. label Dec 12, 2017
@stevekuznetsov
Copy link
Contributor

Also:

=== BEGIN TEST CASE ===
test/end-to-end/core.sh:408: executing 'oc logs dc/failing-dc' expecting success and text 'test pre hook executed'
FAILURE after 0.312s: test/end-to-end/core.sh:408: executing 'oc logs dc/failing-dc' expecting success and text 'test pre hook executed': the output content test failed
Standard output from the command:
--> pre: Running hook pod ...

There was no error output from the command.
=== END TEST CASE ===

/assign @bparees
/kind bug

@soltysh this can't have anything to do with the journald changes lately, could it? Looks like a lot of oc logs bugs.

@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Dec 13, 2017
@stevekuznetsov stevekuznetsov added priority/P1 kind/bug Categorizes issue or PR as related to a bug. and removed kind/bug Categorizes issue or PR as related to a bug. labels Dec 13, 2017
@tnozicka
Copy link
Contributor

@stevekuznetsov your failure is caused by #17747

the original one is pod not starting in 5s; the timeout is being raised in #17728 but that hangs on flakes

@tnozicka
Copy link
Contributor

actually I think all are #17747
here is the pull to disable the frequently failing test #17746

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1
Projects
None yet
Development

No branches or pull requests

5 participants