upstream: add a regression test for ProxyJump/-J; ok dtucker #246
vm.yml
on: push
openbsd-current-upstream
29m 1s
Matrix: dragonflybsd
Matrix: freebsd
Matrix: netbsd
Matrix: omnios
Matrix: openbsd
Matrix: solaris
Annotations
15 errors and 1 warning
|
netbsd-9.4
Process completed with exit code 1.
|
|
omnios-r151046
Process completed with exit code 1.
|
|
netbsd-10.0
Process completed with exit code 1.
|
|
omnios-r151054
Process completed with exit code 1.
|
|
openbsd-7.5
Process completed with exit code 2.
|
|
dragonflybsd-6.4.2
Process completed with exit code 1.
|
|
freebsd-13.5
Process completed with exit code 1.
|
|
netbsd-10.1
Process completed with exit code 1.
|
|
openbsd-7.8
Process completed with exit code 2.
|
|
solaris-11.4-gcc
Process completed with exit code 1.
|
|
openbsd-7.6
Process completed with exit code 2.
|
|
netbsd-9.0
Process completed with exit code 1.
|
|
freebsd-14.3
Process completed with exit code 1.
|
|
openbsd-7.7
Process completed with exit code 2.
|
|
openbsd-7.3
Process completed with exit code 2.
|
|
openbsd-current-upstream
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/save@v4, actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|