Amphetamines are formulated to correct for certain brain chemical imbalances and may be used to treat ADD, ADHD, narcolepsy and obesity. Looks like all the right assertions are active.Amphetamines belong to a class of drugs known as prescription stimulants and are used to treat a handful of medical conditions. Pid 52(powerd): 00:01:32 NetworkClientActive named: "" Pid 378(caffeinate): 03:19:21 UserIsActive named: "caffeinate command-line tool" Pid 378(caffeinate): 03:19:21 PreventSystemSleep named: "caffeinate command-line tool" Pid 378(caffeinate): 03:19:21 PreventUserIdleDisplaySleep named: "caffeinate command-line tool" Timeout will fire in 31524038 secs Action=TimeoutActionRelease Pid 378(caffeinate): 03:19:21 PreventUserIdleSystemSleep named: "caffeinate command-line tool"ĭetails: caffeinate asserting on behalf of 'sh' (pid 377) 19:34:27 -0800 : Showing all currently held IOKit power assertions Rbb-osx1013-3:~ buildbot$ pmset -g assertionslog Sure enough, it's in power state 1, which I guess is sleep. Rbb-osx1013-3:~ buildbot$ ioreg -n IODisplayWrangler | grep -i IOPowerManagement While the hang is in progress, I ssh into the 10.13 box from outside, and do: Symptom: test that uses the display hangs. My machines is on a beta channel and has osx 10.13.1 beta on tap, maybe I'll let that load Let me know if you want me to run any other tests. None of the three systems hung this time, no thanks to caffeinate. Next, I went into Energy Saver and set all three machines to never sleep the display or Result: it woke up and finished the build. Result: the remaining machine hung during the build. I started a build again on the remaining machine, again not fiddling with it at all. Result: 1 of the 2 machines hung during the build.
I noted that the screen slept on both about 1 minute after boot and autologin. On the two that didn't hang, I started a build again, this time not fiddling with them at all first. Result: 1 of the three machines hung during the build. On all three, I then logged in via ssh and ran pmset -g assertionslog and watched,įiddled with keyboard and mouse a bit, waited to see if their screens would blank (hmm, System Settings / Energy Saver shows the display one two was set to sleep after 2 minutes), and then triggered an 8 minute build that hung today before the reset. When they boot, they start the test runner, which just sits there waiting for jobs. Walk over and wiggled the mouse / pressed the shift key, and voila, the test woke up, and pmset continued, sayingĮssentially a very cold boot, so for each of the 3 machines, I shut down, pulled power cord, pressed power button to get it to drain the caps, waited 2 minutes, plugged in power cord, and turned back on. Time Action Type PID(Causing PID) ID Name Showing assertion changes(Press Ctrl-T to log all currently held assertions): Pid 52(powerd): 00:06:01 NetworkClientActive named: "" Pid 366(caffeinate): 03:16:41 UserIsActive named: "caffeinate command-line tool" Pid 366(caffeinate): 03:16:41 PreventSystemSleep named: "caffeinate command-line tool" Timeout will fire in 60198 secs Action=TimeoutActionRelease
Localized=THE CAFFEINATE TOOL IS PREVENTING SLEEP. Pid 366(caffeinate): 03:16:41 PreventUserIdleSystemSleep named: "caffeinate command-line tool"ĭetails: caffeinate asserting on behalf of 'sh' (pid 365)
15:57:23 -0800 : Showing all currently held IOKit power assertions
0 kommentar(er)
