-
Improvement
-
Resolution: Fixed
-
Major
-
None
DepthFirstScanner in the graphanalysis APIs works, but the API mandates that it visit the first node then the branches after (but in reverse order).
Instead we should visit the branches in order for drop-in compatibility with FlowGraphWalker
This will, incidentally, fix JENKINS-38457.
- relates to
-
JENKINS-38457 FlowGraphTable shows parallel branches out of order
-
- Resolved
-
[JENKINS-38458] Mandate consistent iteration order for DepthFirstScanner
Sam Van Oort
created issue -
Sam Van Oort
made changes -
| Assignee | New: Sam Van Oort [ svanoort ] |
| Description |
Original:
DepthFirstScanner in the graphanalysis APIs works, but the API mandates that it visit the *first* node then the branches after (but in reverse order). Instead we should visit the last first, then then others, as with ForkScanner in [ This will, incidentally, fix https://issues.jenkins-ci.org/browse/JENKINS-38381 too. |
New:
DepthFirstScanner in the graphanalysis APIs works, but the API mandates that it visit the *first* node then the branches after (but in reverse order). Instead we should visit the last first, then then others, as with ForkScanner in This will, incidentally, fix |
| Link |
New:
This issue relates to |
Sam Van Oort
made changes -
| Description |
Original:
DepthFirstScanner in the graphanalysis APIs works, but the API mandates that it visit the *first* node then the branches after (but in reverse order). Instead we should visit the last first, then then others, as with ForkScanner in This will, incidentally, fix |
New:
DepthFirstScanner in the graphanalysis APIs works, but the API mandates that it visit the *first* node then the branches after (but in reverse order). Instead we should visit the branches in order for drop-in compatibility with FlowGraphWalker This will, incidentally, fix |
Sam Van Oort
made changes -
| Description |
Original:
DepthFirstScanner in the graphanalysis APIs works, but the API mandates that it visit the *first* node then the branches after (but in reverse order). Instead we should visit the branches in order for drop-in compatibility with FlowGraphWalker This will, incidentally, fix |
New:
DepthFirstScanner in the graphanalysis APIs works, but the API mandates that it visit the *first* node then the branches after (but in reverse order). Instead we should visit the branches in order for drop-in compatibility with FlowGraphWalker This will, incidentally, fix |
Sam Van Oort
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Sam Van Oort
made changes -
| Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Sam Van Oort
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Review [ 10005 ] | New: Closed [ 6 ] |