Skip to content

remove a rando sleep, testing to see if it is still needed#3898

Closed
n3wscott wants to merge 1 commit into
knative:masterfrom
n3wscott:no-sleep-til-e2e
Closed

remove a rando sleep, testing to see if it is still needed#3898
n3wscott wants to merge 1 commit into
knative:masterfrom
n3wscott:no-sleep-til-e2e

Conversation

@n3wscott
Copy link
Copy Markdown
Contributor

No description provided.

@knative-prow-robot knative-prow-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 20, 2020
@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Aug 20, 2020
@knative-prow-robot
Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@knative-prow-robot knative-prow-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Aug 20, 2020
@knative-prow-robot knative-prow-robot added area/test-and-release Test infrastructure, tests or release approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Aug 20, 2020
@n3wscott
Copy link
Copy Markdown
Contributor Author

/test pull-knative-eventing-integration-tests

Copy link
Copy Markdown
Member

@mattmoor mattmoor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Produced via:
gofmt -s -w $(find -path './vendor' -prune -o -path './third_party' -prune -o -name '*.pb.go' -prune -o -type f -name '*.go' -print)
goimports -w $(find -name '*.go' | grep -v vendor | grep -v third_party | grep -v .pb.go | grep -v wire_gen.go)

Comment thread test/lib/operation.go
@@ -18,8 +18,6 @@ package lib

import (
"fmt"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Format Go code:

Suggested change
"fmt"
"fmt"

@n3wscott
Copy link
Copy Markdown
Contributor Author

1/1 passed.

/test pull-knative-eventing-integration-tests

@n3wscott
Copy link
Copy Markdown
Contributor Author

2/2 passed.

/test pull-knative-eventing-integration-tests

@n3wscott
Copy link
Copy Markdown
Contributor Author

3/3 passed.

/test pull-knative-eventing-integration-tests

@n3wscott n3wscott marked this pull request as ready for review August 21, 2020 00:23
@knative-prow-robot knative-prow-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 21, 2020
@knative-test-reporter-robot
Copy link
Copy Markdown

The following jobs failed:

Test name Triggers Retries
pull-knative-eventing-conformance-tests 0/3

Failed non-flaky tests preventing automatic retry of pull-knative-eventing-conformance-tests:

.Up

@knative-test-reporter-robot
Copy link
Copy Markdown

The following jobs failed:

Test name Triggers Retries
pull-knative-eventing-integration-tests 0/3

Failed non-flaky tests preventing automatic retry of pull-knative-eventing-integration-tests:

.Up

@pierDipi
Copy link
Copy Markdown
Member

This issue might be related: #3686

@vaikas
Copy link
Copy Markdown
Contributor

vaikas commented Aug 21, 2020

Both tests failed with this. Not related.

NG: Starting with version 1.18, clusters will have shielded GKE nodes by default.
WARNING: Your Pod address range (`--cluster-ipv4-cidr`) can accommodate at most 1008 node(s). 
This will enable the autorepair feature for nodes. Please see https://cloud.google.com/kubernetes-engine/docs/node-auto-repair for more information on node autorepairs.
ERROR: (gcloud.beta.container.clusters.create) ResponseError: code=503, message=The service is currently unavailable.
Error: error creating clusters: error creating cluster: exit status 1
Step failed: ./test/e2e-tests.sh
+ EXIT_VALUE=1
+ set +o xtrace
WARNING: Starting with version 1.18, clusters will have shielded GKE nodes by default.
WARNING: Your Pod address range (`--cluster-ipv4-cidr`) can accommodate at most 1008 node(s). 
This will enable the autorepair feature for nodes. Please see https://cloud.google.com/kubernetes-engine/docs/node-auto-repair for more information on node autorepairs.
ERROR: (gcloud.beta.container.clusters.create) ResponseError: code=503, message=The service is currently unavailable.
Error: error creating clusters: error creating cluster: exit status 1
Step failed: ./test/e2e-conformance-tests.sh
+ EXIT_VALUE=1
+ set +o xtrace

@vaikas
Copy link
Copy Markdown
Contributor

vaikas commented Aug 21, 2020

/test pull-knative-eventing-integration-tests

@vaikas
Copy link
Copy Markdown
Contributor

vaikas commented Aug 21, 2020

/test pull-knative-eventing-conformance-tests

1 similar comment
@aliok
Copy link
Copy Markdown
Member

aliok commented Aug 24, 2020

/test pull-knative-eventing-conformance-tests

@aliok
Copy link
Copy Markdown
Member

aliok commented Aug 24, 2020

Retest worked, but perhaps only for this time.

Previous failed build: https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_eventing/3898/pull-knative-eventing-conformance-tests/1296875005098856450

    monitoring.go:71: running recordevents port-forward in background, pid = 50882
=== CONT  TestChannelTracingWithReply/InMemoryChannel-messaging.knative.dev/v1
    event_info_store.go:245: Timeout waiting for at least 1 matches.
        Error: FAIL MATCHING: saw 0/1 matching events.
        Recent events: 
        0 events seen, last 0 events:
        Match errors: 
        
        
        knative.dev/eventing/test/lib/recordevents.(*EventInfoStore).AssertAtLeast
        	/home/prow/go/src/knative.dev/eventing/test/lib/recordevents/event_info_store.go:245
        knative.dev/eventing/test/conformance/helpers.tracingTest
        	/home/prow/go/src/knative.dev/eventing/test/conformance/helpers/tracing_test_helper.go:72
        knative.dev/eventing/test/conformance/helpers.ChannelTracingTestHelperWithChannelTestRunner.func1
        	/home/prow/go/src/knative.dev/eventing/test/conformance/helpers/channel_tracing_test_helper.go:43
        knative.dev/eventing/test/lib.(*ComponentsTestRunner).RunTests.func1
        	/home/prow/go/src/knative.dev/eventing/test/lib/test_runner.go:72
        testing.tRunner
        	/root/.gvm/gos/go1.14.6/src/testing/testing.go:1039
        runtime.goexit
        	/root/.gvm/gos/go1.14.6/src/runtime/asm_amd64.s:1373

@aliok
Copy link
Copy Markdown
Member

aliok commented Aug 24, 2020

/test pull-knative-eventing-conformance-tests

1 similar comment
@matzew
Copy link
Copy Markdown
Member

matzew commented Aug 24, 2020

/test pull-knative-eventing-conformance-tests

@matzew
Copy link
Copy Markdown
Member

matzew commented Aug 24, 2020

/test pull-knative-eventing-integration-tests

@n3wscott
Copy link
Copy Markdown
Contributor Author

/test pull-knative-eventing-conformance-tests
/test pull-knative-eventing-integration-tests

@n3wscott
Copy link
Copy Markdown
Contributor Author

welll.... /tableflip

@vaikas
Copy link
Copy Markdown
Contributor

vaikas commented Aug 27, 2020

This failed with the eventinfo store:

    event_info_store.go:245: Timeout waiting for at least 1 matches.
        Error: FAIL MATCHING: saw 0/1 matching events.
        Recent events: 
        0 events seen, last 0 events:
        Match errors: 
        
        
        knative.dev/eventing/test/lib/recordevents.(*EventInfoStore).AssertAtLeast
        	/home/prow/go/src/knative.dev/eventing/test/lib/recordevents/event_info_store.go:245
        knative.dev/eventing/test/e2e/helpers.SequenceTestHelper.func1
        	/home/prow/go/src/knative.dev/eventing/test/e2e/helpers/sequence_test_helper.go:146
        knative.dev/eventing/test/lib.(*ComponentsTestRunner).RunTests.func1
        	/home/prow/go/src/knative.dev/eventing/test/lib/test_runner.go:72
        testing.tRunner
        	/root/.gvm/gos/go1.14.6/src/testing/testing.go:1039
        runtime.goexit
        	/root/.gvm/gos/go1.14.6/src/runtime/asm_amd64.s:1373

#3570

Copy link
Copy Markdown
Member

@pierDipi pierDipi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/retest

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 17, 2020
@knative-prow-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: n3wscott, pierDipi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@pierDipi
Copy link
Copy Markdown
Member

docs/source/receive-adapter.md
	ERROR	https://github.com/knative/eventing-contrib/tree/master/github
		Not Found (HTTP error 404)

/cc @lionelvillard

@pierDipi
Copy link
Copy Markdown
Member

/retest

@pierDipi
Copy link
Copy Markdown
Member

=== CONT  TestChannelTracingWithReply/Channel-messaging.knative.dev/v1
    event_info_store.go:246: Timeout waiting for at least 1 matches.
        Error: FAIL MATCHING: saw 0/1 matching events.
        Recent events: 
        0 events seen, last 0 events:
        Match errors: 
        
        
        knative.dev/eventing/test/lib/recordevents.(*EventInfoStore).AssertAtLeast
        	/home/prow/go/src/knative.dev/eventing/test/lib/recordevents/event_info_store.go:246
        knative.dev/eventing/test/conformance/helpers.tracingTest
        	/home/prow/go/src/knative.dev/eventing/test/conformance/helpers/tracing_test_helper.go:74
        knative.dev/eventing/test/conformance/helpers.ChannelTracingTestHelperWithChannelTestRunner.func1
        	/home/prow/go/src/knative.dev/eventing/test/conformance/helpers/channel_tracing_test_helper.go:45
        knative.dev/eventing/test/lib.(*ComponentsTestRunner).RunTests.func1
        	/home/prow/go/src/knative.dev/eventing/test/lib/test_runner.go:75
        testing.tRunner
        	/root/.gvm/gos/go1.14.6/src/testing/testing.go:1039
        runtime.goexit
        	/root/.gvm/gos/go1.14.6/src/runtime/asm_amd64.s:1373

/retest

@pierDipi
Copy link
Copy Markdown
Member

This is interesting, I've never seen it before:

=== CONT  TestChannelChannelableManipulatorClusterRoleTest/InMemoryChannel-messaging.knative.dev/v1beta1
    rbac.go:46: Operation "get" is not allowed on inmemorychannels.messaging.knative.dev/v1beta1 subresource:""

@n3wscott
Copy link
Copy Markdown
Contributor Author

/retest

1 similar comment
@pierDipi
Copy link
Copy Markdown
Member

/retest

@pierDipi
Copy link
Copy Markdown
Member

=== CONT  TestBrokerTracing/Channel-messaging.knative.dev/v1
    event_info_store.go:246: Timeout waiting for at least 1 matches.
        Error: FAIL MATCHING: saw 0/1 matching events.
        Recent events: 
        0 events seen, last 0 events:
        Match errors: 
        
        
        knative.dev/eventing/test/lib/recordevents.(*EventInfoStore).AssertAtLeast
        	/home/prow/go/src/knative.dev/eventing/test/lib/recordevents/event_info_store.go:246
        knative.dev/eventing/test/conformance/helpers.tracingTest
        	/home/prow/go/src/knative.dev/eventing/test/conformance/helpers/tracing_test_helper.go:74
        knative.dev/eventing/test/conformance/helpers.BrokerTracingTestHelperWithChannelTestRunner.func1
        	/home/prow/go/src/knative.dev/eventing/test/conformance/helpers/broker_tracing_test_helper.go:47
        knative.dev/eventing/test/lib.(*ComponentsTestRunner).RunTests.func1
        	/home/prow/go/src/knative.dev/eventing/test/lib/test_runner.go:75
        testing.tRunner
        	/root/.gvm/gos/go1.14.6/src/testing/testing.go:1039
        runtime.goexit
        	/root/.gvm/gos/go1.14.6/src/runtime/asm_amd64.s:1373

/retest

@pierDipi
Copy link
Copy Markdown
Member

pierDipi commented Oct 2, 2020

/retest

3 similar comments
@pierDipi
Copy link
Copy Markdown
Member

/retest

@n3wscott
Copy link
Copy Markdown
Contributor Author

/retest

@pierDipi
Copy link
Copy Markdown
Member

/retest

@pierDipi
Copy link
Copy Markdown
Member

Apparently, removing this random sleep makes our CI jobs unstable. 🤔

@pierDipi
Copy link
Copy Markdown
Member

/lgtm cancel

@knative-prow-robot knative-prow-robot removed the lgtm Indicates that a PR is ready to be merged. label Oct 30, 2020
@pierDipi
Copy link
Copy Markdown
Member

/retest

@knative-prow-robot
Copy link
Copy Markdown
Contributor

@n3wscott: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
pull-knative-eventing-integration-tests 52490f6 link /test pull-knative-eventing-integration-tests

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@tayarani
Copy link
Copy Markdown
Contributor

@n3wscott is there consensus that we still need the sleep? should we close this?

@n3wscott
Copy link
Copy Markdown
Contributor Author

n3wscott commented Dec 2, 2020

/close

reconciler-test will not use a sleep

@knative-prow-robot
Copy link
Copy Markdown
Contributor

@n3wscott: Closed this PR.

Details

In response to this:

/close

reconciler-test will not use a sleep

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/test-and-release Test infrastructure, tests or release cla: yes Indicates the PR's author has signed the CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants