-
-
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
Failed to compile ginkgo-arch-specs: output file ".../ginkgo-arch-specs.test" could not be found #495
Comments
Note that if we add an empty test file This should likely be another issue that I can raise separately if you care. |
Interesting @BooleanCat! thanks for raising that. FWITW It think the behaviour of
|
It seems that the result of invoking ginkgo for my example suite is an exit code of -1 - a failure. Running |
I'm working through the backlog of old Ginkgo issues - apologies as this issue is probably stale now. I'll add this to the v2 backlog that's under active development. I agree that this should not result in ginkgo marking the test as failed. The cruft accumulating in /tmp should have been solved a few months ago. |
Ginkgo fails to compile suites that have no specs for an architecture when there are specs for other architectures.
Reproduction
Consider this project: https://github.com/BooleanCat/ginkgo-arch-specs
There is a package
ginkgo_arch_specs.go
, which is tested by:If I
ginkgo run .
this package from an archecture other than linux (I reproduced this with Darwin), then I see:Expectation
I would expect ginkgo to succeed, running 0 specs on Darwin. On Linux, it should run the linux specs.
Notes
This block of code in Ginkgo considers no files existing after a successful go build of the test files to be an error - I don't have contest on why.
The text was updated successfully, but these errors were encountered: