On Thu, Aug 8, 2024 at 8:58 PM Gregory Nutt <spudan...@gmail.com> wrote:
> > On 8/8/2024 6:48 PM, Nathan Hartman wrote: > > A dedicated "citest" program is a good idea! > I think that ostest could meet all of the needs of a "citest" program. > I just needs more control of the verbosity and format of the output. It > already meets 95% of the requirement. > Ok so perhaps it could use a command line arg to instruct it how much output to produce. Many unix programs have the convention of --quiet for no output, --verbose for full output, and by default only necessary messages. But a CI test might need different output altogether, since it needs to be compared somehow. So, maybe we need a --ci argument that puts the output in a format suitable for automatic CI testing. My thinking is to provide one mode for CI and another (more user friendly) mode for manual testing. I think that's needed because if the CI tests fail, then we would likely want to run it manually and see what isn't working. Just a thought. Cheers Nathan
