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
fsnotify v1.5.0 and GOOS=freebsd does not build #389
Comments
Thanks for the report. Confirmed that changes in 1.5.0 via #289 began using /cc @Code0x58 |
Of note, we don't have FreeBSD as a GitHub runner, because they only supports Linux, Windows, and macOS. They do support custom runners as one possibility. Or we may be able to use the the same trick that #371 is using for Solaris? I don't currently have a FreeBSD environment set up -- I was using Vagrant before, but I haven't worked with it for a while. |
See https://github.com/vmactions/freebsd-vm / https://github.com/marketplace/actions/freebsd-vm |
v1.5.1 reverts the changes from 1.5.0, but lets leave this open to review. |
I do not have BSD to test on. Please report back whether 1.5.1 resolved the issue. |
Ran |
@r-darwish Any chance you could help me write a github action that uses https://github.com/vmactions/freebsd-vm similar to the one I'm working on for illumos (see nshalman@96066fd) to run the tests on FreeBSD? It would be great to be able to catch these things in the future, even if we have to trigger the tests manually because they're too slow to run on every push/pr. |
It occurs to me that cross-compilation builds might also have caught this. |
This would have caught fsnotify#389 and should catch build failures for supported targets.
This would have caught #389 and should catch build failures for supported targets.
GOOS=freebsd go
build works with Go 1.17 and fsnotify v1.4.9, but stops working with fsnotify v1.5.0.The error message is:
The text was updated successfully, but these errors were encountered: