From b669c2edbdf3661ea1bf39126a2d2d01f81ab161 Mon Sep 17 00:00:00 2001 From: Ed Schouten Date: Wed, 15 May 2024 09:45:39 +0200 Subject: [PATCH] Recommend macOS 14.5 on workers with NFSv4 build directories macOS 14.5 addresses two issues that could cause flakiness when build directories are backed by NFSv4: - Calling open() in parallel against hardlinks stored in different directories could sometimes fail erroneously with ENOENT. - Traversing a symbolic link is hardlinked to a different location that is in the process of being unlinked could also cause ENOENT to be returned spuriously. --- pkg/proto/configuration/filesystem/virtual/virtual.proto | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pkg/proto/configuration/filesystem/virtual/virtual.proto b/pkg/proto/configuration/filesystem/virtual/virtual.proto index 2742b13b..15abb1cd 100644 --- a/pkg/proto/configuration/filesystem/virtual/virtual.proto +++ b/pkg/proto/configuration/filesystem/virtual/virtual.proto @@ -22,8 +22,8 @@ message MountConfiguration { // Run an in-process NFSv4 server and use the kernel's NFSv4 client // to expose the mount. This option is supported on macOS starting - // with Ventura 13.3 (22E252), though the use of Sonoma 14.4 - // (23E214) or later is strongly recommended. + // with Ventura 13.3 (22E252), though the use of Sonoma 14.5 + // (23F79) or later is strongly recommended. // // The NFS server is expected to conform to NFSv4.0 (RFC 7530). // Features provided by newer versions of the protocol, such as