I mentioned before that giving each test an individual file name does NOT help
to resolve the issue. Still the latter modules are not (re)-loaded and do not
trigger the
'raise Exception("bad")\n'
I wondered if python might not keep it's cache by path/filename but instead
per-hash.
In which case since all have the very same content they would be the same for
the module loader.
But using slightly changed content also did not resolve the issue.
** Description changed:
Recent (rebuild) is here
-
https://launchpadlibrarian.net/545919434/buildlog_ubuntu-impish-amd64.breezy-debian_2.8.63build1_BUILDING.txt.gz
+
https://launchpadlibrarian.net/547592506/buildlog_ubuntu-impish-amd64.breezy_3.2.1-1_BUILDING.txt.gz
It has plenty of self-test fails like
======================================================================
FAIL: breezy.tests.test_plugins.TestPlugins.test_plugin_appears_in_plugins
----------------------------------------------------------------------
Traceback (most recent call last):
testtools.testresult.real._StringException: log: {{{
1324.812 loading plugins!
1324.812 using _Path('breezy.testingplugins', [], [], ['.'])
1324.812 Traceback (most recent call last):
File "/<<PKGBUILDDIR>>/breezy/plugin.py", line 429, in _load_plugin_module
__import__(_MODULE_PREFIX + name)
ModuleNotFoundError: No module named 'breezy.testingplugins.plugin'
1324.812 Unable to load plugin 'plugin' from '.': No module named
'breezy.testingplugins.plugin'
WARNING Unable to load plugin 'plugin' from '.': No module named
'breezy.testingplugins.plugin'
1324.813 removed breezy.testingplugins from sys.modules
FYI this is somewhat related to (former maybe now hidden FTFBS of breezy)
https://bugs.launchpad.net/ubuntu/+source/breezy-debian/+bug/1933034
and more indirectly to (need new breezy to get lintian-brush to get thing
moving)
https://bugs.launchpad.net/ubuntu/+source/dulwich/+bug/1931369
-
---
This blocks https://bugs.launchpad.net/ubuntu/+source/dulwich/+bug/1933034
which has instructions on further rebuilds and combined tests after this is
resolved.
---
Interim Summary
The tests ran together fail
$ BRZ_PLUGIN_PATH=-site:-user LC_ALL=C.UTF-8 PYTHONPATH=/build/breezy-
xbGxjH/breezy-3.2.1/.pybuild/cpython3_3.9_breezy/build python3.9 ./brz
-Derror selftest -v breezy.tests.test_plugins.TestLoadingPlugins
Running all of them one by one works fine:
$ for t in
test_plugins.TestLoadingPlugins.test_plugin_with_bad_api_version_reports
test_plugins.TestLoadingPlugins.test_plugin_with_bad_name_does_not_load
test_plugins.TestLoadingPlugins.test_plugin_with_error
test_plugins.TestLoadingPlugins.test_plugin_with_error_suppress
test_plugins.TestLoadingPlugins.test_plugins_can_load_from_directory_with_trailing_slash
test_plugins.TestLoadingPlugins.test_plugins_from_different_dirs_can_demand_load
test_plugins.TestLoadingPlugins.test_plugins_with_the_same_name_are_not_loaded;
do BRZ_PLUGIN_PATH=-site:-user LC_ALL=C.UTF-8
PYTHONPATH=/build/breezy-xbGxjH/breezy-3.2.1/.pybuild/cpython3_3.9_breezy/build
python3.9 ./brz -Derror selftest -v $t; printf "\n\n\n\n\n\n\n\n\n"; done
On Debian unstable this isn't happening (there is always works in an
otherwise rather similar environment).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937173
Title:
FTBFS breezy 3.2.1-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/breezy/+bug/1937173/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
