Closed Bug 585082 Opened 14 years ago Closed 14 years ago

graphs does not recognise the "Firefox-Release" branch

Categories

(Release Engineering :: General, defect, P2)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Assigned: armenzg)

References

Details

Attachments

(2 files, 2 obsolete files)

While I was doing the build3 for Beta 3 I had to do sendchanges manually because there is some bug that does not trigger the unit tests and the talos jobs on the minis.

Once I constructed the correct sendchanges I saw the talos jobs being triggered but to my surprise they did not work saying that the "Firefox-Release" branch does not exist (see log attached).

I have gone to test-master02 inside of talos-r3 and we had talos jobs being triggered but had the same problem (unknown branch"Firefox-Release").

I believe the fix is only one line. I will attach after this.
Attached patch add Firefox-Release branch (obsolete) — Splinter Review
When I have a chance I will go and check that our talos staging environments are running 0.8.0 and use a sendchange like this:

 buildbot sendchange --master talos-staging-master02.build.mozilla.org:9012 --username sendchange --branch release-mozilla-central-linux-talos --revision 900fdd7fb8b2 http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b3-candidates/build3/linux-i686/en-US/firefox-4.0b3.tar.bz2

I will first need someone to land into graphs-staging a fix for me.
Attachment #463569 - Flags: review?(ccooper)
Attachment #463567 - Attachment description: add Firefox-Release → "Firefox-Release" is not a known branch
Attachment #463569 - Flags: review?(ccooper) → review+
Assignee: nobody → armenzg
Status: NEW → ASSIGNED
Priority: -- → P2
Summary: talos for releases is currently broken → talos for releases and talos-master is currently broken
Priority: P2 → P3
Summary: talos for releases and talos-master is currently broken → graphs does not recognise the "Firefox-Release" branch
Priority: P3 → P2
Depends on: 586733
Alice inserted the branch name and now I can run talos runs for releases for the branch Firefox-Release.

I have asked IT to land it on production for me.
From https://bugzilla.mozilla.org/show_bug.cgi?id=586733#c1 I have added the missing branches.

What shall I do with the missing -Release branches? We have 3.0, 3.5 and 4.0 missing on the DB.
Attachment #463569 - Attachment is obsolete: true
Attachment #465784 - Flags: review?(bhearsum)
(In reply to comment #3)
> Created attachment 465784 [details] [diff] [review]
> sql/data.sql add missing branches
> 
> From https://bugzilla.mozilla.org/show_bug.cgi?id=586733#c1 I have added the
> missing branches.
> 
> What shall I do with the missing -Release branches? We have 3.0, 3.5 and 4.0
> missing on the DB.

May as well add them since you're already touching this file.
OK I will follow up with IT to land them.
Attachment #465805 - Flags: review?(bhearsum)
Depends on: 587141
Attachment #465784 - Attachment is obsolete: true
Attachment #465784 - Flags: review?(bhearsum)
IT has landed the missing release branches.
We are good to match it with this patch.
Attachment #465805 - Flags: review?(bhearsum) → review+
Comment on attachment 465805 [details] [diff] [review]
sql/data.sql add missing branches

http://hg.mozilla.org/graphs/rev/3988dc8f6974
Attachment #465805 - Flags: checked-in+
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: