https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: app-admin/ansible-molecule-3.3.4 fails tests. Discovered on: amd64 (internal ref: ci) NOTE: This machine uses GCC-11: https://gcc.gnu.org/gcc-11/porting_to.html If you think this is a GCC-11 related issue, please block bug 732706.
Created attachment 716064 [details] build.log build log and emerge --info
Possible context of error(s): ERROR! Unexpected Exception, this is probably a bug: No module named 'resolvelib' ModuleNotFoundError: No module named 'resolvelib' result = CompletedProcess(args='ansible-galaxy init -v --offline test-role', returncode=250, stdout='the full traceback was:\n\nTraceback (most recent call last):\n File "/usr/lib/python-exec/python3.9/ansible-galaxy", line 104, in <module>\n mycli = getattr(__import__("ansible.cli.%s" % sub, fromlist=[myclass]), myclass)\n File "/usr/lib/python3.9/site-packages/ansible/cli/galaxy.py", line 26, in <module>\n from ansible.galaxy.collection import (\n File "/usr/lib/python3.9/site-packages/ansible/galaxy/collection/__init__.py", line 100, in <module>\n from ansible.galaxy.collection.concrete_artifact_manager import (\n File "/usr/lib/python3.9/site-packages/ansible/galaxy/collection/concrete_artifact_manager.py", line 38, in <module>\n from ansible.galaxy.dependency_resolution.dataclasses import _GALAXY_YAML\n File "/usr/lib/python3.9/site-packages/ansible/galaxy/dependency_resolution/__init__.py", line 26, in <module>\n from ansible.galaxy.dependency_resolution.providers import CollectionDependencyProvider\n File "/usr/lib/python3.9/site-packages/ansible/galaxy/dependency_resolution/providers.py", line 33, in <module>\n from resolvelib import AbstractProvider\nModuleNotFoundError: No module named \'resolvelib\'\n', stderr="ERROR! Unexpected Exception, this is probably a bug: No module named 'resolvelib'\n")
*** This bug has been marked as a duplicate of bug 795933 ***
It is hard to not file duplicates while the bug and the original bug does not have the same package in the subject.
I get it, especially in case of automated systems; it's much easier for a human to see that the stack trace in question has originated from /usr/bin/ansible-galaxy and that it comes from a bit not affected by input data. Which is why I am not complaining about this ticket having been created, marely have linked it to the root issue.
If there will be more duplicates, a "depends on" ( to have a link ) may help a bit =)
