cri-o/contrib/test/integration
Chris Evich 76e25eea42 integration: jUnit output from e2e
Processing node-e2e.log into jUnit format is insane, it's chock-full of
terminal escape codes.  They would either need to be scraped/removed or
disabled somehow.  Instead, take advantage of ``e2e.go --report-dir=``
option.  This will cause it to store native jUnit results in the
specified directory for later collection.  The jUnit results are also
needed for the google test grid.

Signed-off-by: Chris Evich <cevich@redhat.com>
2017-09-28 14:05:25 -04:00
..
build Refactor the CRI-O test playbook to be more modular 2017-09-25 10:02:04 -07:00
callback_plugins integration: Add color + readable logging 2017-09-28 14:05:25 -04:00
ansible.cfg integration: Add color + readable logging 2017-09-28 14:05:25 -04:00
e2e.yml integration: jUnit output from e2e 2017-09-28 14:05:25 -04:00
golang.yml Refactor the CRI-O test playbook to be more modular 2017-09-25 10:02:04 -07:00
main.yml Refactor the CRI-O test playbook to be more modular 2017-09-25 10:02:04 -07:00
system.yml Refactor the CRI-O test playbook to be more modular 2017-09-25 10:02:04 -07:00
test.yml Refactor the CRI-O test playbook to be more modular 2017-09-25 10:02:04 -07:00