All of lore.kernel.org
 help / color / mirror / Atom feed
From: sujith h <sujith.h@gmail.com>
To: "Barros Pena, Belen" <belen.barros.pena@intel.com>
Cc: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: Build cancellation from toaster
Date: Mon, 18 Jan 2016 21:42:21 +0530	[thread overview]
Message-ID: <CADyYWL=c3QO5zkOOjUuaiswwO4FVTGEmqGnF3_TjXH4=TVDbNw@mail.gmail.com> (raw)
In-Reply-To: <D2C1AC14.703C1%belen.barros.pena@intel.com>

[-- Attachment #1: Type: text/plain, Size: 5172 bytes --]

On Mon, Jan 18, 2016 at 1:13 AM, Barros Pena, Belen <
belen.barros.pena@intel.com> wrote:

>
>
> On 13/01/2016 16:47, "sujith h" <sujith.h@gmail.com> wrote:
>
> >
> >I have updated another patch set with which I have verified with:
> >
> >a) cancellation of a normal build
> >
> >b) run again and cancel the build
> >
> >c) stop toaster + start toaster + run again   and cancel the build
> >
> >
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sujith/toast
> >er-build-cancel12
>
> Sorry for the delay in looking into this. Cancellation seems to be working
> well for me for any builds I start from Toaster. However, it doesn't seem
> to work for builds I start from the command line and I track through
> Toaster. For those builds, a 'cancel' button appears, but when I click it,
> nothing happens: the build proceeds until it completes.
>
> I am not even sure if the 'cancel' functionality can work for builds
> started from the command line, although it would be great if it did. If it
> is not possible to make it work, then the cancel button should not display
> for those builds. We can provide a message instead, as we do in the case
> of the 'run again' button, explaining that builds started from the command
> line can only be cancelled from the command line.
>

Somehow when i try to use the same logic to cancel the build triggered from
command line ( with small modification in the code though), I am getting
error in the toaster_web.log as:

ProtocolError: <ProtocolError for 0.0.0.0:42952/: 503 Service Unavailable>

Not able to understand why it is not able to connect to the port. Because
as per my understanding when a build is triggered from toaster, we connect
to the host:port and execute the commands. The runcommand is failing badly
with the log:

2016-01-18 16:06:05,608 ERROR Internal Server Error:
/toastergui/project/1/builds/
Traceback (most recent call last):
  File
"/home/sujith/build/poky-push/venv/lib/python2.7/site-packages/django/core/handlers/base.py",
line 132, in get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File
"/home/sujith/build/poky-push/bitbake/lib/toaster/toastergui/views.py",
line 171, in returned_wrapper
    context = view(request, *args, **kwargs)
  File
"/home/sujith/build/poky-push/bitbake/lib/toaster/toastergui/views.py",
line 2896, in projectbuilds
    bbctrl.forceShutDown()
  File
"/home/sujith/build/poky-push/bitbake/lib/toaster/bldcontrol/bbcontroller.py",
line 73, in forceShutDown
    return self._runCommand(["stateForceShutdown"])
  File
"/home/sujith/build/poky-push/bitbake/lib/toaster/bldcontrol/bbcontroller.py",
line 50, in _runCommand
    result, error = self.connection.runCommand(command)
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1240, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1599, in __request
    verbose=self.__verbose
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1280, in request
    return self.single_request(host, handler, request_body, verbose)
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1328, in single_request
    response.msg,
ProtocolError: <ProtocolError for 0.0.0.0:42952/: 503 Service Unavailable>
Internal Server Error: /toastergui/project/1/builds/
Traceback (most recent call last):
  File
"/home/sujith/build/poky-push/venv/lib/python2.7/site-packages/django/core/handlers/base.py",
line 132, in get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File
"/home/sujith/build/poky-push/bitbake/lib/toaster/toastergui/views.py",
line 171, in returned_wrapper
    context = view(request, *args, **kwargs)
  File
"/home/sujith/build/poky-push/bitbake/lib/toaster/toastergui/views.py",
line 2896, in projectbuilds
    bbctrl.forceShutDown()
  File
"/home/sujith/build/poky-push/bitbake/lib/toaster/bldcontrol/bbcontroller.py",
line 73, in forceShutDown
    return self._runCommand(["stateForceShutdown"])
  File
"/home/sujith/build/poky-push/bitbake/lib/toaster/bldcontrol/bbcontroller.py",
line 50, in _runCommand
    result, error = self.connection.runCommand(command)
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1240, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1599, in __request
    verbose=self.__verbose
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1280, in request
    return self.single_request(host, handler, request_body, verbose)
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1328, in single_request
    response.msg,
ProtocolError: <ProtocolError for 0.0.0.0:42952/: 503 Service Unavailable>
[18/Jan/2016 16:06:05] "POST /toastergui/project/1/builds/ HTTP/1.1" 500
13414


Any helping hand would be appreciated. More over I would also like to know
if we can pass commands to builds triggered from command line?

Thanks,
Sujith H

-- 
സുജിത് ഹരിദാസന്
Bangalore
<Project>Contributor to KDE project
http://fci.wikia.com/wiki/Anti-DRM-Campaign
<Blog> http://sujithh.info

[-- Attachment #2: Type: text/html, Size: 6563 bytes --]

  reply	other threads:[~2016-01-18 16:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 16:56 Build cancellation from toaster sujith h
2015-12-18 12:24 ` Michael Wood
2015-12-18 13:46 ` Ed Bartosh
2015-12-19 15:27   ` sujith h
2015-12-21  8:07     ` sujith h
2015-12-21 13:12       ` sujith h
2015-12-22 10:49         ` sujith h
2016-01-04 13:16           ` sujith h
2016-01-05 13:44             ` Barros Pena, Belen
2016-01-05 14:13               ` sujith h
2016-01-06 13:38                 ` sujith h
2016-01-09 16:53                   ` sujith h
2016-01-11 11:25                     ` Barros Pena, Belen
2016-01-12 10:34                       ` Barros Pena, Belen
2016-01-13 16:47                         ` sujith h
2016-01-17 19:43                           ` Barros Pena, Belen
2016-01-18 16:12                             ` sujith h [this message]
2016-01-20 16:56                               ` Brian Avery
2016-01-26 14:22                                 ` sujith h
2016-01-27 16:20                                   ` sujith h
2016-02-01 15:35                                     ` Barros Pena, Belen
2016-02-03 13:38                                       ` sujith h
2016-02-09 13:40                                         ` sujith h
2016-02-12 11:04                                           ` Barros Pena, Belen
2016-02-19 23:11                                           ` Michael Wood
2016-02-22  6:23                                             ` sujith h
2016-01-21 15:16                               ` [Toaster] " sujith h

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADyYWL=c3QO5zkOOjUuaiswwO4FVTGEmqGnF3_TjXH4=TVDbNw@mail.gmail.com' \
    --to=sujith.h@gmail.com \
    --cc=belen.barros.pena@intel.com \
    --cc=toaster@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.