[GitHub] [camel-k] astefanutti edited a comment on issue #1939: Flaky e2e test (cron-fallback)

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 .

[GitHub] [camel-k] astefanutti edited a comment on issue #1939: Flaky e2e test (cron-fallback)

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?

[GitHub] [camel-k] astefanutti edited a comment on issue #1939: Flaky e2e test (cron-fallback)

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.

[GitHub] [camel-k] astefanutti edited a comment on issue #1939: Flaky e2e test (cron-fallback)

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.