1. 09 5月, 2016 1 次提交
  2. 06 5月, 2016 3 次提交
    • L
      avocado: Avoid custom handling of SIGINT and SIGUSR · d37c23fa
      Lukáš Doktor 提交于
      Currently avocado adds custom handlers of SIGINT and SIGUSR1 in order to
      produce traceback and notify about user interaction or timeout. This
      could be missleading in case the test uses those signals and potentially
      dangerous as some tests assume default behavior.
      
      This patch removes the custom handling of SIGINT and SIGUSR1 and
      reports the failure in `job.log`. Additionally it tries to inject the
      error message in the test output, if status.logfile available.
      
      In order to keep the useful traceback in case of interruption, this
      patch overrides the default SIGTERM handler. The default behavior of
      SIGTERM is to die, our custom handler raises SystemExit with info saying
      the test was interrupted by sigterm, which should generate traceback and
      finish. The runner then changes the result to INTERRUPTED, so even
      when the test modifies the SIGTERM handler, we get the correct status.
      
      Worth mentioning that in case test ignores SIGTERM, SIGKILL is emitted
      by the runner, so this should be safe approach.
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      d37c23fa
    • L
      avocado.core: Get logger just once · 44abeefc
      Lukáš Doktor 提交于
      The `test` and `app` loggers are used many times in
      `avocado.core.runner`. This patch stores them as global variables and
      uses them in the module.
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      44abeefc
    • L
      19189e66
  3. 05 5月, 2016 2 次提交
  4. 04 5月, 2016 7 次提交
  5. 03 5月, 2016 10 次提交
  6. 02 5月, 2016 5 次提交
  7. 30 4月, 2016 1 次提交
  8. 27 4月, 2016 9 次提交
  9. 26 4月, 2016 2 次提交