Closed
Bug 1044348
Opened 9 years ago
Closed 9 years ago
Cannot cancel all jobs belonging to a particular push from Treeherder
Categories
(Tree Management :: Treeherder, defect, P1)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1052891
People
(Reporter: ehsan.akhgari, Assigned: camd)
References
Details
Attachments
(1 file)
46.28 KB,
image/jpeg
|
Details |
No description provided.
Updated•9 years ago
|
Blocks: treeherder-sheriff-transition
Priority: -- → P1
Assignee | ||
Comment 1•9 years ago
|
||
Assignee | ||
Comment 2•9 years ago
|
||
Is this menu item not working? Or was it just not obvious to find it there? Perhaps that menu/button needs a better icon or positioning.
Status: NEW → ASSIGNED
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → cdawson
Updated•9 years ago
|
Flags: needinfo?(ehsan)
Assignee | ||
Comment 4•9 years ago
|
||
:Ehsan: Can I verify with you what exactly happened when encountered the menu item not working? Did you have jobs in the ``pending`` state that just never disappeared as they should? I have tested this canceling on production and it does cancel jobs. If a job is in the ``running`` state, it'll change to ``usercancel``. But if the job is in ``pending`` state, it just sticks around. bug 1052891 outlines this circumstance. Does that sound like what you're seeing?
Assignee | ||
Updated•9 years ago
|
Flags: needinfo?(ehsan)
Reporter | ||
Comment 5•9 years ago
|
||
(In reply to Cameron Dawson [:camd] from comment #4) > :Ehsan: Can I verify with you what exactly happened when encountered the > menu item not working? Did you have jobs in the ``pending`` state that just > never disappeared as they should? My memory is hazy here (sorry, I should have filed a better bug), but as far as I can remember, the cancel all button didn't do anything at all. There is a slight chance that all of the jobs were in the pending state though, since I have a vague memory that I wanted to cancel everything on the job immediately after I realized that I pushed the wrong patch to try. > I have tested this canceling on production and it does cancel jobs. If a > job is in the ``running`` state, it'll change to ``usercancel``. But if the > job is in ``pending`` state, it just sticks around. > > bug 1052891 outlines this circumstance. Does that sound like what you're > seeing? That bug might have been what I saw... I guess this bug in its current form is not actionable, so I would just dupe this against bug 1052891.
Flags: needinfo?(ehsan)
Assignee | ||
Comment 6•9 years ago
|
||
Ehsan-- Cool, sounds good. Thanks for the info!
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•