[From nobody Tue Oct 6 08:34:23 2026 Received: (at maintonly) by bugs.debian.org; 11 Nov 2020 14:05:33 +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=-13.5 required=4.0 tests=BAYES_00,DIGITS_LETTERS, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, MD5_SHA1_SUM,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.2-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 6; hammy, 150; neutral, 123; spammy, 0. spammytokens: hammytokens:0.000-+--autopkgtest, 0.000-+--sk:README, 0.000-+--sk:readme., 0.000-+--sk:README., 0.000-+--apparmor Return-path: <sudipm.mukherjee@gmail.com> Received: from mail-wm1-x334.google.com ([2a00:1450:4864:20::334]:37211) by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <sudipm.mukherjee@gmail.com>) id 1kcqkf-0004Os-QF for maintonly@bugs.debian.org; Wed, 11 Nov 2020 14:05:33 +0000 Received: by mail-wm1-x334.google.com with SMTP id c16so2443335wmd.2 for <maintonly@bugs.debian.org>; Wed, 11 Nov 2020 06:05:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:message-id:subject:to; bh=3bQ9ni7CBt4AcwEF5AghtDAuAJYRzvxtn2njgiePe3c=; b=ZeRS21g2rPEnHu6u1JmFqLa6jM9B/FLFGJc/tsxmYS95BfBBHpoB812/TiZQYIqaOg Y+F3blnDoIBuKOZzy+BgMTfTwXgxol+qK/Wy2mYygZWxxMpyjSHYgHrcyV+Ua/1HSJi2 bmy96C/Mhjbeb7QONYqZLG9DyzSTvQPKY4ht5uBHOmAHmDDn65jyt4X++5SKwE4ugWWh AJBh4AKqqS+iFn+viUGCgRTCoCnRsudU1Z35XvRStPqJa26MqlbLq/Advnn1dBaO7cmJ h6ey1kYI+lAHykxSchfVlIZNbd+NLZAhP23d9WepeZ1/UjrX3lMYmjNYg/n6tWrHDM32 GVZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:message-id:subject:to; bh=3bQ9ni7CBt4AcwEF5AghtDAuAJYRzvxtn2njgiePe3c=; b=rTDrRE7m4lUCN0AfgZhoyeQYEP9gK0a/J1ROUBvZGtK0IFp6BUoV7Kx+i98on8xkdI XvM03i98DQGzbqi2mIsxQpb6UE4MgXSq68wd/1dE8a3tBqDxPVq+vdg9rRMEZCPnOmvL QnIRIUWHb/0f9Q+N3RUwSLCLUj/o27EbA4kdjJBF7TlMr/Q64UbGwoPRnOCZBt2lTOaN 5EDY+9/kshyhA9omR6NYKeok6vqHRdcHdHuBLTRLlos2dlUqRKeJ8TUU3nTz9r+nwqiY ZgoA8nrlGD1J3m3SbMIB0ZnQGoPsvolovole8Vm0wOsm9oERXAE0NbsTBGIGIYe5IaQH I+qA== X-Gm-Message-State: AOAM531sQsMpDIprE3wzZyvKfUhjKvAsdZddOvQIt5Sfx3BjLz6DcPMr mfRVtfb63+TTG7FZEouPjrPQzh8rMJeAEg== X-Google-Smtp-Source: ABdhPJzcuFUGiIbIJQ+nSagLdwfYhzJW61nPXcbCzYegVrBuQSmx0P/x7kT/0h/XCSembs0ZTzOt8g== X-Received: by 2002:a1c:e056:: with SMTP id x83mr4566052wmg.83.1605103528775; Wed, 11 Nov 2020 06:05:28 -0800 (PST) Received: from debian.vm (host-92-5-241-147.as43234.net. [92.5.241.147]) by smtp.gmail.com with ESMTPSA id c17sm2634525wro.19.2020.11.11.06.05.27 for <maintonly@bugs.debian.org> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 11 Nov 2020 06:05:28 -0800 (PST) Date: Wed, 11 Nov 2020 06:05:28 -0800 (PST) X-Google-Original-Date: Wed, 11 Nov 2020 14:05:27 GMT From: Sudip Mukherjee <sudipm.mukherjee@gmail.com> X-Google-Original-From: Sudip Mukherjee <sudip@debian.vm> Received: from debian.vm (localhost [127.0.0.1]) by debian.vm (8.15.2/8.15.2/Debian-20) with ESMTP id 0ABE5RVp021618 for <maintonly@bugs.debian.org>; Wed, 11 Nov 2020 14:05:27 GMT Received: (from sudip@localhost) by debian.vm (8.15.2/8.15.2/Submit) id 0ABE5R0S021617; Wed, 11 Nov 2020 14:05:27 GMT Message-Id: <202011111405.0ABE5R0S021617@debian.vm> Subject: node-vue-hot-reload-api: autopkgtest must be marked superficial To: <maintonly@bugs.debian.org> X-Mailer: mail (GNU Mailutils 3.10) Delivered-To: maintonly@bugs.debian.org Source: node-vue-hot-reload-api X-Debbugs-CC: elbrus@debian.org Severity: important Usertags: superficialtest Dear Maintainer, It has been noticed that the autopkgtest in node-vue-hot-reload-api is running a trivial command that does not provide significant test coverage: - nodejs -e "require('vue-hot-reload-api');" Executing that command is considered to be a trivial test, which does not provide significant coverage for a package as a whole. But these tests are a useful way to detect regressions in dependencies and prevent them from breaking your package. However, it is important that we are realistic about the level of test coverage provided by these commands: most regressions cannot be detected in this way. So it is not appropriate for packages with only superficial tests to have the reduced migration time to migrate from unstable to testing as that means less opportunity for testing by users compared to the package with no tests. To support this, the keyword "Restrictions: superficial" has been defined [1]. Packages where all tests are marked with this keyword are not considered for the reduced migration age from unstable to testing, and will not be allowed to migrate automatically in later stages of the freeze [2]. Its always better to have more extensive testing than having superficial testing, which again is better than having no test. Please consider i) Adding a non-trivial test, and/or ii) Mark the trivial test with "Restrictions: superficial", similar to [3] or [4]. The Release Team has listed this issue in the list of Release Critical Issues for bullseye [5] and has mentioned that the test must be marked superficial if it is not testing one of its own installed binary packages in some way. As a result, the severity of this bug report might be increased to serious in future. [1] https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst#defined-restrictions [2] https://release.debian.org/bullseye/freeze_policy.html [3] https://salsa.debian.org/utopia-team/dbus/-/commit/a80908df7d119b181eec5eb0542634a30c2ad468 [4] https://salsa.debian.org/apparmor-team/apparmor/-/commit/580667513a097088ebe579884b38ac8d8666d3b3 [5] https://release.debian.org/bullseye/rc_policy.txt -- Regards Sudip ]