@biffo/cli 0.176.3 → 0.176.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -73,6 +73,16 @@ LIST=""
|
|
|
73
73
|
FAILED=""
|
|
74
74
|
PASSED=""
|
|
75
75
|
SKIPPED=""
|
|
76
|
+
# Defined up here, not inside run_check. `run_check` returns EARLY in --list
|
|
77
|
+
# mode, before it would set this -- so `pytest_record "$d" "$LAST_CHECK_SECONDS"`
|
|
78
|
+
# read an unset variable and `set -u` killed the script silently, mid-list.
|
|
79
|
+
#
|
|
80
|
+
# The damage was invisible and downstream: gate-coverage.sh reads --list, so a
|
|
81
|
+
# truncated list looked like MISSING COVERAGE. tabsii-geo dropped from 8/8 to
|
|
82
|
+
# 4/8 -- and only in repos where a pytest measurement already existed, i.e. only
|
|
83
|
+
# after the gate had run there once. A defect that appears on second use is the
|
|
84
|
+
# hardest kind to attribute.
|
|
85
|
+
LAST_CHECK_SECONDS=""
|
|
76
86
|
|
|
77
87
|
# pytest is included where the suite is FAST ENOUGH TO PAY, measured rather than
|
|
78
88
|
# opted into (#869, H5 gap 4).
|
|
@@ -284,7 +294,6 @@ run_check() {
|
|
|
284
294
|
return 0
|
|
285
295
|
fi
|
|
286
296
|
start=$(date +%s)
|
|
287
|
-
LAST_CHECK_SECONDS=""
|
|
288
297
|
if "$@" >"/tmp/biffo-verify.$$" 2>&1; then
|
|
289
298
|
PASSED="$PASSED $name"
|
|
290
299
|
LAST_CHECK_SECONDS=$(($(date +%s) - start))
|
|
@@ -73,6 +73,16 @@ LIST=""
|
|
|
73
73
|
FAILED=""
|
|
74
74
|
PASSED=""
|
|
75
75
|
SKIPPED=""
|
|
76
|
+
# Defined up here, not inside run_check. `run_check` returns EARLY in --list
|
|
77
|
+
# mode, before it would set this -- so `pytest_record "$d" "$LAST_CHECK_SECONDS"`
|
|
78
|
+
# read an unset variable and `set -u` killed the script silently, mid-list.
|
|
79
|
+
#
|
|
80
|
+
# The damage was invisible and downstream: gate-coverage.sh reads --list, so a
|
|
81
|
+
# truncated list looked like MISSING COVERAGE. tabsii-geo dropped from 8/8 to
|
|
82
|
+
# 4/8 -- and only in repos where a pytest measurement already existed, i.e. only
|
|
83
|
+
# after the gate had run there once. A defect that appears on second use is the
|
|
84
|
+
# hardest kind to attribute.
|
|
85
|
+
LAST_CHECK_SECONDS=""
|
|
76
86
|
|
|
77
87
|
# pytest is included where the suite is FAST ENOUGH TO PAY, measured rather than
|
|
78
88
|
# opted into (#869, H5 gap 4).
|
|
@@ -284,7 +294,6 @@ run_check() {
|
|
|
284
294
|
return 0
|
|
285
295
|
fi
|
|
286
296
|
start=$(date +%s)
|
|
287
|
-
LAST_CHECK_SECONDS=""
|
|
288
297
|
if "$@" >"/tmp/biffo-verify.$$" 2>&1; then
|
|
289
298
|
PASSED="$PASSED $name"
|
|
290
299
|
LAST_CHECK_SECONDS=$(($(date +%s) - start))
|