Bug#965370: RFS: wand/0.6.2-1 -- Python interface for ImageMagick library (Python 3)
søn. 2. aug. 2020 kl. 18:45 skrev Adam Borowski <kilobyte@angband.pl>:
>
> On Mon, Jul 20, 2020 at 01:17:13PM +0000, Håvard Flaget Aasen wrote:
> > * Package name : wand
> > Version : 0.6.2-1
>
> > Changes since the last upload:
> >
> > * New upstream version 0.6.2
> > * Set upstream metadata fields: Bug-Submit.
> > * Update salsa CI
> > - Watch all variations of reprotest.
> > * Use spaces rather than tabs in d/copyright
> > * Rebase patches
> > * flask sphinx theme is now in the upstream repository
> > - Remove patch and lintian-override
>
> Alas, it fails to build; during tests:
>
> =================================== FAILURES ===================================
> ________________________________ test_artifacts ________________________________
>
> def test_artifacts():
> with Image(filename='rose:') as img:
> img.artifacts['key'] = 'value'
> assert 'date:create' in img.artifacts
> assert img.artifacts['key'] == 'value'
> assert img.artifacts['novalue'] is None
> > assert len(img.artifacts) > 0
> E AssertionError: assert 0 > 0
> E + where 0 = len(<wand.image.ArtifactTree object at 0x7f064a3ce760>)
> E + where <wand.image.ArtifactTree object at 0x7f064a3ce760> = <wand.image.Image: a698f2f 'PNM' (70x46)>.artifacts
>
> tests/image_properties_test.py:51: AssertionError
> =============================== warnings summary ===============================
> .pybuild/cpython3_3.8_wand/build/tests/color_test.py::test_user_error
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_wand/build/wand/color.py:113: OptionWarning: unrecognized color `not_a_color' @ warning/color.c/GetColorCompliance/1057
> self.raise_exception()
>
> -- Docs: https://docs.pytest.org/en/latest/warnings.html
> = 1 failed, 538 passed, 7 skipped, 3 deselected, 2 xfailed, 1 warnings in 16.48 seconds =
>
>
> Meow!
> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁
> ⢿⡄⠘⠷⠚⠋⠀ It's time to migrate your Imaginary Protocol from version 4i to 6i.
> ⠈⠳⣄⠀⠀⠀⠀
>
Thanks for the review.
I'm not entirely sure why this test failed, it was succeeding when I
uploaded it. It also looks like the current version in Debian fails
for the same test.
I uploaded a new version, and ended up disabling the testsuite during
build. This is the same testsuite that I enabled in the last release.
When the package gets uploaded I will reopen bug [#761325]
The autopkgtest is still active and seems to be more reliable.
Håvard
[#761325] https://bugs.debian.org/761325
Reply to: