Received: (at submit) by bugs.debian.org; 26 May 2022 19:25:57 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.2-bugs.debian.org_2005_01_02
	(2018-09-13) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-16.6 required=4.0 tests=BAYES_00,FROMDEVELOPER,
	SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham
	autolearn_force=no version=3.4.2-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 11; hammy, 150; neutral, 139; spammy,
	0. spammytokens: hammytokens:0.000-+--python3, 0.000-+--pkgbuilddir,
	0.000-+--PKGBUILDDIR, 0.000-+--H*RU:178.79.145.134,
	0.000-+--Hx-spam-relays-external:sk:xanadu.
Return-path: <lucas@debian.org>
Received: from xanadu.blop.info ([178.79.145.134]:33862)
	by buxtehude.debian.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <lucas@debian.org>)
	id 1nuJ7M-0003p7-Sh
	for submit@bugs.debian.org; Thu, 26 May 2022 19:25:57 +0000
Received: from [127.0.0.1] (helo=xanadu.blop.info)
	by xanadu.blop.info with smtp (Exim 4.89)
	(envelope-from <lucas@debian.org>)
	id 1nuJ7K-00046O-Q5
	for submit@bugs.debian.org; Thu, 26 May 2022 21:25:55 +0200
Received: (nullmailer pid 59123 invoked by uid 1000);
	Thu, 26 May 2022 19:19:26 -0000
Date: Thu, 26 May 2022 21:19:26 +0200
From: Lucas Nussbaum <lucas@debian.org>
To: submit@bugs.debian.org
Subject: poolcounter: FTBFS: dh_auto_test: error: make -j8 test returned exit
 code 2
Message-ID: <Yo/Svv1kp3WcXW69@xanadu.blop.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Delivered-To: submit@bugs.debian.org

Source: poolcounter
Version: 1.1.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> /usr/bin/pytest /usr/bin/pytest-3 -v
> ============================= test session starts ==============================
> platform linux -- Python 3.10.4, pytest-6.2.5, py-1.10.0, pluggy-1.0.0 -- /usr/bin/python3
> cachedir: .pytest_cache
> rootdir: /usr/bin
> collecting ... ERROR: not found: /usr/bin/pytest-3
> (no name '/usr/bin/pytest-3' in any of [])
> 
> collected 0 items
> 
> =============================== warnings summary ===============================
> ../../../usr/lib/python3/dist-packages/_pytest/cacheprovider.py:428
>   /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:428: PytestCacheWarning: could not create cache path /usr/bin/.pytest_cache/v/cache/nodeids
>     config.cache.set("cache/nodeids", sorted(self.cached_nodeids))
> 
> ../../../usr/lib/python3/dist-packages/_pytest/stepwise.py:49
>   /usr/lib/python3/dist-packages/_pytest/stepwise.py:49: PytestCacheWarning: could not create cache path /usr/bin/.pytest_cache/v/cache/stepwise
>     session.config.cache.set(STEPWISE_CACHE_DIR, [])
> 
> -- Docs: https://docs.pytest.org/en/stable/warnings.html
> ============================= 2 warnings in 0.00s ==============================
> make[1]: *** [Makefile:28: test] Error 4
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_auto_test: error: make -j8 test returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/poolcounter_1.1.3-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220525&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
