S3 Image Test Results (AMD64 / ARM64)

    2 files    2 suites   8m 3s ⏱️
  533 tests 481 ✅  52 💤 0 ❌
1 066 runs  962 ✅ 104 💤 0 ❌

Results for commit 65460ee.

Test Results - Preflight, Unit

22 363 tests  ±0   20 613 ✅ ±0   15m 33s ⏱️ -13s
     1 suites ±0    1 750 💤 ±0 
     1 files   ±0        0 ❌ ±0 

Results for commit 65460ee. ± Comparison against base commit b4c510a.

Awesome find!
Quick question: it seems this has silently failed and we did not realize it: should we actually fail the pipeline if we cannot publish the dev-release? Not in scope of this PR, but more of a general thought

edit:

/home/runner/work/localstack/localstack/.venv/bin/python: No module named build
make: *** [Makefile:81: dist] Error 1
dev release failed (maybe it is already published)

I can see maybe there are reasons not to

Test Results (amd64) - Acceptance

7 tests  ±0   5 ✅ ±0   3m 43s ⏱️ +21s
1 suites ±0   2 💤 ±0 
1 files   ±0   0 ❌ ±0 

Results for commit 65460ee. ± Comparison against base commit b4c510a.

Test Results (amd64) - Integration, Bootstrap

    5 files      5 suites   2h 39m 24s ⏱️
5 252 tests 4 737 ✅ 515 💤 0 ❌
5 258 runs  4 737 ✅ 521 💤 0 ❌

Results for commit 65460ee.

♻️ This comment has been updated with latest results.

LocalStack Community integration with Pro

    2 files      2 suites   2h 0m 21s ⏱️
4 878 tests 4 523 ✅ 355 💤 0 ❌
4 880 runs  4 523 ✅ 357 💤 0 ❌

Results for commit 65460ee.