Skip to content

Emit start-up logs in VitessTestDb after health check fails on max at… #7123

Emit start-up logs in VitessTestDb after health check fails on max at…

Emit start-up logs in VitessTestDb after health check fails on max at… #7123

Triggered via push April 2, 2025 18:23
Status Success
Total duration 11m 40s
Artifacts
Fit to window
Zoom out
Zoom in

Annotations

4 errors
ChildEntityTest.exceptionWhenLoadingChildEntityById(): misk-hibernate/src/test/kotlin/misk/hibernate/ChildEntityTest.kt#L1
java.util.concurrent.ExecutionException: com.github.dockerjava.api.exception.ConflictException: Status 409: {"message":"Conflict. The container name \"/vitess_test_db_ext_movies_vtctldclient\" is already in use by container \"9aab621281038c3606f320df6f16a3119299e154163d0d56af763a389952f226\". You have to remove (or rename) that container to be able to reuse that name."}
ChildEntityTest.loadChildEntityByGid(): misk-hibernate/src/test/kotlin/misk/hibernate/ChildEntityTest.kt#L1
java.util.concurrent.ExecutionException: com.github.dockerjava.api.exception.NotFoundException: Status 404: {"message":"No such container: c9103377da24f938e4f622a3e526c2b49f2c2b3b32dc9f267f2e4e9fc593fe1e"}
VitessTraditionalSchemaMigratorTest.availableMigrations(): misk-jdbc/src/test/kotlin/misk/jdbc/VitessTraditionalSchemaMigratorTest.kt#L1
java.util.concurrent.ExecutionException: com.github.dockerjava.api.exception.ConflictException: Status 409: {"message":"can not get logs from container which is dead or marked for removal"}