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
In a nutshell, a task with an inexistent script should raise a "No such file or directory (os error 2)" error message, but it raises "Task exited with status: exit status: 127" instead on aarch64.
127 being the status code for command not found.
@vlaci I think it should be reported to devenv, right ?
In a nutshell, a task with an inexistent script should raise a "No such file or directory (os error 2)" error message, but it raises "Task exited with status: exit status: 127" instead on aarch64.
127 being the status code for command not found.
@vlaci I think it should be reported to devenv, right ?
Devenv's using an old pinned nixpkgs, so the issue won't pop-up for regular users.
I've made a PoC to allow updating it, which was picked up by the maintainers there cachix/devenv#1489
Unfortunately there are other cases, where it doesn't work correctly. I look into it.
Our Build Nix workflow is failing with these exceptions when built for aarch64 Linux :
There's no mention of this on the devenv issue tracker. Not sure if the problem is coming from devenv or the action runner itself.
The text was updated successfully, but these errors were encountered: