Repository navigation
Run CI on jolt's nightly build - #13
Merged
Merged
Conversation
The 0.8.2 pin missed jolt 0.8.21 moving the timer onto the monotonic clock, which left every sleep and timeout armed for decades until v0.1.4. Tracking nightly surfaces a breaking jolt change the day it lands. workflow_dispatch can still pick a version for one run.
This file contains hidden or 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
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.
The 0.8.2 pin missed jolt 0.8.21 moving the runtime's timer onto the monotonic clock, which left every sleep and timeout armed for decades until v0.1.4 fixed it. CI now installs jolt's nightly build, so a breaking jolt change shows up the day it lands. The workflow_dispatch jolt-version input still overrides it for a single run, which ci-builds uses to test a candidate release.
The suite passes locally on nightly (v0.8.21-68-g26cd9cd0): 280 tests, 1195 assertions.