Submit repo task IDs

[Aleksey Shipilev]

On 1/9/19 4:32 PM, Severin Gehwolf wrote:
> On Wed, 2019-01-09 at 15:29 +0100, Aleksey Shipilev wrote:
>> Hi,
>>
>> Current submit repo job IDs are rather confusing. For example, for a
>> given branch, I have got five IDs:
>>
>> [Mach5] mach5-one-shade-JDK-8215724-20190108-1643-17048: PASSED
>> [Mach5] mach5-one-shade-JDK-8215724-20190108-2239-17125: PASSED
>> [Mach5] mach5-one-shade-JDK-8215724-20190109-0216-17166: PASSED
>> [Mach5] mach5-one-shade-JDK-8215724-20190109-0913-17241: PASSED
>> [Mach5] mach5-one-shade-JDK-8215724-20190109-1210-17278: PASSED
> 
> Not sure if that's related, but I've been getting nofications of
> branches/bugs which no longer exist post-submit-repo-reset. The way to
> stop them was closing the branch, but that's no longer possible after
> the reset :-/

Not sure.

Another relevant complaint: over the weekend, I have got 33 (!) PASSED notifications for the jobs
that were submitted and completed last week. This really drops the signal-to-noise ratio from
jdk-submit. At least put the mercurial ID into them, or even better provide the cause for the
triggering!

-Aleksey