CI are forcing tests for ports where tests are disabled

Joshua Root jmr at
Sun Mar 17 22:50:50 UTC 2024

On 18/3/2024 09:35, Daniel J. Luke wrote:
> On Mar 12, 2024, at 12:20 PM, grey <artkiver at> wrote:
>> 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.
> The test phase (like most other phases) doesn't run as root by default.
> When you run `port test` it's failing because it can't read ssh-keysign which has "-rws--x--x  1 root  admin" permissions (so it /can't/ work).
> You can - stop setting ' yes' since that's the port advertising that 'port test' will work (and it doesn't), tell macports to run the test phase as root (test.asroot yes should work here, but when I did a quick test it didn't and I didn't have a chance to see why), or alter the openssh tests/build to not need to be run as root.

There was also a ticket about this, and some fixes for base have gone 
into git. Until they are released, 'test.ignore_archs yes' can be used 
to disable this particular test for ports that install unreadable files.

- Josh

More information about the macports-dev mailing list