-
Notifications
You must be signed in to change notification settings - Fork 66
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
[DRAFT] Automatic tracking of statistics after each commit #479
base: main
Are you sure you want to change the base?
Conversation
Out of curiosity I went through the stats files checked in on the PR and I noticed that 20 of them showed a usage message rather than displaying statistics, is this behavior intentional?
|
Ah no. It looks the file existed at that point, but didn't support --hist. I'll backport that too. |
This looks excellent! I wrote a parser and got the following numbers:
Does everything look accurate? |
It's strange that the number of open problems increased from 10-02 to 10-03... possibly some flaw in the transitive closure algorithm? |
Yes, something seems off with the first entries. Here is the underlying data for the corresponding commits:
The later entries -- such as |
I'm really excited about this PR, and I’d love to build tooling on top of it. What’s still left to be done? |
Hey @carlini, feel free to reach out if you'd like any help getting this PR ready for merging! I'd like to see it in |
This PR is the first step to log data about how far the project has progressed over time. Right now I've run the
extract_implications --hist
tool for every commit from when the tool was created until this morning. I'll start back-filling the remaining commits by cherry-picking the extraction tool into the past.Once I've completed the backfill, I'll try to get the CI to automatically add one of these files with each PR. I have an idea for how to do this but it'll take a bit of work. and will discuss this on issue #171.