* Using python3.7 in global scope * python3_7: running distutils-r1_run_phase python_install_all rm: cannot remove /var/tmp/portage/dev-python/autobahn-20.4.3/image/usr/lib*/python*/site-packages/twisted/plugins//dropin.cache: No such file or directory * ERROR: dev-python/autobahn-20.4.3::gentoo failed (install phase): * (no error message) * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop-abi32+64-20200505-162645 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10.1.0 * clang version 10.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/10/bin /usr/lib/llvm/10 10.0.0 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.6 [3] python3.8 (fallback) [4] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.43.1 * The following VMs are available for generation-2: *) IcedTea JDK 3.15.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.0.2 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Sat 09 May 2020 11:05:34 PM UTC emerge -qpvO dev-python/autobahn [ebuild N ] dev-python/autobahn-20.4.3 USE="crypt -test" PYTHON_TARGETS="python3_7 -python3_6 -python3_8"
Created attachment 637250 [details] emerge-info.txt
Created attachment 637252 [details] dev-python:autobahn-20.4.3:20200509-232659.log
Created attachment 637254 [details] emerge-history.txt
Created attachment 637256 [details] environment
Created attachment 637258 [details] etc.portage.tbz2
Created attachment 637260 [details] temp.tbz2
DOH! the fix somehow didn't make it to the push to the tree. I had found this same error during my initial bumping. The plugin.cache is not re-generated in the build environment when upgrading from older autobahn. When re-installing, it is generated. Instead I had re-directed output to /dev/null so it would ignore a failure to rm the file before install as it may not exist. If it did fail, but did exist, then the install would fail due to a file collision. Pushing the fixed ebuild to the tree. Please re-test to confirm.
Actually I think the plugin.cache is only generated when you enable tests. As it more fully integrates with twisted than it did in previous versions.
(In reply to Brian Dolbec from comment #8) > Actually I think the plugin.cache is only generated when you enable tests. > As it more fully integrates with twisted than it did in previous versions. No, the image does not have FEATURES=test and I really try to double-ensure it for non-test tinderbox images: https://github.com/toralf/tinderbox/blob/master/bin/setup_img.sh#L461
Yes, since you did not enable tests, the plugin.cache was not generated to run the tests. So when it tried to rm the non-existent file, it failed due to the " | die" tacked on to the command. I missed seeing the fix was missing when I pushed the bump to the tree. The ebuild now just re-directs the output to /dev/null for that rm command. So it won't matter if the file existed or not. If it did it would remove it to prevent a file collision with twisted's plugin.cache which is re-generated in postinst.
Seems to be no other reports of this still occurring... closing
