Flame and FlameKK builds are not visible on treeherder

RESOLVED FIXED

Status

RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: onelson, Assigned: wcosta)

Tracking

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Reporter)

Description

3 years ago
I noticed today that we lost Flame and FlameKK build visibility on treeherder across all repositories. These were utilized by our testing team to gather information about which mercurial/gecko changesets were included with each build spun to aid in bug verifications.

* https://treeherder.mozilla.org/#/jobs?repo=mozilla-central
* https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound

I was told this could be a TaskCluster issue where our builds are not being seen, or brought over from where they are hosted. I have limited knowledge on this side of builds however. Any help would be appreciated.
(Reporter)

Updated

3 years ago
Flags: needinfo?(nhirata.bugzilla)
Wander, fyi.  Not sure if this is in your territory.  If it's not can you redirect it to the appropriate person please?
Flags: needinfo?(nhirata.bugzilla) → needinfo?(wcosta)
(Assignee)

Comment 2

3 years ago
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #1)
> Wander, fyi.  Not sure if this is in your territory.  If it's not can you
> redirect it to the appropriate person please?

:garndt, we had a discussion on this few days ago, I can't remember the conclusion...
Flags: needinfo?(wcosta) → needinfo?(garndt)

Comment 3

3 years ago
So looking at our task definitions for the branches it doesn't appear that we had device builds appear on production treeherder and those might have been buildbot builds?  I know Wander was doing something recently to get some of them to show up on TH, but those shouldn't have been the same ones you've been historically relying on.  Wander can correct me if I'm wrong.

I took a look this morning and I see device image builds on treeherder from buildbot.

:wcosta can we confirm what image builds need to appear on TH and where they should appear (prod/staging).  If they appear at the same time on production, we probably need to have a different group symbol like we did before when we had buildbot and TC related things side-by-side.
Flags: needinfo?(garndt)
(Assignee)

Comment 5

3 years ago
Created attachment 8608797 [details]
MozReview Request: bz://1166945/wcosta

/r/9189 - Bug 1166945: Add flame to treeherder. r=garndt

Pull down this commit:

hg pull -r ad03b56cb02abebae97fb747d747596b0fb9f9bd https://reviewboard-hg.mozilla.org/gecko/
Attachment #8608797 - Flags: review?(garndt)

Comment 6

3 years ago
Comment on attachment 8608797 [details]
MozReview Request: bz://1166945/wcosta

https://reviewboard.mozilla.org/r/9187/#review7841

::: testing/taskcluster/tasks/builds/b2g_flame_kk_nightly_base.yml:22
(Diff revision 1)
> +      - production

So right now buildbot also displays on TH, is the intention that we are displaying both buildbot and TC on prod at the same time?  If so, what is the plan for migrating away from buildbot?

if so we probably want to change groupsymbol to be 'tc-Flame-kk' or something to distinguish it from buildbot.  Also, these are "nightly" builds so does that need some other kind of distinction on TH instead of our normal build symbol "B"?
Attachment #8608797 - Flags: review?(garndt)
(Assignee)

Comment 7

3 years ago
https://reviewboard.mozilla.org/r/9187/#review7843

> So right now buildbot also displays on TH, is the intention that we are displaying both buildbot and TC on prod at the same time?  If so, what is the plan for migrating away from buildbot?
> 
> if so we probably want to change groupsymbol to be 'tc-Flame-kk' or something to distinguish it from buildbot.  Also, these are "nightly" builds so does that need some other kind of distinction on TH instead of our normal build symbol "B"?

I think we should disable buildbot as soon as this lands. I can talk to #releng.
(Assignee)

Updated

3 years ago
Assignee: nobody → wcosta
Status: NEW → ASSIGNED
(Assignee)

Comment 8

3 years ago
This was fixed in bug 1166745.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
(Assignee)

Comment 9

3 years ago
Comment on attachment 8608797 [details]
MozReview Request: bz://1166945/wcosta
Attachment #8608797 - Attachment is obsolete: true
(Assignee)

Comment 10

3 years ago
Created attachment 8620342 [details]
MozReview Request: Bug 1166945: Add flame to treeherder. r=garndt
Component: TaskCluster → General
Product: Testing → Taskcluster
Target Milestone: --- → mozilla41
Version: unspecified → Trunk
Resetting Version and Target Milestone that accidentally got changed...
Target Milestone: mozilla41 → ---
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.