You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This worked smoothly for macos-latest and ubuntu-latest github actions, but on windows-latest, I get this error from the last step:
Error: Could not find haxelib "lime", does it need to be installed?
Failed to invoke `haxelib run-dir lime "C:\Users\runneradmin\AppData\Roaming/haxe/haxe_libraries/lime/8.0.1/haxelib"` because Error: Command failed: haxelib run-dir lime "C:\Users\runneradmin\AppData\Roaming/haxe/haxe_libraries/lime/8.0.1/haxelib"
I know lime is installed, so I'm thinking this has to be a scope resolution issue?
I made a new public repo with a minimal reproduction of the error:
In all my debugging I've found that it IS running the lime haxelib, but on the first time lime is run, it has to compile its tools by referencing the output of haxelib path lime. That's where the process is failing to find lime installed, but again, I don't know why windows is the only OS that can't do it.
Commits following that are me trying various things to get it to work, some of which may be trying hacky workarounds while others might be digging for the real problem.
It's so weird that the build DOES work for me locally in git bash on Windows.
In a private cross-platform project I'm using GitHub actions to run my build which goes basically like this:
lix download
to get the dependencieslix run lime build <args>
to run the build.This worked smoothly for macos-latest and ubuntu-latest github actions, but on windows-latest, I get this error from the last step:
I know lime is installed, so I'm thinking this has to be a scope resolution issue?
I made a new public repo with a minimal reproduction of the error:
https://github.com/NQNStudios/lix-lime-debug
The latest action run is here, showing that the same workflow succeeds on ubuntu and macos, but not Windows:
https://github.com/NQNStudios/lix-lime-debug/actions/runs/4943468182
The text was updated successfully, but these errors were encountered: