Closed rdmark closed 7 months ago
@dgsga These failures were previously hidden by a quirk of the vmactions runners. It turns out that if any command in the run
block passes, the entire step counts as a pass. I added set -e
to the head of the block to make them bail out when a non-0 exit code is encountered.
Yes, I've been aware of this for a while. I think the fault lies with the vmactions VM's as tests pass on both platforms on my ESXi setup. I'm not sure where to start looking atm. The problem with these VM's is that they get out-of date very quickly as we have seen with the Dragonfly one. The ideal solution would be to use docker containers for all the *BSD platforms.
The vmactions runners have proven a bit unreliable, indeed. I might take a look myself later.
Discarding this, with the reasoning that the vmactions VMs have been proven unstable.
The integration tests are failing when run on FreeBSD or OpenBSD on the vmactions runners.
FreeBSD
OpenBSD