Skip to content

Very many epochs/* tags accumulating, can they be garbage collected? #28764

Open
@foolip

Description

#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:

commit c2df3bee8330f8058bd15a59e51567d423ed3a81 (tag: merge_pr_28741, tag: epochs/twelve_hourly/2021-04-30_12H, tag: epochs/three_hourly/2021-04-30_12H, tag: epochs/six_hourly/2021-04-30_12H, origin/master, origin/epochs/twelve_hourly, origin/epochs/three_hourly, origin/epochs/six_hourly, origin/HEAD)
Author: Antonio Sartori <[email protected]>
Date:   Fri Apr 30 13:12:21 2021 +0200

    Fix the Stash Lock to be unique (#28741)
    
    Co-authored-by: Antonio Sartori <[email protected]>

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?

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions