-
Hi, When I try to run a Windows executable in my GH action I get
Running this locally works just fine. I have been trying to search the net for a solution but haven’t managed to fine one. |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments
-
Please try to install a self-hosted runner on the local machine, then use this self-hosted runner to run the “build_windows” job to see if the problem still exists. Not sure if the “jurplel/install-qt-action@v2” action has setup the completed required Qt environments on the runner. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the reply. I can test a local runner. Right now I simply tried to remove the Qt install now and I get the same issue with the remote (default) runner. The script looks like this now
So all it’s doing is to checkout the repo and try to run the executable and with the same result. I will likely try to just build the executable used from source instead and see if it works then. |
Beta Was this translation helpful? Give feedback.
-
It’s strange that the command “bin\windows\tundra2.exe win64-msvc-debug” can work fine if you directly run it on your local machine that has Qt installed, but does not work when running on the self-hosted runner installed on this machine. There may be some issues occur when run this command via the runner application. |
Beta Was this translation helpful? Give feedback.
-
Thanks! Also notice that this application doesn’t require Qt to be installed. It do rely on scripts and files that are included in the repository but if something of those should be missing the program should report it. Right now it seems like Windows can’t run the executable at all for some reason. |
Beta Was this translation helpful? Give feedback.
-
Hey, some more updates here: It actually turns out that the I tracked it down to this code
And I added some more info now and the output is
(I have added the source code to the repo so I can do changes to it) the 5 is the error code from
So for some reason the code above isn’t allowed create a new process. I will speak with the author of this code, but I still find it strange it doesn’t run correct on the builder instance. |
Beta Was this translation helpful? Give feedback.
-
And another update: So now have a work-around for the problem. We aren’t actually fully sure but it might that the VMs are configured in such way that creating a process with In this case the code that does this isn’t actually needed when running on a CI fashion as it’s only there for handling aborting a build (ctrl+c) which doesn’t happen in this here. |
Beta Was this translation helpful? Give feedback.
-
Hello, @emoon |
Beta Was this translation helpful? Give feedback.
-
Thanks! Great bug report :slight_smile: |
Beta Was this translation helpful? Give feedback.
And another update:
So now have a work-around for the problem. We aren’t actually fully sure but it might that the VMs are configured in such way that creating a process with
CREATE_NEW_PROCESS_GROUP
isn’t supported perhaps for some security reason.In this case the code that does this isn’t actually needed when running on a CI fashion as it’s only there for handling aborting a build (ctrl+c) which doesn’t happen in this here.