delta/systemd.git - github.com: systemd/systemd.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	test: store the key on a separate device	Frantisek Sumsal	2022-05-26	1	-5/+9
\|
*	test: generate a custom initrd for TEST-24 if $INITRD is unset	Frantisek Sumsal	2022-05-26	1	-0/+24
\| \| \| \|	Co-Authored-By: Yu Watanabe <watanabe.yu+github@gmail.com>
*	test: cover initrd->sysroot transition in TEST-24	Frantisek Sumsal	2022-05-25	1	-33/+30
\| \| \| \| \| \| \| \| \| \| \|	This should cover cases regarding devices with `OPTIONS+="db_persist"` during initrd->sysroot transition. See: * https://github.com/systemd/systemd/issues/23429 * https://github.com/systemd/systemd/pull/23218 * https://github.com/systemd/systemd/pull/23489 * https://bugzilla.redhat.com/show_bug.cgi?id=2087225
*	test: collect the coverage _before_ unmounting the rootfs	Frantisek Sumsal	2021-10-21	1	-1/+1
\| \| \| \|	d'oh!
*	test: collect coverage in a couple more codepaths	Frantisek Sumsal	2021-10-20	1	-0/+1
\| \| \| \| \| \| \|	Otherwise we'd miss coverage from TEST-{02,24,61}, since they don't go through the "standard" `check_result_common` hook. Follow-up to 7bf20e48bd7d641a39a14a7feb749b7e8b0fc0f6.
*	tests: add spdx headers to scripts and Makefiles	Zbigniew Jędrzejewski-Szmek	2021-10-18	1	-0/+1
\|
*	test: "detect" the test number automagically	Frantisek Sumsal	2021-04-26	1	-1/+1
\| \| \| \| \| \|	Specifying the test number manually is tedious and prone to errors (as recently proven). Since we have all the necessary data to work out the test number, let's do it automagically.
*	test: move the logic to support /skipped into shared logic	Zbigniew Jędrzejewski-Szmek	2021-04-23	1	-1/+1
\| \| \| \| \| \|	The logic to query test state was rather complex. I don't quite grok the point of ret=$((ret+1))… But afaics, the precise result was always ignored by the caller anyway.
*	test: make the test entrypoint scripts shellcheck-compliant	Frantisek Sumsal	2021-04-20	1	-26/+35
\|
*	tests: build the image once and then copy/extend it	Luca Boccassi	2021-01-24	1	-0/+1
\| \| \| \| \| \|	Building custom images for each test takes a lot of time. Build the default one, and if the test needs incompatible changes just copy it and extend it instead.
*	test: switch TEST-02-CRYPTSETUP and TEST-24-UNITTESTS	Zbigniew Jędrzejewski-Szmek	2020-09-24	2	-0/+80
	When tests are executed serially (the default), it seems better to launch the fairly generic test that runs the unittests early in the sequence. Right now the tests are ordered based on when they were written, but this doesn't make much sense.