GNU testsuite comparison:

Skip an intermittent issue tests/misc/tee (fails in this run but passes in the 'main' branch)
Skip an intermittent issue tests/timeout/timeout (fails in this run but passes in the 'main' branch)

CodSpeed Performance Report

Merging #8790 will not alter performance

_{Comparing oech3:wrap-ln (d213e49) with main (be25344)}

Summary

✅ 69 untouched
⏩ 73 skipped¹

@ognevny Does uutils-coreutils of MSYS2 need to have hardlinks of multi-call binary by default?

multicall binary uses symlinks. there are problems with shipping them, so we use "classical" approach with distributing individual binaries. https://www.msys2.org/docs/symlinks/

edit: oh, I see. hard links are acceptable for us, because they are supported in older versions of Windows

I don't know does pacman of MSYS2 support hardlink. If supported, I'll make LN=ln default on win.

I don't know does pacman of MSYS2 support hardlink

it's supported. we have a whole package with hardlinks!

Failing tests by network err: #8787 (comment)

GNU testsuite comparison:

Skipping an intermittent issue tests/timeout/timeout (passes in this run but fails in the 'main' branch)

GNU testsuite comparison:

Skip an intermittent issue tests/tail/overlay-headers (fails in this run but passes in the 'main' branch)
Skip an intermittent issue tests/timeout/timeout (fails in this run but passes in the 'main' branch)

@ognevny It seems hardlink patch is not enough and MULTICALL=y fails on MSYS2 because of missing gmake.exe. pacman -F gmake.exe returns none. Simply sed -i "s/gmake/make/" did not help.

missing gmake.exe. pacman -F gmake.exe returns none

gmake is also not presented on Archlinux, so it shouldn't be used at all

It seems gmake err happen if I tried to backport hardlink feature by sed.
I can build MULTICALL=y with manually applied patch on MSYS2.