error.append(f'{repo} repo missing expected results:\n{missing}') if unknown: error.append(f'{repo} repo unknown results:\n{unknown}') > pytest.fail('\n'.join(error)) E Failed: unmatched repo scan results: E eclass repo missing expected results: E eclass ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop-j4_test-20220210-190824 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.3.1 [2] x86_64-pc-linux-gnu-11.2.1 * clang/llvm (if any): /usr/lib/llvm/13 13.0.1 Python 3.9.10 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) [3] ruby30 (with Rubygems) * Available Rust versions: [1] rust-1.58.1 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 11.0.14_p9 [openjdk-bin-11] 2) Eclipse Temurin JDK 8.322_p06 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-11 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 php cli: [1] php7.4 [2] php8.0 * [3] php8.1 HEAD of ::gentoo commit a38ab25484359bd59b73be72bf43670fffd75154 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Tue Feb 15 08:51:59 2022 +0000 2022-02-15 08:51:57 UTC emerge -qpvO dev-util/pkgcheck [ebuild N ] dev-util/pkgcheck-0.10.9 USE="test" PYTHON_TARGETS="python3_9 -python3_8 -python3_10"
Created attachment 765169 [details] emerge-info.txt
Created attachment 765170 [details] dev-util:pkgcheck-0.10.9:20220215-095511.log
Created attachment 765171 [details] emerge-history.txt.bz2
Created attachment 765172 [details] environment
Created attachment 765173 [details] etc.portage.tar.bz2
Created attachment 765174 [details] tests.tar.bz2
I can't reproduce and I have no clue why it could be happening.
appeared recently at the tinderbox image 17.1_systemd-j4_test-20221211-060004
Created attachment 841755 [details] emerge-info.txt
Created attachment 841757 [details] dev-util:pkgcheck-0.10.19:20221212-032507.log
Created attachment 841759 [details] emerge-history.txt
Created attachment 841761 [details] environment
Created attachment 841763 [details] etc.clang.tar.bz2
Created attachment 841765 [details] etc.portage.tar.bz2
The file size of ./files/temp.tar.bz2 is too big (1.4M) for an upload. For about 8 weeks the link http://tinderbox.zwiebeltoralf.de:31560/17.1_systemd-j4_test-20221211-060004/var/tmp/tb/issues/20221212-032743-dev-util_pkgcheck-0.10.19/files/temp.tar.bz2 is valid.
Created attachment 841767 [details] tests.tar.bz2
So what have happened here? environment attached file has function "SwitchGCC" defined and exported. This is cascaded into the testing environment, which is creeped into ebd parsing the bash env of an eclass, and creating an unknown function (undocumented) SwitchGCC. What should we do? As the upstream maintainer, I'm sorry to say I think this is WONTFIX. I will consult other devs if I should just close this bug, and I don't see any way to solve it without breaking other things.
SwitchGCC() is part of the tinderbox script - and exported. Is this a problem in general ?
(In reply to Toralf Förster from comment #18) > SwitchGCC() is part of the tinderbox script - and exported. > > Is this a problem in general ? Yes, any exported function will break pkgcheck at those 2 specific tests.
*** This bug has been marked as a duplicate of bug 836210 ***