Skip to content

Conversation

anoadragon453
Copy link
Member

@anoadragon453 anoadragon453 commented Aug 14, 2025

This broke very quietly in #158 (See https://github.com/matrix-org/rust-synapse-compress-state/actions/runs/16938635005). So the first commit fixes the syntax.

The second commit changes the solution completely, as apparently exit 0 will not skip the rest of the job. Instead, we need to do a bunch of ifs.

@anoadragon453 anoadragon453 requested a review from a team as a code owner August 14, 2025 09:48
@anoadragon453 anoadragon453 force-pushed the anoa/fix_docker_workflow branch from a1cee1f to 231e44a Compare August 14, 2025 09:49
latest=false
tags: |
type=raw,value=latest,enable=${{ github.ref == 'refs/heads/main' }}
type=sha,prefix=,format=long

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm confused how/why we can't see the failures from #158 ?

Do we need to require some jobs succeed in order to notice this?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point - indeed it looks like we do. I've added a ruleset that requires all CI checks complete -> https://github.com/matrix-org/rust-synapse-compress-state/settings/rules/7412288

And now we can see that build is not passing on #160 (as this PR hasn't merged yet). Whereas before it was just completely green.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better than nothing. I wish we could see the failure as well.

Currently, it just says "Waiting for status to be reported" without any link to see the syntax problem

2025-08-14_13-42

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed, and I wish you could just click on "build" there instead of needing to go to the Checks tab and clicking on the workflow. But it's a strong signal at the very least.

We were failing to push cached images to the registry, because we're no
longer logging to the GHCR. In addition, secrets.GITHUB_TOKEN would need
to be expanded to support writing to the container registry, and giving
that to arbitrary PRs isn't great.

The GitHub Actions build cache is auto-clearing after 7 days, and
requires no auth.
Taken from #160, so the action knows what the 'gha' backend is.
Comment on lines 68 to 69
cache-from: type=registry,ref=ghcr.io/${{ github.repository }}:buildcache
cache-to: type=registry,ref=ghcr.io/${{ github.repository }}:buildcache,mode=max
cache-from: type=gha
cache-to: type=gha,mode=max
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@anoadragon453 anoadragon453 merged commit 554f309 into main Aug 19, 2025
5 checks passed
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.

2 participants