• Bug#1102124: wacomtablet: FTBFS: failing tests

    From Santiago Vila@21:1/5 to All on Sat Apr 5 13:10:02 2025
    This is a multi-part message in MIME format.
    Package: src:wacomtablet
    Version: 3.2.0-4
    Severity: serious
    Tags: ftbfs patch

    Dear maintainer:

    During a rebuild of all packages in unstable, your package failed to build:

    [ please read notes at the end ]

    --------------------------------------------------------------------------------
    [...]
    The following tests FAILED:
    7 - Test.Common.ProfileManager (Subprocess aborted)
    Errors while running CTest
    make[2]: *** [Makefile:74: test] Error 8
    make[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu' dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j2 test ARGS\+=--verbose ARGS\+=-j2 returned exit code 2
    make[1]: *** [debian/rules:9: override_dh_auto_test] Error 25
    make[1]: Leaving directory '/<<PKGBUILDDIR>>'
    make: *** [debian/rules:6: binary] Error 2
    dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --------------------------------------------------------------------------------

    The above is just how the build ends and not necessarily the most relevant part.
    If required, the full build log is available here:

    https://people.debian.org/~sanvila/build-logs/202504/

    About the archive rebuild: The build was made on virtual machines from AWS, using sbuild and a reduced chroot with only build-essential packages.

    If you could not reproduce the bug please contact me privately, as I
    am willing to provide ssh access to a virtual machine where the bug is
    fully reproducible.

    If this is really a bug in one of the build-depends, please use
    reassign and add an affects on src:wacomtablet, so that this is still
    visible in the BTS web page for this package.

    Notes:

    - The random build failures happen in both bookworm and trixie/sid,
    that's why I've put the bookworm version in the Version field.
    However, I have only tested the fix in trixie/sid.

    - The tests which fail seem to be different every time.

    - On the AWS machines with 1 CPU where I tested it, it does not fail.
    On the AWS machines with 2 CPUs where I tested it, it fails 50% of
    the time.

    - The attached patch, which makes tests to be run sequentially,
    fixes the problem here.

    - I see some similarity between this problem and #1069495, but I don't
    know if they are related at all, so I think it's better to file a new bug, since we have a fix for this one.

    Thanks. RnJvbSBiOTAwM2ZhMTg1M2NjYWVhZTE1YjA5YWJlMTJhZWQ0YjZiYmZiMDk1IE1vbiBTZXAg MTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBTYW50aWFnbyBWaWxhIDxzYW52aWxhQGRlYmlhbi5v cmc+CkRhdGU6IFNhdCwgNSBBcHIgMjAyNSAxMjoxNTowMCArMDIwMApTdWJqZWN0OiBbUEFU Q0hdIERvIG5vdCBydW4gdGVzdHMgaW4gcGFyYWxsZWwuIENsb3NlczogI1hYWFhYWFguCgot LS0KIGRlYmlhbi9ydWxlcyB8IDIgKy0KIDEgZmlsZSBjaGFuZ2VkLCAxIGluc2VydGlvbigr KSwgMSBkZWxldGlvbigtKQoKZGlmZiAtLWdpdCBhL2RlYmlhbi9ydWxlcyBiL2RlYmlhbi9y dWxlcwppbmRleCA2Njg5Mzk1Li5kNjVlODQxIDEwMDc1NQotLS0gYS9kZWJpYW4vcnVsZXMK KysrIGIvZGViaWFuL3J1bGVzCkBAIC02LDQgKzYsNCBAQCBleHBvcnQgREVCX0JVSUxEX01B SU5UX09QVElPTlMgPSBoYXJkZW5pbmc9K2FsbAogCWRoICRACiAKIG92ZXJyaWRlX2RoX2F1 dG9fdGVzdDoKLQl4dmZiLXJ1biAtcyAiLXNjcmVlbiAwIDEwMjR4NzY4eDI0ICtleHRlbnNp b24gUkFORFIgK2V4dGVuc2lvbiBSRU5ERVIgK2V4dGVuc2lvbiBHTFgiIC1hIGRidXMtcnVu LXNlc3Npb24gZGhfYXV0b190ZXN0CisJeHZmYi1ydW4gLXMgIi1zY3JlZW4gMCAxMDI0eDc2 OHgyNCArZXh0ZW5zaW9uIFJBTkRSICtleHRlbnNpb24gUkVOREVSICtleHRlbnNpb24gR0xY IiAtYSBkYnVzLXJ1bi1zZXNzaW9uIGRoX2F1dG9fdGVzdCAtLW1heC1wYXJhbGxlbD0xCi0t IAoyLjM5LjUKCg==

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Sat Apr 5 20:10:01 2025
    This is a multi-part message in MIME format...

    Your message dated Sat, 05 Apr 2025 18:06:34 +0000
    with message-id <[email protected]>
    and subject line Bug#1102124: fixed in wacomtablet 6.3.4-2
    has caused the Debian Bug report #1102124,
    regarding wacomtablet: FTBFS: failing tests
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected]
    immediately.)


    --
    1102124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102124
    Debian Bug Tracking System
    Contact [email protected] with problems

    Received: (at submit) by bugs.debian.org; 5 Apr 2025 10:58:55 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-120.5 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,FROMDEVELOPER,HAS_PACKAGE,
    MD5_SHA1_SUM,SPF_HELO_NONE,SPF_NONE,UNPARSEABLE_RELAY,
    USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST,X_DEBBUGS_CC
    autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 21; hammy, 150; neutral, 181; spammy,
    0. spammytokens:
    hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
    0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
    0.000-+--H*RT:311, 0.000-+--H*RT:108
    Return-path: <[email protected]>