4 Commits

Author	SHA1	Message	Date
Frantisek Sumsal	8470a16d6f	test: tweak TriggerLimitIntervalSec= if we're running w/o KVM as well ... 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	2021-12-22 08:56:20 +09:00
Frantisek Sumsal	2cb726adf5	test: tweak the path trigger limit a bit when collecting coverage ... Basically the same thing as in e70103e, but for TEST-63. Uses directives introduced by 47dba9f. Follow-up to aaae822.	2021-12-20 22:05:14 +00:00
Zbigniew Jędrzejewski-Szmek	7b3cec95db	tests: add spdx headers to scripts and Makefiles	2021-10-18 09:04:45 +02:00
Daan De Meyer	9727f2427f	core: Check unit start rate limiting earlier ... 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.	2021-08-25 13:26:14 +01:00