linaro-release team mailing list archive

[Alexander Sack <asac@xxxxxxxxxx>]

On Tue, Sep 6, 2011 at 4:42 PM, James Westby <jw+debian@xxxxxxxxxxxxxxx>wrote:

> On Tue, 06 Sep 2011 13:24:49 -0000, Alexander Sack <asac@xxxxxxxxxx>
> wrote:
> > On Tue, Sep 6, 2011 at 2:24 PM, Frans Gifford
> > <frans.gifford@xxxxxxxxxx>wrote:
> >
> > > Feel free to mark as invalid if you think this is the correct
> behaviour.
> > >
> > >
> > maybe a third state: SUCCESSWITHPROBLEMS would be another option? Not
> sure
> > how easy that is to do on jenkins. I guess this stuff ultimately needs to
> be
> > visualized on a lava dashboard with info like: build, lava submission,
> boot,
> > tests etc. in one shot.
>
> It's quite hard to visualise problems with submitting to LAVA on LAVA
> itself :-)
>
>
:) ... thats true.

OTOH, LAVA is a high priority service of Linaro and I hope we can assume
that we don't get long term downtime there ... on build server having a
queuing mechanism etc. to submit and retry submitting jobs and results feels
worth investigating to make things more robust though.


> Thanks,
>
> James
>
> --
> You received this bug notification because you are a member of linaro-
> infrastructure-drivers, which is the registrant for Linaro Android Build
> Tools.
> https://bugs.launchpad.net/bugs/842452
>
> Title:
>  Failure to submit build to lava results in overall build failure
>
> Status in Linaro Android Build Tools:
>  New
>
> Bug description:
>  For example in https://android-build.linaro.org/builds/~linaro-
>  android/panda/#build=270
>
>  Failure to connect to LAVA is annoying, but shouldn't cause the build
>  to be marked as failed.
>
>  Traceback (most recent call last):
>    File
> "/mnt/jenkins/workspace/linaro-android_panda/build-tools/build-scripts/post-build-lava.py",
> line 121, in <module>
>      main()
>    File
> "/mnt/jenkins/workspace/linaro-android_panda/build-tools/build-scripts/post-build-lava.py",
> line 98, in main
>      lava_job_id = server.scheduler.submit_job(config)
>    File "/usr/lib/python2.7/xmlrpclib.py", line 1224, in __call__
>      return self.__send(self.__name, args)
>    File "/usr/lib/python2.7/xmlrpclib.py", line 1575, in __request
>      verbose=self.__verbose
>    File "/usr/lib/python2.7/xmlrpclib.py", line 1264, in request
>      return self.single_request(host, handler, request_body, verbose)
>    File "/usr/lib/python2.7/xmlrpclib.py", line 1292, in single_request
>      self.send_content(h, request_body)
>    File "/usr/lib/python2.7/xmlrpclib.py", line 1439, in send_content
>      connection.endheaders(request_body)
>    File "/usr/lib/python2.7/httplib.py", line 951, in endheaders
>      self._send_output(message_body)
>    File "/usr/lib/python2.7/httplib.py", line 811, in _send_output
>      self.send(msg)
>    File "/usr/lib/python2.7/httplib.py", line 773, in send
>      self.connect()
>    File "/usr/lib/python2.7/httplib.py", line 1154, in connect
>      self.timeout, self.source_address)
>    File "/usr/lib/python2.7/socket.py", line 571, in create_connection
>      raise err
>  socket.error: [Errno 110] Connection timed out
>  Build step 'Execute shell' marked build as failure
>  Archiving artifacts
>  Finished: FAILURE
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/linaro-android-build-tools/+bug/842452/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net/~linaro-release
> Post to     : linaro-release@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~linaro-release
> More help   : https://help.launchpad.net/ListHelp
>



-- 

 - Alexander