Comment 1 for bug 1831643

FWIW, I've ran a git-bisect on the KiCad tree, with the following test script:

    #! /bin/sh -ex
    count=0
    for i in `seq 1 10`
    do
            git clean -fdx || exit 125
            mkdir Build || exit 125
            cd Build || exit 125
            cmake -DKICAD_SPICE=OFF -DCMAKE_BUILD_TYPE=Debug .. || exit 125
            make -j32 || count=$(($count + 1))
            cd ..
            if [ $count -ne 0 ] && [ $count -ne $i ]; then exit 1; fi
    done
    if [ $count -eq 10 ]; then exit 125; fi

Basically, this does up to 10 attempts per version, marks a version as "bad" if it got a mix of successful and failed builds, "skip" if the build always fails, and "good" if all ten builds succeed.

The result is

    There are only 'skip'ped commits left to test.
    The first bad commit could be any of:
    0617bffce0ebc2549adc05d6ed85b8166fb8e00f
    840e08fa7886814e816b2c37646da5ea6550e156
    300f5cb0821c7aca92c13c67f2df6dee88890a63
    We cannot bisect more!

My suspicion would be 0617bffce0, which turns eeschema into an OBJECT library to allow unit tests to work, but as mentioned in my mail, it's likely not the root cause, but rather just shifted the timing so we actually run into it.