-
-
Notifications
You must be signed in to change notification settings - Fork 650
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
ginkgo refuses to run pre-compiled test binary on Windows #1296
Comments
hey @jgrieger are you up for a PR for this? i think my preferred approach here would be to only enforce the executable bit check if the OS is not windows, but i don’t have a windows machine so it’s possible something else gets in the way further downstream - if you could try to put something together and validate that it works for you that would be great. |
Sure, working on it. |
thanks! |
@onsi I think we have two options here:
Option 1Pro
Contra
Option 2Pro
Contra
What do you think? |
hey @jgrieger thanks for taking the time to explore options. I’d go the simpler route - option 1 - those non-executable files aren’t actually going to run any tests and succeed and so the user will get an error even if the file in question gets past the guard. Thanks! |
PR #1301 created. |
merged it in, thanks! i’ll cut a release soon. |
Great, thanks! |
2.13.1 is out now. You can close this out if you're happy with where we've ended up. Thanks for the PR! |
Thank you for your support, much appreciated :-). |
If I run
ginkgo build \my-package-dir
on Windows (21H2), the output is my-package.test binary.If I run
ginko my-package.test
, the validation in https://github.com/onsi/ginkgo/blob/7161a9d90a24fd70df1e687b71d4ae186ec85dd7/ginkgo/internal/test_suite.go#L195C33-L195C33 fails, because Go does not provide the executable bit in Windows (see golang/go#41809).The workaround is to rename the test binary to my-package.exe.
This is related to #529.
The text was updated successfully, but these errors were encountered: