Re: CI are forcing tests for ports where tests are disabled

2024-03-17 Thread Joshua Root
On 18/3/2024 09:35, Daniel J. Luke wrote: On Mar 12, 2024, at 12:20 PM, grey 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

Re: CI are forcing tests for ports where tests are disabled

2024-03-17 Thread Daniel J. Luke
On Mar 12, 2024, at 12:20 PM, grey 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 c

Re: CI are forcing tests for ports where tests are disabled

2024-03-12 Thread grey
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

Re: CI are forcing tests for ports where tests are disabled

2024-02-28 Thread Sergio Had
Thank you, Josh, I will look into changing that then. > On Feb 29, 2024, at 2:46 PM, Joshua Root wrote: > > Oh I see, the R portgroup is overriding the test phase entirely, which makes > test.run useless. Don't do that; set test.cmd, test.args and so on. > > - Josh > > On 29/2/2024 18:34, Se

Re: CI are forcing tests for ports where tests are disabled

2024-02-28 Thread Joshua Root
Oh I see, the R portgroup is overriding the test phase entirely, which makes test.run useless. Don't do that; set test.cmd, test.args and so on. - Josh On 29/2/2024 18:34, Sergio Had wrote: I believe, they were not forced for R stuff until /very/ recently. I found a solution which should work

Re: CI are forcing tests for ports where tests are disabled

2024-02-28 Thread Sergio Had
I believe, they were not forced for R stuff until very recently. I found a solution which should work to fix running tests for R packages even when tests are unsupported and forced to run, but this situation is quite fragile. For the context: there are some R packages which are in themselves tr

Re: CI are forcing tests for ports where tests are disabled

2024-02-28 Thread Joshua Root
On 29/2/2024 17:01, Sergey Fedorov wrote: There is something broken with CI now. Tests phase must not be run when it is disabled (test.run is set to no), but it is. Built-in tests can always be run. See 2.9 release notes. - Josh

CI are forcing tests for ports where tests are disabled

2024-02-28 Thread Sergey Fedorov
There is something broken with CI now. Tests phase must not be run when it is disabled (test.run is set to no), but it is.