Skip to content

Conversation

@dominikschubert
Copy link
Member

Motivation

Hunting failings tests here is quite awful because the CI doesn't actually show you what went wrong in the started container.

Changes

  • If the container can't start, at least print the logs so that we see them in CI. Also locally this is quite helpful since the container is by default immediately removed.

TODO

Might want to go through the rest of the bootstrap tests and do similar things there

@github-actions
Copy link

LocalStack Community integration with Pro

       2 files         2 suites   1h 7m 18s ⏱️
2 372 tests 2 058 ✔️ 314 💤 0
2 373 runs  2 058 ✔️ 315 💤 0

Results for commit 186ffa49.

@simonrw simonrw added this to the Playground milestone Jan 22, 2024
meteharun

This comment was marked as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants