You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure what this looks like, but a results.txt with some percentages and pass/failure metrics (and types of failures) as well as any surprise failures would be nice. Also, maybe a log of packages that passed both inspection and comparison without error.
The text was updated successfully, but these errors were encountered:
work would be what logs are today; all of the various logfiles tag-runner generates. Reports would be whatever we want to report, though we may need to look at refactoring a few things to clean them up (it has not yet been a focus). Also, I would like a nice general summary to be in the root log directory, so in 2022-07-11-c9s-1 you would see:
report.txt reports/ work/
I also believe to get a good report on which failures we are seeing, I will need to work on #8 to properly consume error messages. I'm also thinking about only appending -2 at the end if more than one run, so something like
logs/2022-07-11-c9s
logs/2022-07-11-c9s-2
But I'm not sure if that's being too clever or not. I like the way it looks, but it may complicate the regex a bit. We'll see.
I'm not sure what this looks like, but a results.txt with some percentages and pass/failure metrics (and types of failures) as well as any surprise failures would be nice. Also, maybe a log of packages that passed both inspection and comparison without error.
The text was updated successfully, but these errors were encountered: