This is accepted in Debian now and works fine on a test build.
The former upload is still stuck in proposed anyway:
breezy | 3.2.1-1ubuntu1 | jammy-proposed/universe | source
I synced the new version as it can replace the one in proposed without a
drawback and keeps auto-syncing from there.
--
** Changed in: breezy (Debian)
Status: New => Fix Released
--
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:
htt
https://launchpad.net/ubuntu/+source/breezy/3.2.1-1ubuntu1 fixes the
FTBFS due to test failures. (autopkgtest is still processing and may
get stuck due to other packages.)
** Changed in: breezy (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/breezy/+git/breezy/+merge/410678
--
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
Focal is also affected; Bionic is not. But in Bionic brz is python2, so
there is quite a big step.
--
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 notifi
Note: this affects the version of brz which is already in the archive,
so it's not really a regression in brz. Reproducible on Impish with:
bzr selftest breezy.tests.test_plugins
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Changed in: breezy (Debian)
Status: Unknown => New
--
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://
** Bug watch added: Debian Bug tracker #995410
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995410
** Also affects: breezy (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995410
Importance: Unknown
Status: Unknown
--
You received this bug notification because
This may also be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/breezy/+bug/1932313 , which
includes an upstream python commit that introduces the breakage
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
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 cas
I think I have laid some debugging groundwork here, but I'm lost.
This probably needs a reset and a new pair of eyes :-/
--
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
I have also lead in with two tests of type B and then it is
B - good
B - good
A - bad
So it seems like the ones that want to evaluate the log for the raised "bad"
can only go first and once. So it still could be that python no more re-loads
the code at all and thereby no more triggered "bad".
T
load_with_paths (tests/test_plugins.py) from sets up the paths that are needed
for this to work.
It reached load_plugins (from breezy/plugin.py) with
path _Path('breezy.testingplugins', [], [], ['.'])
I wondered if the python cache might keep the (failed) module and remember that
it failed to
The load error is intentional (it is a bad module name).
But the test expects the stringified exception
bad
while on the second execution it gets:
No module named 'breezy.testingplugins.some_error'
This checked error message comes from breezy/plugin.py
It is set by:
return record_plugin_war
Ok, I found a pair.
test_plugin_with_bad_api_version_reports and test_plugin_with_error work
individually.
But if run after one another the second one fails.
I changed their order and it is always the second that fails.
--
You received this bug notification because you are a member of Ubuntu
Bu
Of the test test_plugin_with_error seems the most simple and even if the same
is executed twice the second one fails.
So i leaves something yet unknown behind in the test environment that breaks
the second execution
.
brz selftest: /build/breezy-xbGxjH/breezy-3.2.1/brz
/build/breezy-xbGxjH/
To be clear a bunch of the warnings are intentional e.g. on the try to
load breezy.testingplugins.some_error
But I tried to reduce the variables:
test_plugins_with_the_same_name_are_not_loaded was failing when run
combined.
Overall we have:
test_plugins.TestLoadingPlugins.test_plugin_with_bad_ap
** Description changed:
Recent (rebuild) is here
https://launchpadlibrarian.net/545919434/buildlog_ubuntu-impish-amd64.breezy-debian_2.8.63build1_BUILDING.txt.gz
It has plenty of self-test fails like
==
FAIL: bree
This blocks breezy, but also breezy-debian, lintian-brush and dulwich (see bug
1933034).
Once the FTFBS here is resolved there is a series of rebuilds and combined
tests that need to be executed.
I outlined them at
https://bugs.launchpad.net/ubuntu/+source/breezy-debian/+bug/1933034/comments/6
Finally I found a command that fails in bad and works in good env
$ BRZ_CONCURRENCY=3 BRZ_HOME=debian/brzhome 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.
Locally reproducible in sbuild of impish
Most obvious difference is a newer python 3.9.2-3 -> 3.9.4-1
A re-build in Debian unstable works fine
Even Re-runnning the test in Impish after a failed build (chrooted into
the sbuild environment)
a) as a whole
BRZ_CONCURRENCY=3 BRZ_HOME=debian/brzhome B
In Debian this build issue is not present, compare these s390x builds
for example (done on almost the same time - so not as it often happens
months apart introducing a lot of build environment differences)
failing:
https://launchpadlibrarian.net/547563235/buildlog_ubuntu-impish-s390x.breezy_3.2.1-
** Package changed: breezy-debian (Ubuntu) => breezy (Ubuntu)
** Tags added: update-excuse
--
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
** Description changed:
- Plenty of self-test fails like
+ Recent (rebuild) is here
+
https://launchpadlibrarian.net/545919434/buildlog_ubuntu-impish-amd64.breezy-debian_2.8.63build1_BUILDING.txt.gz
+
+ It has plenty of self-test fails like
==
24 matches
Mail list logo
