|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
the reason it is happening is because the iterator is working in descending order. when it does a query with 2 dates it first tests the last build run. So say it is build 200 that ran on the 10th. When the queries are coming in for each day like 1st 2nd 3rd etc. it first test to see if build that was last ran ran on these days.
for example say the query day is 2nd it will check if build 200 was on that day. since it ran on 10th it will not satisfy the requirements. so since the first build did not satisfy the requirements the rest are not checked.
Reason it only comes one day is because when the day query reaches the 10th it checks if build 200 was run on that day. since it satisfies the requirement build 200 is add to the graph. build 199 is tested again day 10. it is satisfes the requirement so add to the graph. Continue on say until build 190 which was run on the 9th does the satisfies the requirement so that is not added to the graph and the filtering then finishes. even though there is 189 builds to check but if 190 failed the date then the rest would since they are in order of date from oldest to newest.