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

compilation should fail if wrong nim_commit was specified #101

Merged
merged 1 commit into from
Jan 23, 2025

Conversation

cskiraly
Copy link
Contributor

Previously, if there was an unavailable version specified, there was an error message, but then compilation went on using another Nim version.

@cskiraly cskiraly requested a review from tersec January 21, 2025 17:16
@tersec
Copy link
Contributor

tersec commented Jan 21, 2025

Well, the CIs are all failing.

But conceptually I agree with this change.

@cskiraly cskiraly force-pushed the fix-silent-checkout-failure branch from f247823 to 536311a Compare January 21, 2025 18:20
Previously there was an error message, but then compilation went
on with another Nim version.

Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
@cskiraly cskiraly force-pushed the fix-silent-checkout-failure branch from 536311a to d0e2138 Compare January 21, 2025 18:22
@cskiraly
Copy link
Contributor Author

Should be better now, but let's wait it out.
The problem was triggered for us when a space made it to the end of a version string, leading to failing checkout but still compiling with the wrong nim version (v2.0.14 instead of the specified 'somehash ').

@tersec tersec merged commit 5f10509 into master Jan 23, 2025
20 checks passed
@tersec tersec deleted the fix-silent-checkout-failure branch January 23, 2025 15:46
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