[Ci-reports] Problems...

[Anttila Janne]

Reason QTQAINFRA-509.

But this time it was partly my own fault. I was still on my computer at home when I saw that build 921 failed. And then I also saw that someone was staging changes to 4.8 without my changes. So I logged into gerrit and unstaged one such change I6ffa96ac9cda0701c99f839804f400a167fcf9a7 and added comment that there is no sense to stage only that one, because it is doomed to fail. (If I would have had approval rights I would have just re-staged my changes with one additional fix instead of unstaging I6ffa96ac9cda0701c99f839804f400a167fcf9a7)

This wasn't wise move since it seems that 'un-stage' and or APIs used by integrator are not atomic. I.e. 4.8 CI build still started with un-staged change (And with this one https://codereview.qt-project.org/37843). If 4.8 CI would not be suspended yet, I think it would be safe to just change status of I6ffa96ac9cda0701c99f839804f400a167fcf9a7 with gerrit gsql back to integrating. AFAIK: This could be done as follows:

ssh -p 29418 codereview.qt-project.org gerrit gsql update changes set status='i' where  change_key='I6ffa96ac9cda0701c99f839804f400a167fcf9a7'and dest_project_name='qt/qt' and dest_branch_name='refs/heads/4.8';

Changing status back to integrating should have just made integrator to add build "Build fail" comment to that unstaged change also. But because 4.8 CI got already suspended for investigation, we need to clean-up INTEGRATING status from https://codereview.qt-project.org/37843 and reset the Qt_4.8_Integration CI project state and restart the integrator. 

Because I don't have access to all needed pieces from home, we will do that on Monday morning together with Samuli.

--
Janne

________________________________________
Lähettäjä: ci-reports-bounces+janne.anttila=digia.com at qt-project.org [ci-reports-bounces+janne.anttila=digia.com at qt-project.org] käyttäjän Qt Continuous Integration System [ci-noreply at qt-project.org] puolesta
Lähetetty: 28. lokakuuta 2012 9:46
Vastaanottaja: ci-reports at qt-project.org
Aihe: [Ci-reports] Problems...

Some problems occurred recently...

  2012-10-28T08:44:06Z: [Qt_4.8_Integration error] command [ssh] [-oBatchMode=yes] [-p] [29418] [codereview.qt-project.org] [gerrit] [staging-approve] [--branch] [4.8] [--build-id] [refs/builds/4.8_1351378739] [--project] [qt/qt] [--result] [fail] [--message] [-] exited with status 256 at /usr/lib/perl5/Coro/AnyEvent.pm line 362.

  stderr:
  Change not in INTEGRATING state (I6ffa96ac9cda0701c99f839804f400a167fcf9a7)
  Change not in INTEGRATING state (I6ffa96ac9cda0701c99f839804f400a167fcf9a7)
  Change not in INTEGRATING state (I6ffa96ac9cda0701c99f839804f400a167fcf9a7)
  Change not in INTEGRATING state (I6ffa96ac9cda0701c99f839804f400a167fcf9a7)
  Change not in INTEGRATING state (I6ffa96ac9cda0701c99f839804f400a167fcf9a7)
  Change not in INTEGRATING state (I6ffa96ac9cda0701c99f839804f400a167fcf9a7)
  , occurred repeatedly.
  2012-10-28T08:44:06Z: [Qt_4.8_Integration error] Suspending for investigation; to resume: kill -USR2 23238

_______________________________________________
Ci-reports mailing list
Ci-reports at qt-project.org
http://lists.qt-project.org/mailman/listinfo/ci-reports