1. 29 11月, 2017 5 次提交
  2. 27 11月, 2017 2 次提交
  3. 24 11月, 2017 4 次提交
  4. 23 11月, 2017 2 次提交
    • D
      resultsdb: Control note's size limit · ae373b15
      Dmitry Monakhov 提交于
      Currently test's note contains full job.state['fail_reason'].
      And it can be huge unreadable single line  backtrace which
      looks ugly in resultsdb_frontend. In my case it populate whole
      webpage. IMHO front end note should be small, if someone want to
      investigate failure reason we should goto logs link.
      
      This patch add config option which allow to limit note's size,
      which is limited by default to preserve original behaviour.
      
      Also map job.INTERRUPTED state to resultsdb.INFO because when human
      manually interrupts test he probably knows the reason, so test should
      not being treated as NEEDS_INSPECTION.
      Signed-off-by: NDmitry Monakhov <dmonakhov@openvz.org>
      ae373b15
    • D
      contrib: add run inplace helper. · 3715d8b0
      Dmitry Monakhov 提交于
      Avocado is amazing tool for journal everyday routines. But it is very
      script oriented, so if one want to quick run simple command under avocado
      script should be created first, which is not too handy.
      
      Let's add trivial wrapper which transparently do it for us
      #Example: 
      $ avocado-run-inplace.sh yum update -y
      JOB ID     : 26b320e99a8413f1fe73d23afaae746d8436bf8e
      JOB LOG    : /root/avocado/job-results/job-2017-11-22T12.06-26b320e/job.log
       (1/1) yum_update_-y.sh: PASS (47.48 s)
      RESULTS    : PASS 1 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0
      JOB TIME   : 51.52 s
      Signed-off-by: NDmitry Monakhov <dmonakhov@openvz.org>
      3715d8b0
  5. 22 11月, 2017 1 次提交
  6. 21 11月, 2017 5 次提交
  7. 20 11月, 2017 3 次提交
  8. 19 11月, 2017 12 次提交
  9. 18 11月, 2017 6 次提交