93% tests passed, 3 tests failed out of 46 Total Test time (real) = 533.85 sec The following tests did not run: 12 - test.fileclone (Skipped) 16 - test.ivfsoverlay (Skipped) 18 - test.modules (Skipped) 19 - test.multi_arch (Skipped) 23 - test.nvcc (Skipped) 24 - test.nvcc_direct (Skipped) 25 - test.nvcc_ldir (Skipped) 26 - test.nvcc_nocpp2 (Skipped) 29 - test.profiling_clang (Skipped) 31 - test.profiling_hip_clang (Skipped) 37 - test.remote_redis (Skipped) 38 - test.remote_redis_unix (Skipped) 40 - test.sanitize_blacklist (Skipped) 41 - test.serialize_diagnostics (Skipped) The following tests FAILED: 3 - test.basedir (Failed) 6 - test.color_diagnostics (Failed) 11 - test.direct (Failed) Errors while running CTest 3/46 Testing: test.basedir 3/46 Test: test.basedir Command: "/bin/bash" "/var/tmp/portage/dev-util/ccache-4.9.1/work/ccache-4.9.1/test/run" "basedir" Directory: /var/tmp/portage/dev-util/ccache-4.9.1/work/ccache-4.9.1_build "test.basedir" start time: Mar 12 02:12 UTC Output: ---------------------------------------------------------- Compiler: hppa2.0-unknown-linux-gnu-gcc (/usr/bin/hppa2.0-unknown-linux-gnu-gcc) Compiler version: hppa2.0-unknown-linux-gnu-gcc (Gentoo 13.2.1_p20240113-r1 p12) 13.2.1 20240113 CUDA compiler: not available Running test suite basedir............... FAILED Test suite: basedir (line 356) Test case: Absolute paths in stderr Failure reason: Expected direct_cache_hit to be 2, actual 1 6/46 Testing: test.color_diagnostics 6/46 Test: test.color_diagnostics Command: "/bin/bash" "/var/tmp/portage/dev-util/ccache-4.9.1/work/ccache-4.9.1/test/run" "color_diagnostics" Directory: /var/tmp/portage/dev-util/ccache-4.9.1/work/ccache-4.9.1_build "test.color_diagnostics" start time: Mar 12 02:14 UTC Output: ---------------------------------------------------------- Compiler: hppa2.0-unknown-linux-gnu-gcc (/usr/bin/hppa2.0-unknown-linux-gnu-gcc) Compiler version: hppa2.0-unknown-linux-gnu-gcc (Gentoo 13.2.1_p20240113-r1 p12) 13.2.1 20240113 CUDA compiler: not available Running test suite color_diagnostics. FAILED Test suite: color_diagnostics (line 42) Test case: Colored diagnostics automatically disabled when stderr is not a TTY (run_second_cpp=true) Failure reason: File test1.output does not contain " Actual content: test1.c:2:2: warning: #warning "Warning from preprocessor" [-Wcpp] 2 | #warning "Warning from preprocessor" | ^~~~~~~ test1.c: In function 'stderr': test1.c:1:58: warning: control reaches end of non-void function [-Wreturn-type] 1 | int stderr(void) { /* Warn about no return statement. */ } | ^ 11/46 Testing: test.direct 11/46 Test: test.direct Command: "/bin/bash" "/var/tmp/portage/dev-util/ccache-4.9.1/work/ccache-4.9.1/test/run" "direct" Directory: /var/tmp/portage/dev-util/ccache-4.9.1/work/ccache-4.9.1_build "test.direct" start time: Mar 12 02:15 UTC Output: ---------------------------------------------------------- Compiler: hppa2.0-unknown-linux-gnu-gcc (/usr/bin/hppa2.0-unknown-linux-gnu-gcc) Compiler version: hppa2.0-unknown-linux-gnu-gcc (Gentoo 13.2.1_p20240113-r1 p12) 13.2.1 20240113 CUDA compiler: not available Running test suite direct............................... FAILED Test suite: direct (line 366) Test case: -Wp,-MD Failure reason: Expected cache_miss to be 1, actual 0 Reproducible: Always
Created attachment 887407 [details] build.log and emerge --info
One of them might be NOCOLOR or similar shenanigans. Not sure about the other.
I don't suppose the 2 non-trivial (docs) commits from https://github.com/ccache/ccache/commits/4.9-maint help?
(In reply to Sam James from comment #3) > I don't suppose the 2 non-trivial (docs) commits from > https://github.com/ccache/ccache/commits/4.9-maint help? Which two commits, sorry?
https://github.com/ccache/ccache/commit/2bf704988762dd1da58a6c01f2b5f91d23bc8e95 https://github.com/ccache/ccache/commit/33d390bb249ddf1a6b3bdecede71b12c70000da3
(In reply to Sam James from comment #5) > https://github.com/ccache/ccache/commit/ > 2bf704988762dd1da58a6c01f2b5f91d23bc8e95 > https://github.com/ccache/ccache/commit/ > 33d390bb249ddf1a6b3bdecede71b12c70000da3 No, no change after applying these two.
I'm pretty sure this used to pass, but the failure makes me feel like it's more of an env specific thing. Can you try bisect but first try some older git tag?
(In reply to Sam James from comment #7) > I'm pretty sure this used to pass, but the failure makes me feel like it's > more of an env specific thing. Can you try bisect but first try some older > git tag? I just tested current stable, 4.8.3, and I still get the same 3 failures. But none of the 3 failures reproduce on any other arch I've tried yet - I've tried amd64, ppc64, ppc so far. Still need to try alpha since it's the only other arch with low-res clock. Debian doesn't seem to see any issues and they don't have any downstream patches.
ok, thanks :|
All tests pass on alpha. Admittedly the clock resolution is not quite as low on alpha as it is on hppa, but it's still much higher than 1ns.
Created attachment 894728 [details] build.log and emerge --info Same with 4.9.1-r1
Created attachment 897378 [details] build.log and emerge --info Same with 4.10.1
