Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pin sybil to < 6.1 #262

Merged
merged 2 commits into from
May 3, 2024
Merged

Pin sybil to < 6.1 #262

merged 2 commits into from
May 3, 2024

Conversation

llucax
Copy link
Contributor

@llucax llucax commented May 3, 2024

This is a temporary workaround until #249 is fixed.

@llucax llucax requested a review from a team as a code owner May 3, 2024 09:33
@github-actions github-actions bot added the part:tooling Affects the development tooling (CI, deployment, dependency management, etc.) label May 3, 2024
@llucax llucax self-assigned this May 3, 2024
@llucax llucax added this to the v0.10.0 milestone May 3, 2024
@llucax llucax enabled auto-merge May 3, 2024 09:33
@llucax llucax enabled auto-merge May 3, 2024 09:40
@llucax llucax added this pull request to the merge queue May 3, 2024
llucax added 2 commits May 3, 2024 11:49
Sybil 6.1.0 fixes a bug which we thought it was proper behavior, so
upgrading to it would break our tests.

This is a temporary workaround until we fix our code to work with the
new sybil version.

Signed-off-by: Leandro Lucarella <[email protected]>
Merged via the queue into frequenz-floss:v0.x.x with commit e45fd51 May 3, 2024
10 checks passed
@llucax llucax deleted the pin-sybil branch May 3, 2024 09:53
@llucax
Copy link
Contributor Author

llucax commented May 3, 2024

There is something funny going on with branch protection using rulesets, now this PR got merged even if the tests were failing. I pushed a fix but what was merged was the unfixed versions. Not sure if we hit a race condition or what but I have been observing a lot of weird behavior with PRs being merged when merge queue tests failed and now this, which should have not been queued at all.

@llucax llucax mentioned this pull request May 3, 2024
github-merge-queue bot pushed a commit that referenced this pull request May 3, 2024
Should have been part of #262.
@llucax llucax modified the milestones: v0.10.0, v0.9.2 May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
part:tooling Affects the development tooling (CI, deployment, dependency management, etc.)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants