From https://github.com/uutils/coreutils-tracking/blob/main/gnu-full-result.json, here are the remaining GNU test cases that are marked as ERROR (as opposed to FAIL, PASS, or SKIP):

• tests/cp/cp-parents.sh - see cp-parents.sh: cp: recursive copy #3332, cp: correctly copy ancestor dirs in --parents mode #3894, cp: correctly copy ancestor dirs in --parents mode #4071
• tests/cp/preserve-slink-time.sh - see cp: --no-dereference option should copy dangling symbolic link but doesn't #3364, cp: error when trying to preserve metadata on dangling symbolic link #3531
• tests/cp/sparse-extents.sh - see cp: implement --sparse option #3362
• tests/cp/sparse.sh - see cp: implement --sparse option #3362
• tests/dd/no-allocate.sh - see dd: seek should cause a read from named pipe but doesn't #3321
• tests/ls/nameless-uid.sh - see chown: fails to set owner given as a UID number #3380
• tests/misc/csplit-io-err.sh - see Panic in multiple programs when redirecting stdout to /dev/full #2925
• tests/misc/shuf.sh - see shuf: accept multiple occurances of head-count argument #3329
• tests/misc/usage_vs_getopt.sh
• tests/split/filter.sh - see split: implement round-robin arg to --number #3281
• tests/tail-2/inotify-rotate-resources.sh - implemented in pull request tail overhaul (--follow=name, etc.) #2695 but errors due to

  coreutils/src/uu/tail/README.md

  Lines 35 to 38 in 702a0b7

  	The functionality for the test "gnu/tests/tail-2/inotify-rotate-resources.sh" is implemented.
  	It fails with an error because it is using `strace` to look for calls to `inotify_add_watch` and `inotify_rm_watch`,
  	however in uu_tail these system calls are invoked from a separate thread.
  	If the GNU test would follow threads, i.e. use `strace -f`, this issue could be resolved.

It would nice to get them from ERROR to at least FAIL.