Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generate a nice summary from the log files #4

Open
jimbair opened this issue May 12, 2022 · 1 comment
Open

Generate a nice summary from the log files #4

jimbair opened this issue May 12, 2022 · 1 comment
Assignees

Comments

@jimbair
Copy link
Collaborator

jimbair commented May 12, 2022

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.

@jimbair jimbair self-assigned this Jul 7, 2022
@jimbair
Copy link
Collaborator Author

jimbair commented Jul 11, 2022

I see this going something like this:

logs/$(date +%F)-${profile}-${num}, where $num is 1 and we ++ if we have subsequent re-runs. So like today that would be

logs/2022-07-11-c9s-1
logs/2022-07-11-c9s-2

Then below that we have two folders: reports and work

logs/2022-07-11-c9s-1/reports
logs/2022-07-11-c9s-1/work

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant