1263316 - Update Verify jobs on mozilla-beta are reporting as '?'s in Treeherder

Status: RESOLVED FIXED

(Tree Management :: Treeherder: Data Ingestion, defect, P2)

Description

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

+++ This bug was initially created as a clone of Bug #1263315 +++

See https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta&revision=b007110e90053e58946b59765605bfca766c30d1&selectedJob=985647&filter-searchStr=%3F


Some of those are the l10n repacks which should be fixed when Treeherder gets a prod push to pick up the patch in bug 1212177, and a bunch more are partner repack jobs that will be fixed in bug 1263315, but a bunch of '?'s will be left still because update verify jobs need a similar patch.

Comment 1

[Ed Morley [:emorley]]

Please could you let me know:
* the specific buildernames
* what group the jobs should be in (and if a new group, what symbol)
* what job name & symbol should be used

Many thanks :-)

Comment 2

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

Buildernames:
release-mozilla-beta_firefox_macosx64_update_verify
release-mozilla-beta_firefox_win32_update_verify
release-mozilla-beta_firefox_win64_update_verify

There's also a `release-mozilla-beta-firefox_updates`, but I don't know if that's grouped in with the rest.

They could go in a new "Updates" group, with a symbol of "Up".

Job name could be "Update Verify" with a symbol of "Uv"?


(Not particularly sold on any of those names/symbols, but I don't think anyone really cares what they end up being...

Comment 3

[Ed Morley [:emorley]]

(In reply to Wes Kocher (:KWierso) from comment #2)
> Buildernames:
> release-mozilla-beta_firefox_macosx64_update_verify
> release-mozilla-beta_firefox_win32_update_verify
> release-mozilla-beta_firefox_win64_update_verify
> 
> There's also a `release-mozilla-beta-firefox_updates`, but I don't know if
> that's grouped in with the rest.

Rail, should firefox_updates be grouped with the others? Also any thoughts on the naming in comment 2?

Many thanks :-)

Comment 4

[Rail Aliiev [:rail]]

I don't mind to keep them in the same group. Thank for addressing this BTW. :)

Comment 5

[Ed Morley [:emorley]]

(In reply to Wes Kocher (:KWierso) from comment #2)
> There's also a `release-mozilla-beta-firefox_updates`, but I don't know if
> that's grouped in with the rest.

That's currently showing up under one of the auto-detected platform names, since it doesn't have a recognisable platform, eg:
https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta&revision=b007110e90053e58946b59765605bfca766c30d1&filter-searchStr=-firefox_updates

I'm not quite sure what that job is supposed to be - could you file a new bug for it?

Comment 6

[GitHub Autolander Bot]

Attachment: [treeherder] mozilla:support-update-verify > mozilla:master

Comment 7

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

Comment on attachment 8749123 [details] [review]
[treeherder] mozilla:support-update-verify > mozilla:master

Lets do it.
Ni to myself to file that other bug.

Comment 8

[Treeherder GitHub Bugbot]

Commit pushed to master at https://github.com/mozilla/treeherder

https://github.com/mozilla/treeherder/commit/8a101d2cafbde4ddd8bed582f4d696b0f2272eda
Bug 1263316 - Support update-verify jobs