lp:~sbeattie/qa-regression-testing

Owned by Steve Beattie
Get this repository:
git clone https://git.launchpad.net/~sbeattie/qa-regression-testing
Only Steve Beattie can upload to this repository. If you are Steve Beattie please log in for upload directions.

Branches

Name Last Modified Last Commit
test-lpci-noble-jobs 2024-05-04 16:47:24 UTC
lpci: add noble to job matrices for all tests

Author: Steve Beattie
Author Date: 2024-05-04 16:47:24 UTC

lpci: add noble to job matrices for all tests

Signed-off-by: Steve Beattie <steve.beattie@canonical.com>

todo 2024-05-01 07:01:55 UTC
TODO: test-cgroup.py: flesh out testcases

Author: Steve Beattie
Author Date: 2017-07-07 21:52:36 UTC

TODO: test-cgroup.py: flesh out testcases

misc-fixes-in-progress-2024.04.24 2024-05-01 06:45:59 UTC
test-ghostscript.py: convert conversion test to subtests

Author: Steve Beattie
Author Date: 2024-04-25 06:35:18 UTC

test-ghostscript.py: convert conversion test to subtests

Signed-off-by: Steve Beattie <steve.beattie@canonical.com>

lpci-apply_updates_before_testing 2024-04-26 23:07:18 UTC
lpci: run `apt upgrade` before exercising tests

Author: Steve Beattie
Author Date: 2024-04-26 18:37:02 UTC

lpci: run `apt upgrade` before exercising tests

The automatic runs of qa-regression-testing were failing in
the util-linux tests, even though the most recent util-linux
security update had been published to the ubuntu archive, because
lpci explicitly does not apply updates to the spawned test
environments that the jobs are run in. Furthermore, there is no
specific job configuration to tell lpci to apply updates first in
https://lpci.readthedocs.io/en/latest/configuration.html#job-definitions

To work around this limitation, add a run-before step in each job to run
`apt upgrade` so that the most up-to-date version of a package is tested
against.

An open question here is whether it would be more appropriate to use
`dist-upgrade` rather than a simple `upgrade`.

- v1: initial attempt
- v2: disable interactive prompts when upgrading

Signed-off-by: Steve Beattie <steve.beattie@canonical.com>
Bug: https://bugs.launchpad.net/lpci/+bug/2063880
MR: https://code.launchpad.net/~sbeattie/qa-regression-testing/+git/qa-regression-testing/+merge/465105

ecdsautils-lp-ci 2023-12-12 05:38:52 UTC
test-ecdsautils: disable CVE-2022-24884 in LP CI for bionic

Author: Steve Beattie
Author Date: 2023-07-23 23:17:10 UTC

test-ecdsautils: disable CVE-2022-24884 in LP CI for bionic

The fix for CVE-2022-24884 is only available in Ubuntu Pro on bionic,
which is not currently available in the LP CI infrastructure. Expect
this test to fail in LP CI in bionic, but run the test so that if
this ever changes, then the test will start unexpectedly succeeding
and cause the CI run to fail, letting us adjust.

Signed-off-by: Steve Beattie <steve.beattie@canonical.com>
Acked-by: Alex Murray <alex.murray@canonical.com>
MR: https://code.launchpad.net/~sbeattie/qa-regression-testing/+git/qa-regression-testing/+merge/448427

glibc-security-tests 2023-11-01 04:51:14 UTC
test-kernel-security: add simple shared library for LD_* tests

Author: Steve Beattie
Author Date: 2023-11-01 04:51:14 UTC

test-kernel-security: add simple shared library for LD_* tests

In jammy and other systemd based releases, preloading libmemusage ends
up conflicting (I suspect) with systemd's allocation routines, in such a
way that the pam_systemd either throws an assert in its json handling
code (wtf?!) or segfaults.

This commit creates a simple library for use as a LD_PRELOAD and
LD_AUDIT target, and switched the test to use it. *Ideally* it
should get temporarily installed in one of the system libraries,
as the loader will do some magic around that for setuid binaries,
but the kernel should get there first.

Signed-off-by: Steve Beattie <steve.beattie@canonical.com>

test-coreutils 2023-08-30 23:16:26 UTC
test-coreutils.py: run in lpci

Author: Steve Beattie
Author Date: 2023-08-30 23:16:26 UTC

test-coreutils.py: run in lpci

Signed-off-by: Steve Beattie <steve.beattie@canonical.com>

util-linux-tests 2023-07-20 22:49:05 UTC
test-util-linux.py: disable tests that fail in lpci environment

Author: Steve Beattie
Author Date: 2023-07-20 22:49:05 UTC

test-util-linux.py: disable tests that fail in lpci environment

Signed-off-by: Steve Beattie <steve.beattie@canonical.com>

moar-ci-tests 2023-07-20 20:45:49 UTC
[WIP] .launchpad.yaml: enable util-linux tests

Author: Steve Beattie
Author Date: 2023-07-07 07:07:45 UTC

[WIP] .launchpad.yaml: enable util-linux tests

Signed-off-by: Steve Beattie <steve.beattie@canonical.com>

ci-test-git 2023-05-16 03:41:11 UTC
WIP: lpcraft-runner: export env var for skipping tests in lpci

Author: Steve Beattie
Author Date: 2023-05-16 03:41:11 UTC

WIP: lpcraft-runner: export env var for skipping tests in lpci

[WIP: trying to see if I can make the udhcpc test work]

Signed-off-by: Steve Beattie <steve.beattie@canonical.com>

install-check-improvements 2022-08-08 03:59:16 UTC
[WIP] add support for ss(1) output

Author: Steve Beattie
Author Date: 2022-06-19 05:54:11 UTC

[WIP] add support for ss(1) output

Signed-off-by: Steve Beattie <steve.beattie@canonical.com>

kernel-security-riscv-fixes 2020-09-18 05:43:24 UTC
test-kernel-security: update test test_190_config_have_stack_protector for ri...

Author: Colin Ian King
Author Date: 2020-09-15 12:16:47 UTC

test-kernel-security: update test test_190_config_have_stack_protector for riscv64

The new riscv64 architecture does not yet support stack protector so
disable this for test for kernels 5.8 and lower on riscv64. As yet,
it's still to early to know when this will be implemented for this
architecture, so make the test fail for 5.9+ so we can catch this
config setting being disabled for new releases until it gets implemented.

Signed-off-by: Colin Ian King <colin.king@canonical.com>

112 of 12 results
This repository contains Public information 
Everyone can see this information.

Subscribers