We had 2 commits blocking the CI: https://codereview.qt-project.org/#change,49413 https://codereview.qt-project.org/#change,48613
They both had duplicate IDs with already merged commits. These errors appeared after we abandoned the first one, but didn't yet know about the second one. Both are now Abandoned and the CI should be unlocked again. Regards, -Tony > -----Original Message----- > From: [email protected] [mailto:ci- > [email protected]] On Behalf Of Qt > Continuous Integration System > Sent: 28. toukokuuta 2013 12:14 > To: [email protected] > Subject: [Ci-reports] Problems... > > Some problems occurred recently... > > 2013-05-28T09:12:16Z: [QtDeclarative_dev_Integration error] command [ssh] > [-oBatchMode=yes] [-p] [29418] [codereview.qt-project.org] [gerrit] [staging- > approve] [--branch] [dev] [--build-id] [refs/builds/dev_1369565782] > [--project] > [qt/qtdeclarative] [--result] [fail] [--message] [-] exited with status 256 at > /usr/lib/perl5/Coro/AnyEvent.pm line 362. > > stderr: > Change not in INTEGRATING state > (Ia6ca1046fc2162a13be5c26cbf5d2b698ffa2367) > Change not in INTEGRATING state > (Ia6ca1046fc2162a13be5c26cbf5d2b698ffa2367) > Change not in INTEGRATING state > (Ia6ca1046fc2162a13be5c26cbf5d2b698ffa2367) > Change not in INTEGRATING state > (Ia6ca1046fc2162a13be5c26cbf5d2b698ffa2367) > Change not in INTEGRATING state > (Ia6ca1046fc2162a13be5c26cbf5d2b698ffa2367) > Change not in INTEGRATING state > (Ia6ca1046fc2162a13be5c26cbf5d2b698ffa2367) > , retry in 32 seconds > > _______________________________________________ > Ci-reports mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/ci-reports _______________________________________________ Ci-reports mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/ci-reports
