You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildstream.apache.org by GitBox <gi...@apache.org> on 2022/11/08 07:17:39 UTC

[GitHub] [buildstream] gtristan commented on issue #1787: BuildStream doesn't quit on ctrl+c then `quit`

gtristan commented on issue #1787:
URL: https://github.com/apache/buildstream/issues/1787#issuecomment-1306740497

   > BuildStream to finish building the few packages it was building, then stop
   
   This is no longer the correct expectation, and indeed will be the result of #1727 which addresses #534 (Failed builds not pushing artifacts on quit). Essentially without this, the default/majority behavior makes sharing of failed build artifacts is useless because failed builds do not get pushed.
   
   As of #1727, the expectation is that *imperative* tasks and *pre-imperative* tasks will no longer be queued after quitting, while *post-imperative* tasks will continue to be queued and processed. This only really applies to the *build* command, and the behavior will be that no further elements will be *built*, but any already built elements will continue to be *pushed*.
   
   Normally I would leave this open and wait for further info, but since this is casting doubt on the already delayed 2.0 release I'll close this and ask that if you find that *pre-imperative* tasks continue to be processed/queued after quitting, to please reopen this.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org