-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Haskell windows 2019 fails with version check #3223
Comments
@AHuusom Thanks for your fix. However, it looks like we need to raise the issue in the choco repository because we should have 3 latest versions, but not 3 random versions |
@miketimofeev Choco definetely gives you over 3 versions... but the sorting done by the code to get the latest was faulty, as it sorted on the count instead of the version naming. |
@AHuusom yeah, it gives, but sometimes not all the versions |
Created a bug in the choco repository regarding version 9.0.1 |
We've implemented a test to make sure version 9.* is installed. |
It's failing now again. |
@AHuusom test is failed if version 9.0.1 is not found among the others. We did it intentionally to avoid a sudden GHC downgrade. I've created an issue in choco repo regarding inconsistent search chocolatey/choco#2271 |
Thanks, I followed the link to the issue and integrated the Odata query in our solution so our build doesn't fail. |
Description
The sorting mechanism on the versioning is off and shows 3 different outcomes on 3 different VMS.
The if statement testing if version is < 8 is testing against a unused variable.
Area for Triage:
Haskell
Question, Bug, or Feature?:
Bug
Virtual environments affected
Image version
?
Expected behavior
That it sets the newest version as default
Actual behavior
As the sorting mechanism isn't working, if version 9 is shown as the newest it works as haskell path is always set to the versions 9's executable.
This is because it tests against a $null variable and thus always sets the path to version 9
Repro steps
Just run the haskel section on windows 2019
I've made a PR with the corrections [/pull/3219] please review it
The text was updated successfully, but these errors were encountered: