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

	Commit message (Collapse)	Author	Age	Files	Lines
*	test: tweak TriggerLimitIntervalSec= if we're running w/o KVM as well	Frantisek Sumsal	2021-12-22	1	-5/+6
\| \| \| \| \| \| \| \| \|	since in that case we might be also slow enough to miss the rate-limit window. However, let's not set the trigger limit unconditionally to still have coverage for the unaltered path unit (but without sacrificing CI stability). See: https://github.com/systemd/systemd/pull/21808#issuecomment-998927401
*	test: tweak the path trigger limit a bit when collecting coverage	Frantisek Sumsal	2021-12-20	1	-0/+12
\| \| \| \| \| \| \|	Basically the same thing as in e70103e, but for TEST-63. Uses directives introduced by 47dba9f. Follow-up to aaae822.
*	tests: add spdx headers to scripts and Makefiles	Zbigniew Jędrzejewski-Szmek	2021-10-18	1	-0/+1
\|
*	core: Check unit start rate limiting earlier	Daan De Meyer	2021-08-25	2	-0/+10
	Fixes #17433. Currently, if any of the validations we do before we check start rate limiting fail, we can still enter a busy loop as no rate limiting gets applied. A common occurence of this scenario is path units triggering a service that fails a condition check. To fix the issue, we simply move up start rate limiting checks to be the first thing we do when starting a unit. To achieve this, we add a new method to the unit vtable and implement it for the relevant unit types so that we can do the start rate limit checks earlier on.