Test rsync on OpenBSD #527

	name: Test rsync on OpenBSD

	on:
	push:
	branches: [ master ]
	paths-ignore:
	- '.github/workflows/*.yml'
	- '!.github/workflows/openbsd-build.yml'
	pull_request:
	branches: [ master ]
	paths-ignore:
	- '.github/workflows/*.yml'
	- '!.github/workflows/openbsd-build.yml'
	schedule:
	- cron: '42 8 * * 1'

	jobs:
	test:
	runs-on: ubuntu-latest
	name: Test rsync on OpenBSD
	steps:
	- uses: actions/checkout@v4
	with:
	fetch-depth: 0
	- name: Test in OpenBSD VM
	id: test
	uses: vmactions/openbsd-vm@v1
	with:
	usesh: true
	prepare: \|
	pkg_add -I bash autoconf%2.71 automake%1.16
	run: \|
	uname -a
	export AUTOCONF_VERSION=2.71
	export AUTOMAKE_VERSION=1.16
	./configure --with-rrsync --disable-zstd --disable-md2man --disable-xxhash --disable-lz4
	make
	./rsync --version
	make check
	# The --use-tcp daemon tests run at -j2 here (vs -j8 elsewhere): this
	# job runs inside a nested VM, and at -j8 the many concurrent loopback
	# daemons occasionally lose a connection-handshake timing race under
	# that resource pressure, hanging one test to the 300s timeout. It is
	# an environment artifact, not an rsync bug (the handshake is
	# deadlock-free and unreproducible elsewhere, even pinned to 1 CPU at
	# -j8); -j2 keeps the VM from over-subscribing. The pipe `make check`
	# above stays at the default parallelism.
	./runtests.py --rsync-bin=`pwd`/rsync --use-tcp -j 2
	./rsync-ssl --no-motd download.samba.org::rsyncftp/ \|\| true
	- name: save artifact
	uses: actions/upload-artifact@v4
	with:
	retention-days: 45
	name: openbsd-bin
	path: \|
	rsync
	rsync-ssl
	rsync.1
	rsync-ssl.1
	rsyncd.conf.5
	rrsync.1
	rrsync

Provide feedback