motiejus/hermetic_cc_toolchain
1
Fork 0
Code Releases Activity

ci/test: show how bad the artifact situation is

Browse Source
This commit is contained in:
Motiejus Jakštys 2023-02-24 12:41:32 +02:00
parent 4647e8436c
commit 0d0441b9c7
1 changed files with 9 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
ci/test
View File

@ -16,14 +16,13 @@ bazel build "$@" \
# then test everything else with the standard sandbox # then test everything else with the standard sandbox
bazel test "$@" ... bazel test "$@" ...
# TODO: Go 1.20 regressed this. Find a way to re-enable. See README.
# $BAZEL_ZIG_CC_CACHE_PREFIX should be empty for the test below to be valid.
# Ensure that github.com/ziglang/zig/issues/13050 does not regress # Ensure that github.com/ziglang/zig/issues/13050 does not regress
#find "$BAZEL_ZIG_CC_CACHE_PREFIX" -name mutex_destructor.o -execdir file '{}' \; | \ find "$BAZEL_ZIG_CC_CACHE_PREFIX" -name mutex_destructor.o -execdir file '{}' \; | \
# sort | uniq -c | sort -rn > /tmp/got_cache sort | uniq -c | sort -rn > /tmp/got_cache
#
#diff -u ci/testdata/want_cache /tmp/got_cache || { diff -u ci/testdata/want_cache /tmp/got_cache || {
# >&2 echo "ERROR: unexpected artifacts." >&2 echo "ERROR: unexpected artifacts. This is TODO."
# >&2 echo "Was $BAZEL_ZIG_CC_CACHE_PREFIX empty before the test?" # TODO: Go 1.20 regressed this. Find a way to re-enable. See README.
#exit 1 #exit 1
#} exit 0
}