utility: deal with a parent becoming empty/pruned with a split grandparent
When the obsolete parent of a revision being evolved becomes empty and gets pruned, it should look at the successors of the grandparent. If the grandparent was split, however, we were not handling the split properly and were still trying to find successors of the parent.
Status | Job ID | Name | Coverage | ||||||
---|---|---|---|---|---|---|---|---|---|
Test | |||||||||
passed |
#92822
|
checks-py2 |
00:01:28
|
|
|||||
passed |
#92823
|
checks-py3 |
00:01:55
|
|
|||||
passed |
#92828
|
doc |
00:00:23
|
|
|||||
manual |
#92821
allowed to fail
manual
|
pytype |
|
||||||
passed |
#92824
|
tests-py2-cext |
00:05:12
|
|
|||||
passed |
#92825
|
tests-py2-pure |
00:05:04
|
|
|||||
passed |
#92826
|
tests-py3-cext |
00:03:41
|
|
|||||
passed |
#92827
|
tests-py3-pure |
00:03:05
|
|
|||||