Remove OOM check from tox role
This is something we did in openstack-infra but not sure it make sense for default tox jobs. It is possible we want to make this an ansible role for playbooks to opt into post-run. But with properly logging on a job, it should be straightforward to determine why a tox test failed. Change-Id: I746fae586a3df40a07ceca9c0bebe579f9f74f34 Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This commit is contained in:
parent
c7037bb2b4
commit
cd6902638f
@ -38,20 +38,6 @@
|
|||||||
fi
|
fi
|
||||||
}
|
}
|
||||||
|
|
||||||
function check_oom {
|
|
||||||
$script_path/jenkins-oom-grep.sh post
|
|
||||||
oomresult=$?
|
|
||||||
|
|
||||||
if [ $oomresult -ne "0" ]; then
|
|
||||||
echo
|
|
||||||
echo "This test has failed because it attempted to exceed configured"
|
|
||||||
echo "memory limits and was killed prior to completion. See above"
|
|
||||||
echo "for related kernel messages."
|
|
||||||
echo
|
|
||||||
exit 1
|
|
||||||
fi
|
|
||||||
}
|
|
||||||
|
|
||||||
function check_nose_html {
|
function check_nose_html {
|
||||||
htmlreport=$(find . -name $NOSE_HTML_OUT_FILE)
|
htmlreport=$(find . -name $NOSE_HTML_OUT_FILE)
|
||||||
if [ -f "$htmlreport" ]; then
|
if [ -f "$htmlreport" ]; then
|
||||||
@ -81,7 +67,6 @@
|
|||||||
result=$?
|
result=$?
|
||||||
|
|
||||||
process_testr_artifacts
|
process_testr_artifacts
|
||||||
check_oom
|
|
||||||
check_nose_html
|
check_nose_html
|
||||||
|
|
||||||
# Rename tox .log files to .log.txt so that Apache serves them as
|
# Rename tox .log files to .log.txt so that Apache serves them as
|
||||||
|
Loading…
x
Reference in New Issue
Block a user