You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2021/01/22 13:31:25 UTC
[GitHub] [camel-k] nicolaferraro opened a new issue #1939: Flaky e2e test (cron-fallback)
nicolaferraro opened a new issue #1939:
URL: https://github.com/apache/camel-k/issues/1939
We need to fix this flaky e2e test:
```
--- FAIL: TestRunCronExample (310.61s)
--- PASS: TestRunCronExample/cron (127.61s)
--- PASS: TestRunCronExample/cron-timer (60.37s)
--- FAIL: TestRunCronExample/cron-fallback (91.99s)
```
It happens often, e.g. https://github.com/apache/camel-k/runs/1747588145?check_suite_focus=true, but disappears after running the CI multiple times.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] astefanutti commented on issue #1939: Flaky e2e test (cron-fallback)
Posted by GitBox <gi...@apache.org>.
astefanutti commented on issue #1939:
URL: https://github.com/apache/camel-k/issues/1939#issuecomment-765557557
OK, sounds good. It'd better be that. I did my tests quickly as I were bringing CI back on track so I may have overlooked things or forgotten others 😀.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] astefanutti commented on issue #1939: Flaky e2e test (cron-fallback)
Posted by GitBox <gi...@apache.org>.
astefanutti commented on issue #1939:
URL: https://github.com/apache/camel-k/issues/1939#issuecomment-765563180
The needle in the haystack 😄. That was too much cron dependencies for me :)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] astefanutti edited a comment on issue #1939: Flaky e2e test (cron-fallback)
Posted by GitBox <gi...@apache.org>.
astefanutti edited a comment on issue #1939:
URL: https://github.com/apache/camel-k/issues/1939#issuecomment-765440112
Hum that's what I did (adding the extra dependencies, not running it locally) and thought too, but IIRC if failed randomly also. Have you tried to run it multiple times?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] astefanutti commented on issue #1939: Flaky e2e test (cron-fallback)
Posted by GitBox <gi...@apache.org>.
astefanutti commented on issue #1939:
URL: https://github.com/apache/camel-k/issues/1939#issuecomment-765440112
Hum that's what I did and thought too, but IIRC if failed randomly also. Have you tried to run it multiple times?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] astefanutti edited a comment on issue #1939: Flaky e2e test (cron-fallback)
Posted by GitBox <gi...@apache.org>.
astefanutti edited a comment on issue #1939:
URL: https://github.com/apache/camel-k/issues/1939#issuecomment-765423170
Note that I've faced the issue by running the TestRunCronExample e2e test locally as well, so it does not seem CI environment specific.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] astefanutti edited a comment on issue #1939: Flaky e2e test (cron-fallback)
Posted by GitBox <gi...@apache.org>.
astefanutti edited a comment on issue #1939:
URL: https://github.com/apache/camel-k/issues/1939#issuecomment-765557557
OK, sounds good. It'd better be that. I did my tests quickly as I was bringing CI back on track, so I may have overlooked things or forgotten others 😀.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] astefanutti commented on issue #1939: Flaky e2e test (cron-fallback)
Posted by GitBox <gi...@apache.org>.
astefanutti commented on issue #1939:
URL: https://github.com/apache/camel-k/issues/1939#issuecomment-765563718
And you've just cut the project CI budget by half 👍🏼!
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] astefanutti edited a comment on issue #1939: Flaky e2e test (cron-fallback)
Posted by GitBox <gi...@apache.org>.
astefanutti edited a comment on issue #1939:
URL: https://github.com/apache/camel-k/issues/1939#issuecomment-765423170
Note that I've faced the issue by running the TestRunCronExample/cron-fallback e2e test locally as well, so it does not seem CI environment specific.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] astefanutti commented on issue #1939: Flaky e2e test (cron-fallback)
Posted by GitBox <gi...@apache.org>.
astefanutti commented on issue #1939:
URL: https://github.com/apache/camel-k/issues/1939#issuecomment-765423170
Note that I've faced the issue by running the TestRunCronExample e2e test locally as well, so it does not seem environment specific.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] nicolaferraro commented on issue #1939: Flaky e2e test (cron-fallback)
Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #1939:
URL: https://github.com/apache/camel-k/issues/1939#issuecomment-765532585
> Hum that's what I did (adding the extra dependencies, not running it locally) and thought too, but IIRC if failed randomly also. Have you tried to run it multiple times?
No, it seems to work.. at least locally..
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] astefanutti closed issue #1939: Flaky e2e test (cron-fallback)
Posted by GitBox <gi...@apache.org>.
astefanutti closed issue #1939:
URL: https://github.com/apache/camel-k/issues/1939
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] nicolaferraro commented on issue #1939: Flaky e2e test (cron-fallback)
Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #1939:
URL: https://github.com/apache/camel-k/issues/1939#issuecomment-765560895
Found it! Catalog contains both:
```
camel-k-cron:
groupId: org.apache.camel.k
artifactId: camel-k-cron
schemes:
- id: cron
http: false
passive: false
```
And
```
camel-quarkus-cron:
groupId: org.apache.camel.quarkus
artifactId: camel-quarkus-cron
schemes:
- id: cron
http: false
passive: false
javaTypes:
- org.apache.camel.component.cron.CronComponent
```
So depending on the status of some butterflies, the right component gets loaded.
I think `camel-quarkus-cron` is the right one, the other is part of the cron capability.
Opening issue in the runtime.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] astefanutti commented on issue #1939: Flaky e2e test (cron-fallback)
Posted by GitBox <gi...@apache.org>.
astefanutti commented on issue #1939:
URL: https://github.com/apache/camel-k/issues/1939#issuecomment-765427350
That's a good question 😉.
I've looked at the dependencies and it seems the quartz dependencies are added correctly. It may be an issue with how Quarkus resolve classes...
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] nicolaferraro commented on issue #1939: Flaky e2e test (cron-fallback)
Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #1939:
URL: https://github.com/apache/camel-k/issues/1939#issuecomment-765573246
Yeah, that's why restarting CI 2-3 times was working XD
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] nicolaferraro commented on issue #1939: Flaky e2e test (cron-fallback)
Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #1939:
URL: https://github.com/apache/camel-k/issues/1939#issuecomment-765424571
> Note that I've faced the issue by running the TestRunCronExample e2e test locally as well, so it does not seem CI environment specific.
Uh, so why sometimes it passes :facepalm: ?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] nicolaferraro commented on issue #1939: Flaky e2e test (cron-fallback)
Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #1939:
URL: https://github.com/apache/camel-k/issues/1939#issuecomment-765438220
> That's a good question .
>
> I've looked at the dependencies and it seems the quartz dependencies are added correctly. It may be an issue with how Quarkus resolve classes...
This works:
```
kamel local run cron-fallback.groovy -d camel-quarkus:quartz -d camel-quarkus:cron
```
So I guess the camel-quarkus:cron dependency is missing for some reason.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org