Closed
Bug 623682
Opened 15 years ago
Closed 15 years ago
hg.m.o/build/buildbotcustom has some broken tags, needs cleanup
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joduinn, Assigned: bhearsum)
Details
(Whiteboard: [release][tag cleanup])
$
$ hg clone http://hg.mozilla.org/build/buildbotcustom
destination directory: buildbotcustom
requesting all changes
adding changesets
adding manifests
adding file changes
added 1204 changesets with 1543 changes to 98 files (+3 heads)
updating working directory
.hgtags@8546abc704ee, line 93: tag 'FIREFOX_3_6_9_BUILD1' refers to unknown node
.hgtags@8546abc704ee, line 94: tag 'FIREFOX_3_6_9_RELEASE' refers to unknown node
.hgtags@2a101d9a4044, line 93: tag 'FIREFOX_3_6_9_BUILD1' refers to unknown node
.hgtags@2a101d9a4044, line 94: tag 'FIREFOX_3_6_9_RELEASE' refers to unknown node
77 files updated, 0 files merged, 0 files removed, 0 files unresolved
host-3-19:mozilla_repo_hg john$
$
| Reporter | ||
Updated•15 years ago
|
Summary: hg.m.o /builds/buildbotcustom has some broken tags, needs cleanup → hg.m.o/build/buildbotcustom has some broken tags, needs cleanup
Comment 1•15 years ago
|
||
armenzg and jhford - can you take a look at this because the only two merge/commits that come any where near this revision chain are the ones you did.
so one of your merges is causing this issue.
Updated•15 years ago
|
Whiteboard: [release][tag cleanup]
Updated•15 years ago
|
Priority: -- → P3
Comment 2•15 years ago
|
||
It is unrelated.
This has been like this for months.
Comment 3•15 years ago
|
||
(In reply to comment #2)
> It is unrelated.
> This has been like this for months.
I believe that's the point. The repo has been broken in this particular way since 3.6.9. Bear tracked down the commits from that time period and you and jhford are on the hook.
Comment 4•15 years ago
|
||
fwiw, this isn't a problem on hg 1.6 or hg 1.7, which is why some folks can't reproduce locally.
Comment 5•15 years ago
|
||
then is the issue not jhford and/or armenzg's at all?
we should get joduinn to upgrade his HG?
Comment 6•15 years ago
|
||
well, hg is right, that the revision for FIREFOX_3_6_9_BUILD1 and FIREFOX_3_6_9_RELEASE doesn't exist. It's pointing to df8c105142f7e2cd0ced8513e46cd2fb78451d0c.
We should update .hgtags to point to the right revision if we can figure out what it is.
Comment 7•15 years ago
|
||
k, i'll due some digging and try and find it then ask you for a review.
Assignee: nobody → bear
Comment 8•15 years ago
|
||
ok, found the source commit that caused this
Added tag FIREFOX_3_6_9_RELEASE for changeset df8c105142f7 Changeset 7579b62d6b52: 4 months ago ago, by Ben Hearsum
Added tag FIREFOX_3_6_9_BUILD1 for changeset df8c105142f7 Changeset 4b0a8d90ec42: 4 months ago ago, by Ben Hearsum
assigning to bhearsum for the moment
Assignee: bear → bhearsum
| Assignee | ||
Comment 9•15 years ago
|
||
I manually edited .hgtags on all of these branches and the errors are gone.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•