rsync/.github/workflows/openbsd-build.yml at master · RsyncProject/rsync · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
name: Test rsync on OpenBSD

concurrency:
  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.run_id }}
  cancel-in-progress: true

on:
  push:
    branches: [ master ]
    paths-ignore:
      - '.github/workflows/*.yml'
      - '!.github/workflows/openbsd-build.yml'
  pull_request:
    types: [opened, synchronize, reopened]
    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 --disable-idn
          make
          ./rsync --version
          # The flipper (symlink-race) tests are excluded on OpenBSD, as on the
          # fleet's OpenBSD box: this kernel has a connect()-under-rename-load
          # lost-wakeup and an FFS rename-storm corruption that hang them to
          # the 300s timeout for non-rsync reasons (see
          # dev-notes/openbsd-connect-lost-wakeup-report.txt); the protections
          # they exercise are verified on the Linux/BSD boxes.
          export RSYNC_EXCLUDE=acl-symlink-race,sender-readlink-atfd,sender-remove-source-secure
          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