Skip to content
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

Cancelled jobs report an exit code of 0 on Windows #1489

Closed
keithduncan opened this issue Aug 19, 2021 · 4 comments · Fixed by #2741
Closed

Cancelled jobs report an exit code of 0 on Windows #1489

keithduncan opened this issue Aug 19, 2021 · 4 comments · Fixed by #2741

Comments

@keithduncan
Copy link
Contributor

This is inconsistent with Linux (haven’t tested on macOS). We should make this behaviour the same across all operating systems.

@twometresteve
Copy link

Works fine for us here on macOS, but fixing it on Windows would be great - thank you.

@staticfloat
Copy link
Contributor

I can confirm that this is occurring as well. If there's any need for debugging (we have a fleet of Windows VMs that we run in buildkite) I'd be happy to deploy changes for testing, etc...

@twometresteve
Copy link

After looking at this more, we came to the conclusion that it was down to the behaviour of Windows (try interrupting a running batch script and query the exit code - it's always 0). We just dodged the bullet enitely by using the Linux agent under WSL - to very good effect.

@JustinTether
Copy link

We're also running into this issue which has been causing some confusion when looking at a green cancelled step -- We found that we could get more accurate states by removing the artifact_paths keys from our steps and artifacting manually

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants