Cro::LDAP bisect log (thanks, Blin)

cro-ldap.log

»»»»» Testing 1112988024e3be231afef5742965e5daa424e4dd
»»»»» Script output:
===SORRY!===
Missing serialize REPR function for REPR NativeRef (StrLexRef)

»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 0
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 165f918403b390897b44fee5cbf24a6fe4450b3c
»»»»» Script output:

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing bc764c2e8be2c9c6ce106fe16a6fde6eebaf0c19
»»»»» Script output:

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 1680fbec89afb7014579c49f85bcae27ec4a1326
»»»»» Script output:

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 389ebefe7f7436fbc6c57497d560113b637bab7b
»»»»» Script output:
===SORRY!===
Missing serialize REPR function for REPR NativeRef (StrLexRef)

»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 0
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 4d44bd9375335ce8278c6c9a5d893750eee59726
»»»»» Script output:

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing e274f4a26ed0323369937fc867871d644173fe54
»»»»» Script output:
===SORRY!===
Missing serialize REPR function for REPR NativeRef (StrLexRef)

»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 0
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 532d19fc4e18bc08f7660d430d1c696bcbbe4b9d
»»»»» Script output:

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 37b7ef7ce9b6c5afb18f94b2230db625da24c96a
»»»»» Script output:

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
e274f4a26ed0323369937fc867871d644173fe54 is the first new commit
commit e274f4a26ed0323369937fc867871d644173fe54
Author: Stefan Seifert <nine@detonation.org>
Date:   Sat May 4 12:46:46 2019 +0200

    Fix bogus role conflict when the same method is added under multiple names
    
    It is possible to add the same method object under different names to a class
    or role. Thus we must not rely on the method object's name but always use the
    name given to add_method when processing lists of methods.
    
    Many thanks to Xliff++ for the excellent report! Fixes GH #2873

:040000 040000 12159552e92129a9c242a66cc1b683dab4935b99 1e536274ce81c331ebcf0b2dd753dd7d3f3b4c27 M	src
:040000 040000 3d944d984e78a210be6356ad8b93c0b7d6945c0f e9e5bd718776d0737cae6e238077fa48efc3bbe6 M	tools