One approach you could use for the test output is to redirect it into a file, and then put a ui message to look at that file for the results.
David On Sat, Sep 20, 2014 at 2:11 PM, Mark Brethen <[email protected]> wrote: > > On Sep 20, 2014, at 10:30 AM, Clemens Lang <[email protected]> wrote: > > > Hi, > > > > ----- On 20 Sep, 2014, at 16:27, Mark Brethen [email protected] > wrote: > > > >> You're thinking it should run automatically instead of user setting? > > > > > > Setting test.run and test.cmd doesn't make MacPorts run the tests > automatically. > > You still have to run `sudo port test` explicitly to run tests. > > > >> Does that change where the output is sent? > > > > No. I'm not aware of a proper method to do this, either. You might be > > able to fiddle with MacPorts' internal verbosity setting, but that > > would be a hack. > > > > -- > > Clemens Lang > > Is the test phase for debugging? > > This script tests each math package in a CAS program after build. Would it > would make more sense to keep this as a variant and the script at > post-build? > > Mark > > > > > _______________________________________________ > macports-dev mailing list > [email protected] > https://lists.macosforge.org/mailman/listinfo/macports-dev >
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
