[lldb-dev] A commit between r227595 and r228444 broke tests on FreeBSD

[Ed Maste]

On 13 February 2015 at 20:22, Zachary Turner <zturner at google.com> wrote:
> Is it possible to bisect the revision range?

I've been trying, but discovered that the issue only shows up when the
full test suite is run (i.e., ninja check-lldb) -- which makes for a
very slow process. If I run python dotest.py directly the tests do not
timeout. That's a big clue itself, and I'm starting to suspect it may
be a problem in FreeBSD that's somehow triggered by a change in the
range. The hunt continues...