It seems if you add new jobs via the "Add new jobs" menu item, the newly-added jobs would run the whole set rather that the limited set of tests specified by the tag. I guess it is sometimes an expected behavior, but sometimes not. Probably the best stage is to allow adding new jobs with any tag specified somehow (via a prompt or?).
These jobs are scheduled via try extender/mozci, so I believe the fix will need to be made there. Armen, when you're back from PTO I don't suppose you could suggest the next steps? :-)
Component: Treeherder → General
Product: Tree Management → Testing
Version: --- → unspecified
I will grab it and look at it this week.
Assignee: nobody → armenzg
I'm sorry this took so long. xidorn, do you remember which jobs you were adding? If a build job was selected or a test job that requires a build that does not exist, it will not respect the try syntax. If we had Builbot bridge scheduling we would be able to control this properly. Right now, for certain cases we have to schedule builds through the Buildapi and that takes away any control we might intend.
Assignee: armenzg → nobody
I think I added some test jobs which did not require additional builds, and some of the jobs might even be a repeat of existing ones from the try syntax directly. But I could be wrong since this was reported two months ago...
OK I will have to close this as incomplete for now. If you hit it again let's try to get that info in and hopefully we can fix it sooner rather than later. My apologies for missing this! I had too many assigned bugs. I should have NIed myself.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.