Bug 722287 - beah should report the limit reached when recording size_limit results
Summary: beah should report the limit reached when recording size_limit results
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: beah
Version: 0.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: Marian Csontos
QA Contact:
URL:
Whiteboard:
Depends On: 722387
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-14 20:31 UTC by Bill Peck
Modified: 2019-05-22 13:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-28 23:50:13 UTC


Attachments (Terms of Use)

Description Bill Peck 2011-07-14 20:31:25 UTC
Description of problem:

/kernel/power-management/setitimer has reached soft size limit!

when you record the above log record the limit reached. (also
spell out if it was file limit or task limit, etc..) (This is
important since we could have changed the limits in our config file.
Luckily we haven't yet)

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

Comment 1 Marian Csontos 2011-07-15 07:29:39 UTC
I have found a bug in beah_beaker.conf file which prevented file soft limit from taking effect - Bug 722387. Thus all the limits seen so far were tasks reaching soft limit.

When this is fixed it should look like in output of 

  bkr job-results --prettyxml J:111871

Excerpt:

<result id="12132189" path="upload_limit" result="Warn" score="1170.00">
    file://file0 has reached upload limit!
</result>
<result id="12132190" path="size_limit/soft" result="Warn" score="1186.00">
    /distribution/beaker/beah/bz629025-caps has reached soft size limit!
</result>

If that's enough close as duplicate of 722387, please.

Comment 2 Marian Csontos 2011-07-19 12:01:58 UTC
The changes were merged into beah/master and beaker/develop.


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