From: "Barros Pena, Belen" <belen.barros.pena@intel.com>
To: sujith h <sujith.h@gmail.com>
Cc: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: Build cancellation from toaster
Date: Sun, 17 Jan 2016 19:43:00 +0000 [thread overview]
Message-ID: <D2C1AC14.703C1%belen.barros.pena@intel.com> (raw)
In-Reply-To: <CADyYWLmpJE3y63f_-7QJAWhwxjq0gRo7QnfzGxW1-Ou_ddoqNA@mail.gmail.com>
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.
Thanks!
Belén
next prev parent reply other threads:[~2016-01-17 19:43 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 [this message]
2016-01-18 16:12 ` sujith h
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=D2C1AC14.703C1%belen.barros.pena@intel.com \
--to=belen.barros.pena@intel.com \
--cc=sujith.h@gmail.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.