Bug 1035793 - tuna throwing valueerror when not specified priority
Summary: tuna throwing valueerror when not specified priority
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: realtime-utilities
Version: 2.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: John Kacur
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks: 1035794 1035795 1035796
TreeView+ depends on / blocked
 
Reported: 2013-11-28 13:44 UTC by Jiri Kastner
Modified: 2015-05-07 13:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1035794 1035795 1035796 (view as bug list)
Environment:
Last Closed: 2015-05-07 13:22:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jiri Kastner 2013-11-28 13:44:23 UTC
Description of problem:
when after scheduler is not specified priority 'tuna -t $PID -p OTHER' (it doesn't matter if RR or FIFO or OTHER), tuna ends with traceback.

Version-Release number of selected component (if applicable):
every

How reproducible:
alway

Steps to Reproduce:
1. install tuna
2. run tuna -t PID_OF_SOME_PROCESS -p OTHER
3. check output

Actual results:

[root@localhost ~]# tuna -t 3199 -p OTHER
Traceback (most recent call last):
  File "/usr/bin/tuna", line 598, in <module>
    main()
  File "/usr/bin/tuna", line 482, in main
    tuna.threads_set_priority(thread_list, a, affect_children)
  File "/usr/lib/python2.6/site-packages/tuna/tuna.py", line 479, in threads_set_priority
    rtprio = int(parms[0])
ValueError: invalid literal for int() with base 10: 'OTHER'


Expected results:
instead of traceback some warning and/or used some default value.

Additional info:

Comment 1 Jiri Kastner 2014-03-12 14:37:17 UTC
commit 443234bd24c794068a752d567bb7f4d903fbbaac in upstream fixed that.


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