Control: severity -1 important
On Thu, Jul 19, 2018 at 12:16:00PM +0200, JCF Ploemen wrote:
> The original bug reported here - partial failure of cram's test suite -
> seems to be triggered by python-coverage >= 4.5, first uploaded to
> Debian in Februari of 2018 (i.e. roughly 2 years after cram 0.7-1). With
> earlier versions of coverage, cram 0.7-1 builds fine. I don't know
> whether the bug is in cram, its test suite, or coverage though.
>
> Any known examples of cram failing in packages using it for their test
> suites? Otherwise, please consider doing an upload of cram that runs
> the test suite but ignores the outcome until there's more definitive
> info on the root cause of this bug.
Uploaded with ignoring test result and bug severity set to important.
Kind regards
Andreas.
--
http://fam-tille.de
