[01:54] <kasper81> hey guys, i have a automake test question. does anyone here knows how to print the name of a test "being" run?
[01:54] <kasper81> one of my test is hanging in ci, but i don't know which one is it. i was thinking if it is possible to just enable printing the test name "before" it is started.
[01:55] <kasper81> the default behavior is that it would print PASS <testname>, FAIL <testname>, XFAIL <testname> or SKIP <testname>.
[01:56] <kasper81> but if the test hangs, then there is no way of knowing which one was it with the default configuration.
[01:56] <sarnold> kasper81: I don't know much about automake, but I don't think of it as actually doing anything like that -- I thought it was just a component of building a makefile
[01:57] <sarnold> kasper81: is this a test that's part of your package's test suite? or is this a test used as part of configure?
[01:57] <kasper81> https://www.gnu.org/software/automake/manual/html_node/Scripts_002dbased-Testsuites.html#Scripts_002dbased-Testsuites
[01:57] <kasper81> it is actually this feature of automake "scripting tests" which i am referring to.
[01:57] <kasper81> it provides the infrastructure for testing
[01:58] <kasper81> the wrapper scripts, which generate the messages PASS/FAIL/XFAIL/SKIP i mentioned above are generated by automake itself.
[01:59] <sarnold> kasper81: oh wow. thanks. sorry for the distraction then :)
[02:01] <kasper81> no problem, it's new for me too but going by github search, there are like million Makefile.am which uses this test infra.. so there must be people for whom it's their bread and butter. i am just looking to touch base with one of them. :D
[02:01] <kasper81> https://github.com/search?q=XFAIL_TESTS+filename%3Amakefile.am&type=Code (requires signed in user)
[02:02] <sarnold> heh I just learned yesterday that the code search requires a signed in user
[06:28] <icey> I just noticed a strange autopkgtest failure in setuptools; volatildap's tests fail when using only setuptools from proposed (`--apt-pocket=proposed=src:setuptools`), but if I run with `--apt-pocket=proposed` it passes its tests
[07:17] <icey> mwhudson: I'm picking breezy back up today / tomorrow, hoping to narrow down cause for the failures and maybe propose a fix
[10:15] <mwhudson> icey: good luck!
[13:58] <xnox> i am trying to figure out if my internets are here or not
[13:59] <ogra> there are here but not there 🙂
[13:59] <ogra> (there is some issue in the canonical network)
[14:00] <ogra> xnox, ^^^
[14:00] <xnox> yeah, figured by now
[14:04] <Unit193> But at least you have IRC!
[14:06] <ogra> seems to be back (partzs at least)
[15:54] <slyon> ddstreet: FYI: I'm doing some cgroups v2 testing here: https://bileto.ubuntu.com/#/ticket/4602 let's see how it works, running all the autopkgtests
[15:54] <slyon> I included all the changes you staged in git
[16:29] <xnox> sil2100:  https://bileto.ubuntu.com/#/ticket/4594 is it normal that i don't see any autopkgtest results?
[16:30] <xnox> or should i like upload that into security-proposed ppa?
[17:04] <sil2100> xnox: hm, let me look
[17:04] <sil2100> ARGH, wait, bileto is dying I se
[17:04] <sil2100> *see
[17:06] <sil2100> Looks like an issue accessing the amqp queue
[17:06] <sil2100> xnox: I'll try looking into that in a bit
[19:13] <ddstreet> slyon cool, though i have no clue what all that stuff on the bileto web page means
[19:15] <slyon> Well, it's just a PPA which can automatically run all the usual autopkgtests and migration scripts for testing