Overview
| Comment: | added zombie test sweep to launch:execute |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | v1.65-telemetry |
| Files: | files | file ages | folders |
| SHA1: |
071b3404c3161daf383416e569219c94 |
| User & Date: | bjbarcla on 2019-02-20 18:24:53 |
| Other Links: | branch diff | manifest | tags |
Context
|
2019-02-21
| ||
| 19:21 | attempted smartening up find-and-mark-incomplete; still not quite right check-in: 4135872b65 user: bjbarcla tags: v1.65-telemetry | |
|
2019-02-20
| ||
| 18:24 | added zombie test sweep to launch:execute check-in: 071b3404c3 user: bjbarcla tags: v1.65-telemetry | |
| 18:22 | added zombie test sweep to launch:execute check-in: 0db6a22974 user: bjbarcla tags: v1.65-telemetry | |
Changes
Modified launch.scm from [14b5655bbb] to [ffc904a8de].
| ︙ | ︙ | |||
453 454 455 456 457 458 459 | (handle-exceptions exn #f (process-signal pid-num signal/kill))) (process:get-sub-pids pid)))) ;; (debug:print-info 0 *default-log-port* "not killing process " pid " as it is not alive")))) pids) | > | | | 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 |
(handle-exceptions
exn
#f
(process-signal pid-num signal/kill)))
(process:get-sub-pids pid))))
;; (debug:print-info 0 *default-log-port* "not killing process " pid " as it is not alive"))))
pids)
;; BB: question to Matt -- does the tests:test-state-status! encompass rollup to toplevel? If not, should it?
(tests:test-set-status! run-id test-id "KILLED" "KILLED" (conc (args:get-arg "-m")" "kill-reason) #f)) ;; BB ADDED kill-reason -- confirm OK with Matt
(begin
(debug:print-error 0 *default-log-port* "Nothing to kill, pid1=" pid1 ", pid2=" pid2)
(tests:test-set-status! run-id test-id "KILLED" "FAILED TO KILL" (conc (args:get-arg "-m")" "kill-reason) #f) ;; BB ADDED kill-reason -- confirm OK with Matt
)))
(mutex-unlock! m)
;; no point in sticking around. Exit now.
(exit)))
(if (hash-table-ref/default misc-flags 'keep-going #f)
(begin
(thread-sleep! 3) ;; (+ 3 (random 6))) ;; add some jitter to the call home time to spread out the db accesses
|
| ︙ | ︙ |