Account for unseen constraint combinations.
Don't force jobs to wait for constraint combinations that haven't been seen in the recent past. By default, if a set of constraints have not been seen together in the past 3 days, then assume they won't be satisfied together and don't wait for those constraints to be met in order to run a job. Other constraint combinations may still be valid, so the job may be forced to wait for those. Bug: 236261941 Bug: 299329948 Bug: 299346198 Test: atest CtsJobSchedulerTestCases:FlexibilityConstraintTest Test: atest FrameworksMockingServicesTests:ConnectivityControllerTest Test: atest FrameworksMockingServicesTests:FlexibilityControllerTest Change-Id: I8f68b76afa2cc68e062f7ce09477aafb237dc6f1
Loading
Please register or sign in to comment