Bug 1035794 - 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 Linux 7
Classification: Red Hat
Component: tuna
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: John Kacur
QA Contact: Jiri Kastner
URL:
Whiteboard:
Depends On: 1035793 1035796
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-28 13:46 UTC by Jiri Kastner
Modified: 2014-06-13 11:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1035793
Environment:
Last Closed: 2014-06-13 11:24:21 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jiri Kastner 2013-11-28 13:46:00 UTC
+++ This bug was initially created as a clone of Bug #1035793 +++

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 2 John Kacur 2014-03-12 12:41:41 UTC
No upstream solution yet.

Comment 4 John Kacur 2014-03-12 14:36:17 UTC
Upstream fix is  443234bd24c794068a752d567bb7f4d903fbbaac

Comment 10 Ludek Smid 2014-06-13 11:24:21 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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