From c809bb3888921feb5d3d00ceae51f0743d1ca89c Mon Sep 17 00:00:00 2001
From: Joining7943 <111500881+Joining7943@users.noreply.github.com>
Date: Sat, 28 Jan 2023 13:02:30 +0100
Subject: [PATCH] tests/tail: Disable test_follow_with_pid on freebsd because
 of intermittent failures in the ci

---
 tests/by-util/test_tail.rs | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/tests/by-util/test_tail.rs b/tests/by-util/test_tail.rs
index a82d66565..5670e23c9 100644
--- a/tests/by-util/test_tail.rs
+++ b/tests/by-util/test_tail.rs
@@ -626,11 +626,14 @@ fn test_follow_invalid_pid() {
 }
 
 // FixME: test PASSES for usual windows builds, but fails for coverage testing builds (likely related to the specific RUSTFLAGS '-Zpanic_abort_tests -Cpanic=abort')  This test also breaks tty settings under bash requiring a 'stty sane' or reset. // spell-checker:disable-line
+// FIXME: FreeBSD: See issue https://github.com/uutils/coreutils/issues/4306
+//        Fails intermittently in the CI, but couldn't reproduce the failure locally.
 #[test]
 #[cfg(all(
     not(target_vendor = "apple"),
     not(target_os = "windows"),
-    not(target_os = "android")
+    not(target_os = "android"),
+    not(target_os = "freebsd")
 ))] // FIXME: for currently not working platforms
 fn test_follow_with_pid() {
     use std::process::Command;