Docker, CI: Make JS integration tests more robust; update screenshots #1021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This prevents unexpected jumps in Debian releases when the `:current` tag changes and makes screenshot rendering more predictable
Font rendering seems to have changed once again with the jump from Debian Buster to Bookworm (the Dockerfile was updated to pin Bookworm with Node 22)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
CHANGES.rstbecause this is a user-facing change or an important bugfixWhat changes does this Pull Request introduce?
docker-js-testbedimage weekly so that it doesn't get outdated and introduce subtle errors (previously, I - @ix5 - was building and pushing this image manually)testbedDockerfileto Debian Bookworm with Node 22:currentwas implicitly updating the testbed image to Bookworm already)Why is this necessary?
Flaky tests