Debugging for failed kafka containers

fedinskiy commented 3 months ago

Summary

Adds detailed output and hopefully fixes this error: https://github.com/quarkus-qe/quarkus-test-framework/issues/1186

Please check the relevant options

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Dependency update
[ ] Refactoring
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] This change requires a documentation update
[x] This change requires execution against OCP (use run tests phrase in comment)

Checklist:

[x] Example scenarios has been updated / added
[x] Methods and classes used in PR scenarios are meaningful
[x] Commits are well encapsulated and follow the best practices

michalvavrik commented 3 months ago

@gtroitsk thoughts on CI failure?

michalvavrik commented 3 months ago

damn I didn't realize these secrets won't be present in fork PRs. @gtroitsk creating PR from quarkus-qe repo like here https://github.com/quarkus-qe/quarkus-test-framework/pull/1174 isn't quite standard. that's why I didn't mention. let's talk via Slack

fedinskiy commented 2 months ago

run tests

fedinskiy commented 2 months ago

@michalvavrik the failure in jvm is unrelated (it is in debug mode). Do you prefer to merge now or wait for strimzi 0.107.0 to be relased first?

michalvavrik commented 2 months ago

@michalvavrik the failure in jvm is unrelated (it is in debug mode). Do you prefer to merge now or wait for strimzi 0.107.0 to be relased first?

Let's get it in, good job.

quarkus-qe / quarkus-test-framework

Debugging for failed kafka containers #1191

Summary

Checklist: