summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/ui/depexp.py
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2013-09-13 17:31:54 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-09-14 08:20:38 +0100
commit7663a520612203db35145609a8ff3fd80de4149a (patch)
tree7b26dd111b828926eaccb36144548e900069e080 /bitbake/lib/bb/ui/depexp.py
parent2174a51ee8bcfd3a14e0a889e9beccc0b32e406b (diff)
downloadpoky-7663a520612203db35145609a8ff3fd80de4149a.tar.gz
bitbake: cooker: Rename confusing 'stop' state to 'forceshutdown'
The shutdown state causes the server to finish what its doing, stop was them meant to completely stop it. It doesn't mean the server is stopped though. Renaming the current stop event for forceshutdown gives more meaning to what it actually does. The stopped namespace then becomes available to indicate a completely stopped server. (Bitbake rev: 12e9d33bfae5294e3870dfd1202f63383ad05e92) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/ui/depexp.py')
-rw-r--r--bitbake/lib/bb/ui/depexp.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/bitbake/lib/bb/ui/depexp.py b/bitbake/lib/bb/ui/depexp.py
index cbda6d5afe..0b160e2f4e 100644
--- a/bitbake/lib/bb/ui/depexp.py
+++ b/bitbake/lib/bb/ui/depexp.py
@@ -314,7 +314,7 @@ def main(server, eventHandler, params):
314 break 314 break
315 if shutdown == 1: 315 if shutdown == 1:
316 print("\nSecond Keyboard Interrupt, stopping...\n") 316 print("\nSecond Keyboard Interrupt, stopping...\n")
317 _, error = server.runCommand(["stateStop"]) 317 _, error = server.runCommand(["stateForceShutdown"])
318 if error: 318 if error:
319 print('Unable to cleanly stop: %s' % error) 319 print('Unable to cleanly stop: %s' % error)
320 if shutdown == 0: 320 if shutdown == 0: