clamav-1.5.0-beta: Make Test fails.

[suishouen]

trafficstars

clamav-1.5.0-beta: Make Test fails.

Build Environments: MacBookPro (Intel) macOS 15.4 (24E248) Darwin Kernel Version 24.4.0 com.apple.pkg.CLTools_Executables version: 16.3.0.0.1.1742442376

Make test ends up as follows:

Running tests... Test project /Users/xxx/Desktop/clamav-1.5.0-beta/build Connected to MAKE jobserver Start 1: libclamav 1/6 Test #1: libclamav ........................ Passed 16.29 sec Start 2: libclamav_rust 2/6 Test #2: libclamav_rust ................... Passed 12.24 sec Start 3: clamscan 3/6 Test #3: clamscan ......................... Passed 0.14 sec Start 4: clamd 4/6 Test #4: clamd ............................ ***Failed 13.10 sec Start 5: freshclam 5/6 Test #5: freshclam ........................ Passed 42.04 sec Start 6: sigtool 6/6 Test #6: sigtool .......................... Passed 0.81 sec

83% tests passed, 1 tests failed out of 6

Total Test time (real) = 84.64 sec

The following tests FAILED: 4 - clamd (Failed) Errors while running CTest

Part of "Output of clamav-1.5.0-beta/build/Testing/Temporary/LastTest.log"

FAIL test_clamd_10_allmatch_not_sticky (clamd_test.TC) Verify that a scanning without allmatch does not use allmatch mode, after scanning with allmatch. ...

FAIL test_clamd_11_alertexceedsmax_maxfilesize (clamd_test.TC) Verify that exceeding maxfilesize with AlertExceedsMax reports an alert and not an error. ...

Although, the latest clamav-main (https://github.com/Cisco-Talos/clamav/tree/00886ee90d07a3b382041b1a9ef0c01e093f571e) running tests succeed as follows;

Running tests... Test project /Users/xxx/Desktop/clamav-main/build Connected to MAKE jobserver Start 1: libclamav 1/6 Test #1: libclamav ........................ Passed 16.44 sec Start 2: libclamav_rust 2/6 Test #2: libclamav_rust ................... Passed 11.79 sec Start 3: clamscan 3/6 Test #3: clamscan ......................... Passed 0.13 sec Start 4: clamd 4/6 Test #4: clamd ............................ Passed 13.98 sec Start 5: freshclam 5/6 Test #5: freshclam ........................ Passed 42.02 sec Start 6: sigtool 6/6 Test #6: sigtool .......................... Passed 0.83 sec

100% tests passed, 0 tests failed out of 6

[val-ms]

Thank you for testing the beta. I haven't seen these two tests fail before. The clamav 1.5.0-beta is presently the same as the latest in clamav main branch. So I am a little confused and it feels like a fluke.

There should be more detailed log files you can inspect, under the build directory's "unit_tests" directory:

./unit_tests/test_clamd_10_allmatch_not_sticky.log
./unit_tests/test_clamd_11_alertexceedsmax_maxfilesize.log

Outside of looking at those log files for some explanation, can you try a second time with the beta to see if it was a fluke?

[rma-x]

I see similar test failures with test_clamd_09_clamdscan_ExcludePath and test_clamd_10_allmatch_not_sticky on openSUSE Tumbleweed x86_64 after dropping the 1.5.0 beta tarball into the 1.4.2 RPM spec file. The failures are reproducible. Will investigate the details tomorrow and report back. Please let me know if you prefer to have this reported as a separate issue.

[val-ms]

@rma-x I think it makes sense to add the details to this ticket. Thank you for reporting and investigating!

[suishouen]

I tested clamav-main and clamav-beta four times. The clavav-main running test succeeded and the clamav-beta running test failed. That is the same.

However, this time the logs were a little different. I hope this helps!

Part of LastTest.log (clamav-1.5.0-beta) is as follows:

Part of LastTest.log
======================================================================
FAIL: test_clamd_09_clamdscan_ExcludePath (clamd_test.TC)
Verify that ExcudePath works and does not cause other  on works as expected.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/xxx/Desktop/clamav-1.5.0-beta/unit_tests/clamd_test.py", line 516, in test_clamd_09_clamdscan_ExcludePath
    self.run_clamdscan('{}'.format(TC.path_tmp),
  File "/Users/xxx/Desktop/clamav-1.5.0-beta/unit_tests/clamd_test.py", line 200, in run_clamdscan
    self.verify_output(output.out, expected=expected_out, unexpected=unexpected_out)
  File "/Users/xxx/Desktop/clamav-1.5.0-beta/unit_tests/testcase.py", line 248, in verify_output
    log_checker.verify_expected_output(expected, text, order=order)
  File "/Users/xxx/Desktop/clamav-1.5.0-beta/unit_tests/testcase.py", line 808, in verify_expected_output
    assert match, "Expected item `%s` not found in output:\n%s" % (
AssertionError: Expected item `a_found: ClamAV-Test-File.UNOFFICIAL FOUND` not found in output:
/Users/xxx/Desktop/clamav-1.5.0-beta/build/unit_tests/TC-utx2ohgo: OK

----------- SCAN SUMMARY -----------
Infected files: 0
Time: 0.000 sec (0 m 0 s)
Start Date: 2025:04:02 07:59:05
End Date:   2025:04:02 07:59:05


======================================================================
FAIL: test_clamd_10_allmatch_not_sticky (clamd_test.TC)
Verify that a scanning without allmatch does not use allmatch mode, after scanning with allmatch.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/xxx/Desktop/clamav-1.5.0-beta/unit_tests/clamd_test.py", line 548, in test_clamd_10_allmatch_not_sticky
    assert output.ec == 1
AssertionError

----------------------------------------------------------------------
Ran 13 tests in 12.971s

FAILED (failures=2)
<end of output>

[rma-x]

I get the same error for test_clamd_09_clamdscan_ExcludePath. For test_clamd_10_allmatch_not_sticky I get:

E       AssertionError: assert 0 == 1
E        +  where 0 = CmdResult(ec=0, out='/[...]/BUILD/clamav-1.5.0-build/clamav-1.5.0-beta/unit_tests/input/pe_allmatch/test.exe: OK\n\n----------- SCAN SUMMARY -----------\nInfected files: 0\nTime: 1.000 sec (0 m 1 s)\nStart Date: 2025:04:02 15:26:42\nEnd Date:   2025:04:02 15:26:43\n', err='ERROR: Could not connect to clamd on LocalSocket clamd-test.socket: No such file or directory\nERROR: Could not connect to clamd on localhost: Connection refused\n').ec

/[...]/BUILD/clamav-1.5.0-build/clamav-1.5.0-beta/unit_tests/clamd_test.py:548: AssertionError
----------------------------- Captured stdout call -----------------------------

[INFO]: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO]:                Testing clamdscan --allmatch is not sticky               
[INFO]: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO]: Starting clamd:   /[...]/BUILD/clamav-1.5.0-build/clamav-1.5.0-beta/build/clamd/clamd --config-file=/[...]/BUILD/clamav-1.5.0-build/clamav-1.5.0-beta/build/unit_tests/TC-4n565g96/clamd-test.conf
[DEBUG]: Run command: /[...]/BUILD/clamav-1.5.0-build/clamav-1.5.0-beta/build/clamdscan/clamdscan -c /[...]/BUILD/clamav-1.5.0-build/clamav-1.5.0-beta/build/unit_tests/TC-4n565g96/clamd-test.conf --wait --ping 10 /[...]/BUILD/clamav-1.5.0-build/clamav-1.5.0-beta/unit_tests/input/pe_allmatch/test.exe 
LibClamAV Warning: Only loading signed bytecode, skipping load of unsigned bytecode!
LibClamAV Warning: Turn on BytecodeUnsigned/--bytecode-unsigned to enable loading of unsigned bytecode

It looks to me like clamd fails to start or takes longer to start than the test expects and hence clamdscan cannot connect to its socket.

[suishouen]

I got sources from the ClamAV GitHub release page and the clamav page. Clamav-clamav-1.5.0-beta.zip and clamav-main.zip contain the same files, just different names. So, I tested with the names swapped and the results are as follows. Is this of any help?

Case 1)
Source: clamav-clamav-1.5.0-beta.zip -> Unzip: clamav-clamav-1.5.0-beta -> Test: FAILURE
Source: clamav-clamav-1.5.0-beta.zip -> Unzip: clamav-clamav-1.5.0-beta -> Rename: clamav-main -> Test: SUCCESS

Case 2)
Source: clamav-main.zip -> Unzip: clamav-main -> SUCCESS
Source: clamav-main.zip -> Unzip: clamav-main -> Rename: clamav-clamav-1.5.0-beta -> FAILURE

[teoberi]

Source GitHub: Source code (tar.gz) -> clamav-1.5.0-beta.tar.gz -> clamav-1.5.0-beta -> Rename: clamav-main -> Test: FAILURE

Test project /home0/tmp/src/clamav-main/build Start 1: libclamav 1/11 Test #1: libclamav ........................ Passed 9.29 sec Start 2: libclamav_valgrind 2/11 Test #2: libclamav_valgrind ............... Passed 87.50 sec Start 3: libclamav_rust 3/11 Test #3: libclamav_rust ................... Passed 15.93 sec Start 4: clamscan 4/11 Test #4: clamscan .........................***Failed 0.14 sec Start 5: clamscan_valgrind 5/11 Test #5: clamscan_valgrind ................***Failed 0.14 sec Start 6: clamd 6/11 Test #6: clamd ............................ Passed 23.04 sec Start 7: clamd_valgrind 7/11 Test #7: clamd_valgrind ...................***Failed 60.43 sec Start 8: freshclam 8/11 Test #8: freshclam ........................ Passed 40.77 sec Start 9: freshclam_valgrind 9/11 Test #9: freshclam_valgrind ...............***Failed 21.07 sec Start 10: sigtool 10/11 Test #10: sigtool .......................... Passed 0.38 sec Start 11: sigtool_valgrind 11/11 Test #11: sigtool_valgrind ................. Passed 13.91 sec

64% tests passed, 4 tests failed out of 11

Total Test time (real) = 272.62 sec

The following tests FAILED: 4 - clamscan (Failed) 5 - clamscan_valgrind (Failed) 7 - clamd_valgrind (Failed) 9 - freshclam_valgrind (Failed)

[suishouen]

@rma-x

Thanks for your supplementary exam. I tested Clamav-clamav-1.5.0-beta.zip (https://github.com/Cisco-Talos/clamav/archive/refs/tags/clamav-1.5.0-beta.zip) and clamav-main.zip (https://github.com/Cisco-Talos/clamav/archive/refs/heads/main.zip).

Clamav-1.5.0-beta.tar.gz (https://github.com/Cisco-Talos/clamav/releases/download/clamav-1.5.0-beta/clamav-1.5.0-beta.tar.gz) and clamav-main.zip (https://github.com/Cisco-Talos/clamav/archive/refs/heads/main.zip) don't contain the same files, I think.

[suishouen]

@rma-x For your reference: ClamAV 1.5.0 beta now available! (https://blog.clamav.net/2025/03/clamav-150-beta-now-available.html) writes: Tip: If you are downloading the source from the GitHub release page, the package labeled "clamav-1.5.0-beta.tar.gz" does not require an internet connection to build. All dependencies are included in this package. However, if you download the ZIP or TAR.GZ generated by GitHub, located at the very bottom, then an internet connection will be required during the build to download additional Rust dependencies.

Clamav-1.5.0-beta.tar.gz: File Size -> 63.8MB clamav-clamav-1.5.0-beta.tar.gz: File Size -> 13.9MB clamav-clamav-1.5.0-beta.zip: File Size -> 14.6MB clamav-main.zip: File Size -> 14.6MB

[rma-x]

Thanks, @suishouen. I am aware of the release announcement and intentionally took the "batteries included" tarball, because packages for openSUSE are not allowed to download stuff from the internet at RPM build time. All their build dependencies have to be contained in their source files or be imported from other RPMs. At some point I might have a try to satisfy the Rust dependencies from existing RPMs, so that I can take the smaller and quicker building source archive, but my guess is that this would take me directly into version dependency hell.

[Kangie]

I am seeing this failure in 1.5.0-beta for Gentoo, we use the GitHub release as our source and fetch any required crates and git crates.

self = <clamd_test.TC testMethod=test_clamd_10_allmatch_not_sticky>

    def test_clamd_10_allmatch_not_sticky(self):
        '''
        Verify that a scanning without allmatch does not use allmatch mode, after scanning with allmatch.
        This is a regression test for an issue where the allmatch scan option is sticky and any scans after an allmatch scan become an allmatch scan.
        '''
        self.step_name('Testing clamdscan --allmatch is not sticky')
    
        # Get a list of Path()'s of each of signature file
        test_path = TC.path_source / 'unit_tests' / 'input' / 'pe_allmatch'
        database_files = list(test_path.glob('alert-sigs/*'))
    
        test_exe = test_path / 'test.exe'
    
        # Copy them to the database directory before starting ClamD
        for db in database_files:
            shutil.copy(str(db), str(TC.path_db))
    
        #
        # Start ClamD
        #
        self.start_clamd()
    
        poll = self.proc.poll()
        assert poll == None  # subprocess is alive if poll() returns None
    
        # Try first without --allmatch
        output = self.execute_command('{clamdscan} -c {clamd_config} --wait --ping 10 {test_exe}'.format(
            clamdscan=TC.clamdscan, clamd_config=TC.clamd_config, test_exe=test_exe))
>       assert output.ec == 1
E       AssertionError: assert 0 == 1
E        +  where 0 = CmdResult(ec=0, out='/var/tmp/portage/app-antivirus/clamav-1.5.0_beta/work/clamav-clamav-1.5.0-beta/unit_tests/input/pe_allmatch/test.exe: OK\n\n----------- SCAN SUMMARY -----------\nInfected files: 0\nTime: 0.000 sec (0 m 0 s)\nStart Date: 2025:05:17 10:44:10\nEnd Date:   2025:05:17 10:44:10\n', err='').ec

/var/tmp/portage/app-antivirus/clamav-1.5.0_beta/work/clamav-clamav-1.5.0-beta/unit_tests/clamd_test.py:548: AssertionError
--------------------------------------------------------------------------- Captured stdout call ---------------------------------------------------------------------------

[INFO]: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO]:                Testing clamdscan --allmatch is not sticky               
[INFO]: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO]: Starting clamd:   /var/tmp/portage/app-antivirus/clamav-1.5.0_beta/work/clamav-clamav-1.5.0-beta_build/clamd/clamd --config-file=/var/tmp/portage/app-antivirus/clamav-1.5.0_beta/work/clamav-clamav-1.5.0-beta_build/unit_tests/TC-60qfncln/clamd-test.conf
[DEBUG]: Run command: /var/tmp/portage/app-antivirus/clamav-1.5.0_beta/work/clamav-clamav-1.5.0-beta_build/clamdscan/clamdscan -c /var/tmp/portage/app-antivirus/clamav-1.5.0_beta/work/clamav-clamav-1.5.0-beta_build/unit_tests/TC-60qfncln/clamd-test.conf --wait --ping 10 /var/tmp/portage/app-antivirus/clamav-1.5.0_beta/work/clamav-clamav-1.5.0-beta/unit_tests/input/pe_allmatch/test.exe 
LibClamAV Warning: Only loading signed bytecode, skipping load of unsigned bytecode!
LibClamAV Warning: Turn on BytecodeUnsigned/--bytecode-unsigned to enable loading of unsigned bytecode
LibClamAV Warning: Only loading signed bytecode, skipping load of unsigned bytecode!
LibClamAV Warning: Turn on BytecodeUnsigned/--bytecode-unsigned to enable loading of unsigned bytecode
LibClamAV Warning: Only loading signed bytecode, skipping load of unsigned bytecode!
LibClamAV Warning: Turn on BytecodeUnsigned/--bytecode-unsigned to enable loading of unsigned bytecode
LibClamAV Warning: Only loading signed bytecode, skipping load of unsigned bytecode!
LibClamAV Warning: Turn on BytecodeUnsigned/--bytecode-unsigned to enable loading of unsigned bytecode
LibClamAV Warning: Only loading signed bytecode, skipping load of unsigned bytecode!
LibClamAV Warning: Turn on BytecodeUnsigned/--bytecode-unsigned to enable loading of unsigned bytecode
LibClamAV Warning: Only loading signed bytecode, skipping load of unsigned bytecode!
LibClamAV Warning: Turn on BytecodeUnsigned/--bytecode-unsigned to enable loading of unsigned bytecode
Sat May 17 10:44:10 2025 -> Limits: Global time limit set to 120000 milliseconds.
Sat May 17 10:44:10 2025 -> Limits: Global size limit set to 419430400 bytes.
Sat May 17 10:44:10 2025 -> Limits: File size limit set to 104857600 bytes.
Sat May 17 10:44:10 2025 -> Limits: Recursion level limit set to 17.
Sat May 17 10:44:10 2025 -> Limits: Files limit set to 10000.
Sat May 17 10:44:10 2025 -> Limits: Core-dump limit is 18446744073709551615.
Sat May 17 10:44:10 2025 -> Limits: MaxEmbeddedPE limit set to 41943040 bytes.
Sat May 17 10:44:10 2025 -> Limits: MaxHTMLNormalize limit set to 41943040 bytes.
Sat May 17 10:44:10 2025 -> Limits: MaxHTMLNoTags limit set to 8388608 bytes.
Sat May 17 10:44:10 2025 -> Limits: MaxScriptNormalize limit set to 20971520 bytes.
Sat May 17 10:44:10 2025 -> Limits: MaxZipTypeRcg limit set to 1048576 bytes.
Sat May 17 10:44:10 2025 -> Limits: MaxPartitions limit set to 50.
Sat May 17 10:44:10 2025 -> Limits: MaxIconsPE limit set to 100.
Sat May 17 10:44:10 2025 -> Limits: MaxRecHWP3 limit set to 16.
Sat May 17 10:44:10 2025 -> Limits: PCREMatchLimit limit set to 100000.
Sat May 17 10:44:10 2025 -> Limits: PCRERecMatchLimit limit set to 2000.
Sat May 17 10:44:10 2025 -> Limits: PCREMaxFileSize limit set to 104857600.
Sat May 17 10:44:10 2025 -> Archive support enabled.
Sat May 17 10:44:10 2025 -> Image (graphics) scanning support enabled.
Sat May 17 10:44:10 2025 -> Detection using image fuzzy hash enabled.
Sat May 17 10:44:10 2025 -> AlertExceedsMax heuristic detection disabled.
Sat May 17 10:44:10 2025 -> Heuristic alerts enabled.
Sat May 17 10:44:10 2025 -> Portable Executable support enabled.
Sat May 17 10:44:10 2025 -> ELF support enabled.
Sat May 17 10:44:10 2025 -> Mail files support enabled.
Sat May 17 10:44:10 2025 -> OLE2 support enabled.
Sat May 17 10:44:10 2025 -> PDF support enabled.
Sat May 17 10:44:10 2025 -> SWF support enabled.
Sat May 17 10:44:10 2025 -> HTML support enabled.
Sat May 17 10:44:10 2025 -> XMLDOCS support enabled.
Sat May 17 10:44:10 2025 -> HWP3 support enabled.
Sat May 17 10:44:10 2025 -> OneNote support enabled.
Sat May 17 10:44:10 2025 -> Heuristic: precedence enabled
Sat May 17 10:44:10 2025 -> Self checking every 600 seconds.
Sat May 17 10:44:10 2025 -> Listening daemon: PID: 684
Sat May 17 10:44:10 2025 -> MaxQueue set to: 800
[DEBUG]: Exit code: 0
[DEBUG]: stdout: /var/tmp/portage/app-antivirus/clamav-1.5.0_beta/work/clamav-clamav-1.5.0-beta/unit_tests/input/pe_allmatch/test.exe: OK

----------- SCAN SUMMARY -----------
Infected files: 0
Time: 0.000 sec (0 m 0 s)
Start Date: 2025:05:17 10:44:10
End Date:   2025:05:17 10:44:10


Sat May 17 10:44:10 2025 -> Waiting for all threads to finish
Sat May 17 10:44:10 2025 -> Shutting down the main sockets.
Sat May 17 10:44:10 2025 -> Pid file removed.
Sat May 17 10:44:10 2025 -> --- Stopped at Sat May 17 10:44:10 2025
Sat May 17 10:44:10 2025 -> Closing the main sockets.
Sat May 17 10:44:10 2025 -> Socket file removed.
========================================================================= short test summary info ==========================================================================
FAILED clamd_test.py::TC::test_clamd_09_clamdscan_ExcludePath - AssertionError: Expected item `a_found: ClamAV-Test-File.UNOFFICIAL FOUND` not found in output:
FAILED clamd_test.py::TC::test_clamd_10_allmatch_not_sticky - AssertionError: assert 0 == 1
====================================================================== 2 failed, 11 passed in 13.56s =======================================================================

Is it this? LibClamAV Warning: Turn on BytecodeUnsigned/--bytecode-unsigned to enable loading of unsigned bytecode

[val-ms]

@Kangie I don't think so. The warnings about --bytecode-unsigned are because the alert-sigs directory includes some unsigned bytecode signatures (*.cbc) plus a bunch of other signatures. That allmatch_not_sticky test only cares if the match count is 1 or greater than 1. It the bytecode signatures aren't necessary there, so skipping those should still pass the test.

I was able to reproduce the issue using the zip or tar.gz from github. I couldn't reproduce the issue using a git clone that was checked out to the 1.5.0-beta tag. The only difference between the repo at that commit and the unzipped github source for the beta is:

❯ diff -bur ./clamav-repo/ ./clamav-clamav-1.5.0-beta/
Only in ./clamav-repo/: .git
Only in ./clamav-repo/: .gitattributes
Only in ./clamav-repo/: .gitignore
Only in ./clamav-repo/libclammspack/doc: .gitignore
Only in ./clamav-repo/libclammspack/examples: .gitignore
Only in ./clamav-repo/libclammspack/mspack: .gitignore
Only in ./clamav-repo/libclammspack/test: .gitignore

(repo left, unzipped clamav-1.5.0-beta.zip right)

I am absolutely stumped. I tried downloading the latest clamav-main.zip from github (their generated zip of the stuff in the main branch). I.e. from:

Compiling from clamav-main.zip did not fail the clamd tests. 🤷‍♀

[arjendekorte]

Thanks, @suishouen. I am aware of the release announcement and intentionally took the "batteries included" tarball, because packages for openSUSE are not allowed to download stuff from the internet at RPM build time. All their build dependencies have to be contained in their source files or be imported from other RPMs. At some point I might have a try to satisfy the Rust dependencies from existing RPMs, so that I can take the smaller and quicker building source archive, but my guess is that this would take me directly into version dependency hell.

Also remember that on the openSUSE Build Service, it is not allowed during %check to write to the source directory. This means that you'll need to set TMP to a different place where there is write access:

diff -purN a/unit_tests/CMakeLists.txt b/unit_tests/CMakeLists.txt
--- a/unit_tests/CMakeLists.txt 2025-06-11 21:00:48.607962528 +0200
+++ b/unit_tests/CMakeLists.txt 2025-06-11 21:01:23.641587015 +0200
@@ -259,7 +259,7 @@ endif()
 
 set(ENVIRONMENT
     PYTHONTRACEMALLOC=1 VERSION=${PROJECT_VERSION}${VERSION_SUFFIX}
-    SOURCE=${SOURCE} BUILD=${BUILD} TMP=${TMP}
+    SOURCE=${SOURCE} BUILD=${BUILD} TMP=/tmp
     CK_FORK=no
     CK_DEFAULT_TIMEOUT=300
     LD_LIBRARY_PATH=${LD_LIBRARY_PATH}

I have not found a solution to the test_clamd_10_allmatch_not_sticky failing, other than bluntly skipping it.

[suishouen]

Clamav-1.5.0-rc has been released for testing. This time 100% tests passed, 0 tests failed out of 6.

This bug is out of date, please close this.

Build Environments: MacBookPro (Intel) macOS 15.6.1 (24G90) Darwin Kernel Version 24.6.0 com.apple.pkg.CLTools_Executables version: 16.4.0.0.1.1747106510

[teoberi]

You are the author, who is stopping you from pressing "Close issue"?

[suishouen]

Thanks teoberi. I close this bug.