Repository navigation
Pin lint-mojo 0.1.2 (portable mojolint binary) - #8
Merged
Merged
Conversation
lint-mojo 0.1.1 built mojolint for the host CPU of whichever runner compiled it; the cached env then hit an illegal instruction on runners without AVX-512, which is why every ubuntu lint job went red today. 0.1.2 builds the binary for x86-64-v2 on linux-64. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Pin-only change:
lint-mojo2a12807b(0.1.1) →3fa66644(0.1.2), lock regenerated with pixi 0.78.0.Why. 0.1.1 built the
mojolintbinary withmojo build's default target, i.e. the host CPU of whichever runner compiled it into the pixi env. setup-pixi caches that env, GitHub's ubuntu runners are a mix of AVX-512 and non-AVX-512 machines, and the cached binary died withIllegal instructionon the wrong ones — that is why every ubuntu lint job in the org went red today. 0.1.2 (magmalake/lint.mojo#5) builds the linux-64 binary forx86-64-v2and has a CI guard that fails on anyymm/zmmregister in the shipped binary.This repo's own sources already compile without deprecation warnings under the current toolchain, so there is nothing else to change and no version bump.