On 02/09/2015 15:31, "Reyna, David" <[email protected]> wrote:
>Hi Belén, > >I have just one question about the backend latency, and how the backend >does the cancel. > >It appears that when you click "Cancel" the Toaster GUI immediately >transitions to show that the build is cancelled and the "Run Again" >button appears. Normally when I cancel a build on the command line it can >take several minutes for the tasks to cleanly finish up. That would mean >that if the user immediately clicks the "Run Again" button in Toaster the >backend may not be ready. > >So, how is the cancel handled? Does Toaster try the clean way to stop a >build, or does it something radical like killing the build thread? These are really good questions. The answer is I don't know. I guess some discussion is needed about the technical implementation details of this feature. If a delay is likely between clicking 'cancel' and the build being stopped, we can create a 'cancelling' state for builds in the UI. I will make sure to add that to the design document. Cheers Belén > >- David > >> -----Original Message----- >> From: [email protected] [mailto:toaster- >> [email protected]] On Behalf Of Barros Pena, Belen >> Sent: Tuesday, September 01, 2015 5:48 AM >> To: [email protected] >> Subject: [Toaster] Design - Cancelling builds >> >> We have been speaking about letting users cancel builds at any point >> during the build process. We have a Bugzilla entry for that >> >> https://bugzilla.yoctoproject.org/show_bug.cgi?id=6787 >> >> Which now has design attached to it. It should not be controversial in >>any >> way, but if you have any questions / comments, let me know. >> >> Thanks! >> >> Belén >> >> -- >> _______________________________________________ >> toaster mailing list >> [email protected] >> https://lists.yoctoproject.org/listinfo/toaster -- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
