Closed
Bug 976361
Opened 11 years ago
Closed 11 years ago
occasional failures in vcs2vcs pushes to gecko.git
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: u429623, Unassigned)
Details
(Whiteboard: [re-vcs-sync])
Attachments
(1 file)
15.33 KB,
text/plain
|
Details |
Starting today, the error below has been seen six times, but never before today:
remote: error: denying non-fast-forward refs/heads/v1.3t
The problem always self corrects, but appears to be independent of changes in the repo.
Rough timeline.
Fri, Feb 21 - latest commit to 1.3t (merge from 1.3)
Sat, Feb 22 - box shutdown for bios update & restarted
Mon, Feb 24 - error messages start appearing.
I'll paste a log below
This log shows more detail of the errors than the email messages, and provide context of surrounding operations.
Comment 2•11 years ago
|
||
Hi Hal,
Is this something we should fix, or should we wait to migrate to the new vcs2vcs system, and see if the problem still exists then?
Thanks,
Pete
Unknown if this needs "fixing" or just a one-day anomaly. If it doesn't recur within a week, I'll close, and we'll have a bread crumb if it surfaces again.
Comment 4•11 years ago
|
||
I saw this when there was a branch with the same name on two repos, and they weren't in sync.
https://wiki.mozilla.org/ReleaseEngineering/VCSSync/HowTo#How_to_deal_with_GECKO90_2011121217_RELBRANCH
Not seen since, not enough information to take action closing.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•8 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•