- 14 Dec, 2018 3 commits
-
-
Chris Lamb authored
-
This is not enforced by code quality scripts but needed for release. Signed-off-by:
Chris Lamb <lamby@debian.org> -
The test set contains two tests that are designed to test the performance of file sets produced by historical versions of dh-make. Both tests use a special feature designed to excercise debian diff performance, or the related patch that is automatically generated for package format 3.0 (quilt). In both cases, however, the files in ./diff and ./orig are identical. There is no diff. Furthermore, dh-make never dealt with such diff sets. The files were probably duplicated by accident at some point. All such files in ./diff were removed. Signed-off-by:
Chris Lamb <lamby@debian.org>
-
- 13 Dec, 2018 18 commits
-
-
Signed-off-by:
Chris Lamb <lamby@debian.org> -
Signed-off-by:
Chris Lamb <lamby@debian.org> -
Signed-off-by:
Chris Lamb <lamby@debian.org> -
'testdata' -> 'testcase' 'test_data' -> 'testcase' 'testdir' -> 'specpath' 'targetdir' -> 'runpath' 'TESTSET' -> 'testset' 'RUNDIR' -> 'outpath' 'test_filter' -> 'onlyrun' 'ALWAYS_REBUILD' -> 'force_rebuild' 'JOBS' -> 'numjobs' 'DUMP_LOGS' -> 'dump_logs' 'VERBOSE' -> 'verbose' Signed-off-by:
Chris Lamb <lamby@debian.org> -
This commit moves the actual test phase (i.e. the package building and the all-important call to Lintian) into a separate module. Signed-off-by:
Chris Lamb <lamby@debian.org> -
This commit makes the runner more modular by splitting the preparation phase into its own module. Signed-off-by:
Chris Lamb <lamby@debian.org> -
This commit splits the test runner into two phases. The preparation phase copies all necessary files to the work directory in debian/test-out and fills the templates. The run phase builds packages and runs the test. Signed-off-by:
Chris Lamb <lamby@debian.org> -
This module was previously attached to the bottom of t/runtests. It is now separate. Signed-off-by:
Chris Lamb <lamby@debian.org> -
Chris Lamb authored
-
Chris Lamb authored
Clarify that symbols-file-missing-build-depends-package-field is emitted per-package in its long description, not based on a file.
-
The variable $build_path introduced in commit 4aaab6b1 is being passed as an argument but not being processed as such. This commit adds the variable as an argument in the function declaration. Signed-off-by:
Chris Lamb <lamby@debian.org> -
This commit adjusts the expected tags for tests after tag 'debian-watch-does-not-check-gpg-signature' was marked experimental (in commit 69d31855).
-
Chris Lamb authored
Don't emit systemd-service-file-missing-hardening-features for Type=oneshot "services" such as mdadm(8).
-
Chris Lamb authored
-
Chris Lamb authored
-
Chris Lamb authored
-
Chris Lamb authored
-
The test results were produced independent messages, and this one was missed. Signed-off-by:
Chris Lamb <lamby@debian.org>
-
- 12 Dec, 2018 16 commits
-
-
Chris Lamb authored
Apply a patch set from Felix Lechner to sign test packages. when a upstream/private-key.asc is present. (MR: !93)
-
This is a test to verify orig tarball signing. It is thus also a test for false positives of 'orig-tarball-missing-upstream-signature' Signed-off-by:
Chris Lamb <lamby@debian.org> -
This commit causes upstream packages of the form orig.tar.gz to be signed if a private key is found at upstream/private-key.asc. For now, this works only in suite 'tests'. Signed-off-by:
Chris Lamb <lamby@debian.org> -
Both are available in stretch-backports. /usr/bin/gpg-agent was also available in the original stretch. Both package names have changed since then but the present names were already available in stretch via virtual packages. This commit uses the current package name from unstable. Signed-off-by:
Chris Lamb <lamby@debian.org> -
The detection of arch-dependent files in checks/files.pm now excludes executable ASCII files. For these tests, changing the Architecture to 'all' resulted in the tag 'not-binnmuable-all-depends-any'. A trade off was made to add the tag instead. Signed-off-by:
Chris Lamb <lamby@debian.org> -
The detection of arch-dependent files in checks/files.pm now excludes executable ASCII files. For this test package holding an app, it seemed appropriate to change the Architecture to 'all'. Signed-off-by:
Chris Lamb <lamby@debian.org> -
In accordance with the author's wishes as received in orig/README, this tag is added without modifications to other files. Signed-off-by:
Chris Lamb <lamby@debian.org> -
Sometimes file_info is unsafe to call. The recommended call to is_open_ok did not solve the issue, so checking directly. Signed-off-by:
Chris Lamb <lamby@debian.org> -
Chris Lamb authored
Signed-off-by:
Chris Lamb <lamby@debian.org> -
This commit adjusts the autopkgtest command to the new way commas in 'onlyrun' now separate fully styled selectors. Signed-off-by:
Chris Lamb <lamby@debian.org> -
This commit uses the new test selection mechanism in favor over the present one. Signed-off-by:
Chris Lamb <lamby@debian.org> -
This module provides an alternative way to select tests to run. The syntax is very similar except for one detail: Commas now separate fully styled selectors such as "tag:some-tag,suite:changes" (which are combined via a logical OR). It is no longer advisable to use something like "suite:tests,changes". As a new feature, one can now select all tests connected to particular Lintian check with 'check:'. It is designed to more or less make the tag selector 'tag:' obsolete in everyday use, although it will remain available. Otherwise, tests are selected very much the way they were before, except one may find it useful to specify the desired category in onlyrun=. (Reasonable attempts are made to guess what was meant.) Please choose from: * test: runs the named test (or tests) in any of the suites * suite: runs all tests in the named suite * tag: runs all tests regarding the named tag * check: runs all tests regarding the named Lintian check Signed-off-by:
Chris Lamb <lamby@debian.org> -
This commit provides a direct way for a test to infer its suite from its own path. A test no longer has to rely on a variable that was passed down from the test selection mechanism. Signed-off-by:
Chris Lamb <lamby@debian.org> -
An absolute reference to the testset is needed to safely calculate the suite from a test's specification path. Signed-off-by:
Chris Lamb <lamby@debian.org> -
This enviroment variable is needed in Test::Lintian::Filter.pm and is also useful when running tests via TAP::Harness. Signed-off-by:
Chris Lamb <lamby@debian.org> -
Signed-off-by:
Chris Lamb <lamby@debian.org>
-
- 11 Dec, 2018 3 commits
-
-
Chris Lamb authored
-
The type designates whether a test is intended to build native or non-native packages. This declaration is closely tied to the templates served. Most significantly, non-native packages require a watch file, while native packages will not tolerate one. This declaration is also found in the default settings or the skeleton definitions and thus no longer needed for each test. This commit removes all such statements from the tests in t/tests. Some tests declared Type: native even though that was the default. Those statements were likewise removed. Signed-off-by:
Chris Lamb <lamby@debian.org> -
The package type declaration is closely tied to the templates being served. This commit means that all tests relying on the 'builder-only' skeleton will automatically declare a non-native type. At the time of writing, that skeleton was only used by two tests for historical debhelper templates, generic-dh-make-2005 and generic-dh-make-2008. Those two tests no longer need to provide their own declarations. Signed-off-by:
Chris Lamb <lamby@debian.org>
-