I think I may have run into a similar issue with how tests have changed in CI with 2.9.x MacPorts and the OpenSSH 9.7p1 PR I submitted yesterday:
https://github.com/macports/macports-ports/pull/22981 Going back to reverting to 9.6p1 locally and running port -d -v test I see that it fails with the same error; whereas when the CI checks for that ran with my PR in December of 2023, the CI checks passed. The man page for port test is pretty slim: test Tests portname. So I am guessing this is the spot to reference for more descriptive explanations of test.cmd and test.args https://guide.macports.org/#reference.phases.test Whereas the net/openssh Portfile just has these defined at the moment: test.run yes test.target tests I've include the output of manually invoking "make test" in the following Trac issue I opened regarding this CI buildbot failure: https://trac.macports.org/ticket/69478#comment:2 Which, as you can see, ends with "all tests passed"; so I don't think this is an issue with upstream/OpenSSH's tests. Not to mention, running make tests from the OpenSSH tarball is really quite time consuming and probably not the best use of CI buildbot resources? I can't make heads or tails of this commit from 2.9.0 which introduced the "simple default tests for all ports" https://github.com/macports/macports-base/commit/ddc26554e6ed49ce8501069b967284739fa6d34e But, I am guessing, it's either not that simple, or at a minimum, I might need some additional insights into how to placate it. Thanks!
