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

Investigste TestRunIncrementalBuildRoutine flakiness #5485

Open
lburgazzoli opened this issue May 9, 2024 · 3 comments
Open

Investigste TestRunIncrementalBuildRoutine flakiness #5485

lburgazzoli opened this issue May 9, 2024 · 3 comments
Labels
area/test/flakiness kind/bug Something isn't working

Comments

@lburgazzoli
Copy link
Contributor

lburgazzoli commented May 9, 2024

What happened?

The TestRunIncrementalBuildRoutine sometimes fails with no clear explanation

Steps to reproduce

Seen latest time in https://github.com/apache/camel-k/actions/runs/9008778242/job/24765909747?pr=5480

Relevant log output

❌ TestRunIncrementalBuildRoutine (10m24.24s)
      incremental_build_test.go:55: 
          Timed out after 300.000s.
          Expected
              <string>: kind-registry:5000/test-0c69be85-3121-48a6-9228-5e055a1f5b24/camel-k-kit-cou7vd3ia7ns738hnbl0@sha256:ef37351cef1b88365a6c1e9399fa028d03a763ade86ff06d609068552bd5697e
          to equal
              <string>: eclipse-temurin:17


### Camel K version

_No response_
@squakez
Copy link
Contributor

squakez commented May 9, 2024

Similar of #5332 - all these parallel builds are suffering some problem lately. I suppose it could be the enabled parallelism introduced in tests are showing possible concurrency problem in the build process.

@squakez
Copy link
Contributor

squakez commented May 9, 2024

As you're tracking these kind of failures as well, please, link the action so it is easier to follow it up and get the log dump for a more clear analysis. Thanks!

Seen in https://github.com/apache/camel-k/actions/runs/9008778242/job/24765909747?pr=5480

@valdar
Copy link
Member

valdar commented May 10, 2024

This might be fixed by #5494

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test/flakiness kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants