Windows task fails but doesn't appear in red and the task continues executing commands

[vinferrer]

Question

Hi , I was checking my jobs and I realized that even if there are errors in my windows jobs, the cirrus-CI webpage shows them as done correctly. For example this one: https://cirrus-ci.com/task/6202306100199424
Is there a way to correct this behavior? it would be annoying to have to check manually everytime if windows jobs are working properly

[fkorotkov]

That's weird. This is how Cirrus Agent generates a PS script to execute https://github.com/cirruslabs/cirrus-ci-agent/blob/master/internal/executor/cmd_windows.go#L63-L78 and it deliberately sets ErrorActionPreference. Does your Makefile make any changes that can chnage how Powershell reports exit code?

[vinferrer]

not at all: https://github.com/vinferrer/phys2bids/blob/master/Makefile . If you notice the work should stop before the makefile in the populate_enviroment_cache script

[vinferrer]

Maybe is not detecting the error from pip? that's the first command that should trigger failure

[vinferrer]

Could you comment when you have more info about this? I am gonna need to keep track of windows jobs for the moment

[fkorotkov]

I'm actually trying to investigate it. It does look like an issue with EXEs and Powershell as I found in this Stackoverflow issue. I don't see any Powershell specific things that you do so could you please try to remove SHELL: powershell environment variable?

[vinferrer]

Let me try, I am gonna open a new branch for this

[vinferrer]

I just open a new branch and delete the SHELL:powershell from some of the tests, now those tests are failing, but from completely different reasons than before. Right now the job is not detecting pip:
failing job: https://cirrus-ci.com/task/6232965623578624
cirrus ci yml: https://github.com/vinferrer/phys2bids/blob/c00253263653c92e96909d850ef0818a0fdcbb43/.cirrus.yml#L47

Seems like the problem is powershell, but I builded my scripts on powershell config :(

[vinferrer]

I managed to fix my tests without using powershell. If you want we can close this issue

[fkorotkov]

@vinferrer glad it worked. Sorry I wasn't that helpful. 😪