1354044 - Reset group names for nss(-try)

Status: RESOLVED FIXED

(Tree Management :: Treeherder, enhancement)

Description

[Tim Taubert [:ttaubert] (inactive)]

Cameron, can you please reset the cached group names for the nss and nss-try repository again? We changed the task definitions after screwing up the first time and it doesn't pick up the new group names and assignments :( Thanks!

Comment 1

[Cameron Dawson [:camd]]

Tim: I'd be happy to.  Unfortunately, it's more specific than just resetting a cache.  It's specific to which jobs and which groups they SHOULD belong to.  

Can you give me a list of job symbols and names that are in the wrong groups and the right groups for them?  Then I can go in and fix them.

Thanks.  :)

Comment 2

[Tim Taubert [:ttaubert] (inactive)]

Hey Cameron, here's a link to our project on Treeherder: https://treeherder.mozilla.org/#/jobs?repo=nss (and nss-try)

We have a "Linux64 fuzz" row, that contains the following jobs:

add, addmod, div, expmod, mod, mulmod, sqr, sqrmod, sub, submod

All of them should be in the "MPI" group. invmod is the only job that made it there.

Thanks!


Oh, btw, if we have two jobs named "Foo" and one of them is in a group, one is not, should that work?

Comment 3

[Cameron Dawson [:camd]]

Hey Tim--  Ok, these should be all fixed up on Stage and Production.  Please let me know if I missed any.  

I noticed there were some jobs with, for instance, symbol of "add" with one entry of "MPI (add)" and another of "MPI (${mpi_name})".  I'm figuring the second one was probably a mistake where templating didn't work or something, and you don't care about it.  I fixed only the first and left the second (juuuust in case it belonged to someone else who DID care about it).  Please let me know if I got that wrong.  If the second one isn't used in a couple months, it'll be garbage collected anyway.

Yeah, you can have different jobs with the same symbol as long as the "name" field is different in some way.  So if you wanted one to be in a group and one NOT in that group, just make the "name" field slightly different somehow and you should be good.

I gotta get around to fixing this stupid bug some time... We have a better back-end now which would make this easier.  :)

Comment 4

[Tim Taubert [:ttaubert] (inactive)]

(In reply to Cameron Dawson [:camd] from comment #3)
> Hey Tim--  Ok, these should be all fixed up on Stage and Production.  Please
> let me know if I missed any.  

Thanks!

> I noticed there were some jobs with, for instance, symbol of "add" with one
> entry of "MPI (add)" and another of "MPI (${mpi_name})".  I'm figuring the
> second one was probably a mistake where templating didn't work or something,
> and you don't care about it.  I fixed only the first and left the second
> (juuuust in case it belonged to someone else who DID care about it).  Please
> let me know if I got that wrong.  If the second one isn't used in a couple
> months, it'll be garbage collected anyway.

The $mpi_name was just us screwing up job descriptions :) We'll just let it be GC'ed.

> Yeah, you can have different jobs with the same symbol as long as the "name"
> field is different in some way.  So if you wanted one to be in a group and
> one NOT in that group, just make the "name" field slightly different somehow
> and you should be good.

Okay, that's what I thought. Thanks!