Bug 710524 - [Beaker] cmdline job-watch --nowait not working as expected
Summary: [Beaker] cmdline job-watch --nowait not working as expected
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: command line
Version: 0.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: Bill Peck
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-03 15:37 UTC by Jeff Burke
Modified: 2019-05-22 13:40 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-08 02:43:18 UTC


Attachments (Terms of Use)

Description Jeff Burke 2011-06-03 15:37:14 UTC
Description of problem:
The --nowait option is not working as expected.

This is from a completed job:

$ bkr job-watch J:84399
Watching tasks (this may be safely interrupted)...
J:84399 kernel-2.6.18-260.el5.kpq1 KernelTier1: Completed
--> Completed: 1 [total: 1]
*Returns you to the prompt (as expected)

$ bkr job-watch --nowait J:84399 
*Not sure why it return nothing? shouldn't it return the
same thing as the command without the --nowait

--------------------------------------------------

This is from a job that was running at the time I ran the command

$ bkr job-watch J:92788
Watching tasks (this may be safely interrupted)...
J:92788 ipa sssd testing: Running
--> Running: 1 [total: 1]
*Stays connected (as expected)

$ bkr job-watch --nowait J:92788
*should return the same thing as the command without the --nowait
but give back the prompt

Comment 1 Bill Peck 2011-06-03 17:09:41 UTC
I'm not even sure why we have --nowait for job-watch.  The option doesn't make any sense and will be removed.

Comment 2 Marian Csontos 2011-06-03 18:30:51 UTC
(In reply to comment #1)
> I'm not even sure why we have --nowait for job-watch.  The option doesn't make
> any sense and will be removed.

Backwards compatibility, I guess.

Comment 4 Dan Callaghan 2011-09-08 02:43:18 UTC
Beaker 0.7.1 has been released.


Note You need to log in before you can comment on or make changes to this bug.