| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
It seems the ubuntu:lunar image has a user with UID 1000 already
which was not the case in previous versions.
|
| |
|
|
|
|
|
| |
The documentation will not realistically vary between architectures so
building it twice is just wasting time and resources.
|
|
|
|
|
| |
The checks mostly deal with verifying the syntax of the documentation
files and the po4a translations which have no tests otherwise.
|
|
|
|
|
|
|
|
|
| |
autopkgtest says:
Tests may not modify the source tree (and may not have write access to it).
We don't really modify the source of course, but we created our build/
directory in the tree, which seems to work just fine (for now), but lets
be nice.
|
|
|
|
|
|
|
|
| |
If the system tells us that a core dump was created we should try to
display the contained info as that system might not be easily available
when we see the error (like C-I or autopkgtest).
Gbp-Dch: Ignore
|
|
|
|
|
| |
This reverts commit d96c9a0280bffcfb0f4a319e003e9af60c6cfaf1.
It is not correct for master.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This should avoid test failures on ubuntu:bionic
|
|
|
|
| |
This ensures that we don't hang waiting for debconf.
|
|
Salsa has support for GitLab CI. This introduces a test setup
for it, derived from the ones for shippable and travis. It is
not optimal yet: The build is run in the test stage. Fixing this
requires us to separate test from build dependencies, and storing
build/ as an artifact of the build stage; since build and test
stage run on different runners with fresh checkouts and images.
|