Fixes #38597 - Add 'Scheduled' option#989
Conversation
|
Blocked on #988 (comment) and a rebase |
27acfef to
e690124
Compare
e690124 to
6e174a0
Compare
9e1145b to
474336e
Compare
4f4c603 to
7625ac2
Compare
7625ac2 to
8b842a7
Compare
|
Rebase |
|
Also, not sure if its in the scope of this PR, but searching for |
After discussion with @adamruzicka about this. We decided to do just this "quick fix" for the scheduled option. Because the filter itself is written in some way, that does not allow us to quickly add this option without breaking things or do lot of work to get it done. So the answer is: Yes, it's out of scope of this PR |
I took a look at this issue, and it actually looks like, that it is a bug, because I don't think it should filter 'success' while all of the jobs are 'awaiting'. Or does it have some special behavior? That is also question for @kmalyjur I think the issue is here: The index skips "ALL_STATUSES", but it skips it also when there are not any finished jobs. Then there is a question what is the correct behavior:
|
You're right, it's a bug, it probably happened because I and others forgot about the scheduling option.
The first option makes more sense for me. |
8b842a7 to
3d137c3
Compare
|
After some time of investigating, I added this minimalist fix, it should be fine now. @kmalyjur 3d137c3#diff-a8d318f6a8e6229ab923d8d228378f32cabfd5c03ce9c9e6fb168a2eaa14f983R79-R83 3d137c3#diff-a8d318f6a8e6229ab923d8d228378f32cabfd5c03ce9c9e6fb168a2eaa14f983R103 |


#988 Is required for this one