Got another report of my commit breaking CI. I don't believe report correctly nailed down the commit. Bisection should be fixed. """ Subject: BROKEN: repository became broken! To: <gentoo-automated-testing@lists.gentoo.org> CC: <slyfox@gentoo.org> Content-Type: text/plain; charset=utf8 Message-Id: <20180522225653.8F3ED3980310@drfinkelstein.bonedaddy.net> Date: Tue, 22 May 2018 18:56:53 -0400 (EDT) From: mgorny@bonedaddy.net Looks like someone just broke Gentoo! New issues (1): https://qa-reports.gentoo.org/output/gentoo-ci/7a5b05058/output.html#sys-cluster/openmpi Introduced by commits: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4bbb9c39f09f Changes since last check: https://gitweb.gentoo.org/repo/gentoo.git/log/?qt=range&q=0607474fe104..4bbb9c39f09f """
The code is at [1]. Any help would be appreciated. [1]:https://github.com/mgorny/repo-mirror-ci
To start debugging it would be nice to have exact command arguments being ran on that particular false positive if it's easily extractable from logs.
Sadly, logs are only stored if the script crashes. I should probably add separate logs for bisecting but I don't currently have time to dive into that code.
Another miss today: """ Looks like someone just broke Gentoo! New issues (21): https://qa-reports.gentoo.org/output/gentoo-ci/d7c1196/output.html#dev-ruby/ruby-atk https://qa-reports.gentoo.org/output/gentoo-ci/d7c1196/output.html#dev-ruby/ruby-cairo-gobject ... (other ruby stuff) Introduced by commits: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e7d904a3821 Changes since last check: https://gitweb.gentoo.org/repo/gentoo.git/log/?qt=range&q=3cab0379873..e7d904a3821 """ Looks like off-by-one error. Or the sorting is confused by by-date/by-parent order mismatch.
