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.

Sign up for GitHub

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

Jump to bottom

[flaky] test/e2e.TestBrokerTrigger/1 #168

Closed
knative-test-reporter-robot opened this issue Sep 13, 2020 · 3 comments
Closed

[flaky] test/e2e.TestBrokerTrigger/1 #168

knative-test-reporter-robot opened this issue Sep 13, 2020 · 3 comments
Labels
auto:flaky

Comments

@knative-test-reporter-robot
Copy link

Auto-generated issue tracking flakiness of test

  • Test name: test/e2e.TestBrokerTrigger/1
  • Repository name: eventing-kafka-broker
@knative-test-reporter-robot
Copy link
Author

Latest result for this test: Flaky
Last build start time: 2020-09-13 10:59:30 +0000 UTC
Failed 1 times out of 10 runs. Failed runs: 1305083780309979136

2020-09-13 10:59:30 +0000 UTC: ✔ ✖ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔

✔ Passed ✖ Failed ◻ Skipped

@pierDipi
Copy link
Member 

=== Failed
=== FAIL: test/e2e TestBrokerTrigger/3 (unknown)
=== FAIL: test/e2e TestBrokerTrigger/4 (unknown)
=== FAIL: test/e2e TestBrokerTrigger/0 (unknown)
=== FAIL: test/e2e TestBrokerTrigger/1 (unknown)
=== FAIL: test/e2e TestBrokerTrigger/2 (unknown)

gotestyourself/gotestsum#141

/close

@knative-prow-robot
Copy link
Contributor

@pierDipi: Closing this issue.

In response to this:

=== Failed
=== FAIL: test/e2e TestBrokerTrigger/3 (unknown)
=== FAIL: test/e2e TestBrokerTrigger/4 (unknown)
=== FAIL: test/e2e TestBrokerTrigger/0 (unknown)
=== FAIL: test/e2e TestBrokerTrigger/1 (unknown)
=== FAIL: test/e2e TestBrokerTrigger/2 (unknown)

gotestyourself/gotestsum#141

/close

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.

lberk pushed a commit to lberk/eventing-kafka-broker that referenced this issue Apr 5, 2022
@pierDipi
Use Vert.x 4.2.5 (knative-extensions#168)
a97f556 
Replace the use of the `vertx-stack-depchain` with individual
dependencies and bump Vert.x from 4.2.4 to 4.2.5.

vertx-stack-depchain is just a bom, to avoid declaring
every single dependency, however, it's not productized at 4.2.5
https://maven.repository.redhat.com/ga/io/vertx/vertx-stack-depchain/4.2.5.redhat-00001/

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
pierDipi referenced this issue in pierDipi/eventing-kafka-broker Apr 12, 2022
@pierDipi
Use Vert.x 4.2.5 (#168)
5a155c7 
Replace the use of the `vertx-stack-depchain` with individual
dependencies and bump Vert.x from 4.2.4 to 4.2.5.

vertx-stack-depchain is just a bom, to avoid declaring
every single dependency, however, it's not productized at 4.2.5
https://maven.repository.redhat.com/ga/io/vertx/vertx-stack-depchain/4.2.5.redhat-00001/

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
pierDipi referenced this issue in pierDipi/eventing-kafka-broker Apr 14, 2022
@pierDipi @lberk
[release-v1.3] Use Vert.x 4.2.5 (#168) (#202)
034e57c 
* Use Vert.x 4.2.5 (#168)

Replace the use of the `vertx-stack-depchain` with individual
dependencies and bump Vert.x from 4.2.4 to 4.2.5.

vertx-stack-depchain is just a bom, to avoid declaring
every single dependency, however, it's not productized at 4.2.5
https://maven.repository.redhat.com/ga/io/vertx/vertx-stack-depchain/4.2.5.redhat-00001/

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>

* Update to maven repository and update vertx.version (#172)

Co-authored-by: Lukas Berk <lberk@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto:flaky
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pierDipi @knative-prow-robot @knative-test-reporter-robot