correct the pass/fail metric for python 34

This commit is contained in:
Casey Faist
2019-10-24 12:48:04 -07:00
parent f90dfbc12e
commit f1b0f8c154
2 changed files with 17 additions and 8 deletions
+1 -1
View File
@@ -1 +1 @@
python-3.4.9
python-3.4.10
+16 -7
View File
@@ -38,14 +38,18 @@ testPython2_fail() {
}
testPython3_4() {
updateVersion "python3_4" $LATEST_34
compile "python3_4"
assertCaptured $LATEST_34
assertNotCaptured "security update"
if [[ $STACK == "cedar-14" ]] || [[ $STACK == "heroku-16" ]]; then
assertCapturedSuccess
# if cedar 14 and legacy binaries, fail. if cedar 14 and staging, succeed.
if [[ ! -n $USE_STAGING_BINARIES ]] && [[ $STACK == "cedar-14" ]]; then
assertCapturedError
# if heroku 18 and legacy binaries, succeed. if heroku 18 and staging, fail.
elif [[ -n $USE_STAGING_BINARIES ]] && [[ $STACK == "heroku-18" ]]; then
assertCapturedError
else
assertCapturedError
# all else succeed
assertCapturedSuccess
fi
}
@@ -53,10 +57,15 @@ testPython3_4_warn() {
compile "python3_4_warn"
assertCaptured "python-3.4.9"
assertCaptured "security update!"
if [[ $STACK == "cedar-14" ]] || [[ $STACK == "heroku-16" ]]; then
assertCapturedSuccess
# if cedar 14 and legacy binaries, fail. if cedar 14 and staging, succeed.
if [[ ! -n $USE_STAGING_BINARIES ]] && [[ $STACK == "cedar-14" ]]; then
assertCapturedError
# if heroku 18 and legacy binaries, succeed. if heroku 18 and staging, fail.
elif [[ -n $USE_STAGING_BINARIES ]] && [[ $STACK == "heroku-18" ]]; then
assertCapturedError
else
assertCapturedError
# all else succeed
assertCapturedSuccess
fi
}