-
Notifications
You must be signed in to change notification settings - Fork 13.4k
remote file lock issue causes a panic #84417
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Just in case the backtrace helps at all, I re-ran it with the backtrace enabled:
|
So I posted this from a MacOS client, but I also tried it via a FreeBSD machine. The underlying lack of graceful exit on the Mac still exists when it can't get a file lock. But I solved the fundamental issue on my infrastructure allowing network file locking to function properly. |
Thanks for the report! Incremental builds requiring working file locks is a known issue (#49773, #59224, #66513, #76251). I believe there are some limitations of smb on macOS. The compiler at least shouldn't panic. Some workarounds are to use a target directory on the local filesystem, or disable incremental. Since there are multiple issues for this, I'm going to close this as a duplicate of #59224 (which mentions macos). |
running on Mac OS 10.13.6 to a network file system hosted on FreeNAS via smbfs.
The text was updated successfully, but these errors were encountered: