-
Notifications
You must be signed in to change notification settings - Fork 0
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
[ci] make ci green again #1573
[ci] make ci green again #1573
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the reason is that multiple ci runs may be happening concurrently on the same machine, so no test/ci-run can use a fixed port number...
3a6277a
to
e18a98d
Compare
current issueseems to be introduced here
@4meta5 would you please fix it? (for some reason that job wasn't run at the time of your merge, but it definitely was broken at that time) |
@FlorianFranzen is removing the migration to fix it, it is weird because it compiles locally for me and the files and declarations are there |
Removed any migrations that were no longer needed (including the one bracking chronicle image builds). Should be ready to go. Will merge it once CI passes. |
recent PR broke merging ci jobs, let's fix it