-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Very many epochs/* tags accumulating, can they be garbage collected? #28764
Comments
I knew about the command
I didn't had a need to use them, since there wasn't any issue reported with the CI and WebKitGTK builds since then. If no one else is finding this useful, then I agree it is a good idea to revert #26122 and document |
BTW; I'm quickly checking if all commits annotated via tags are reported by
Result:
Those have an epoch tag but doesn't seem to appear in the |
I've sent web-platform-tests/rfcs#117 to drop these tags. |
#26122 introduced tags for pushes to the epochs/* branches, in order to have a record of what those branches had pointed to in the past. That's resulted in over 2000 such tags since then, which are pretty prominent in git log:
It's not a big problem, but I wonder if these tags have helped debug issues, @clopez?
In the issue the challenge was identifying the commit that triggered the taskcluster run on epochs/daily for October 12, 2020.
The commit should be one listed by
./wpt rev-list --epoch 1d --max-count=365
. Looking at./wpt rev-list --epoch 1d --max-count=365 | xargs git log --no-walk --pretty=fuller
I think it was 1b2893a, and clicking through to https://community-tc.services.mozilla.com/tasks/MRVToMMNQjOG7npZAfF0jQ confirms it.Being able to list the right commits after the fact was an intentional part of how
./wpt rev-list
was implemented, but it's not documented how to figure this out anywhere.@clopez did you recall if you looked for documentation about this anywhere? If you did, then maybe we can put documentation there, and stop creating the tags?
The text was updated successfully, but these errors were encountered: