Watchdog leaving active processes around in testing #60
Labels
No labels
area/api
area/content_model
area/framework
area/infrastructure
area/io
area/presentation
area/preservation
area/rdf
area/security
area/submission
area/ui
p
critical
p
high
p
low
p
medium
s
blocked
s
done
s
progress
s
testing
s
wontfix
t
bug
t
documentation
t
enhancement
t
feature
t
test
p
critical
p
high
p
low
p
normal
t
bug
t
documentation
t
enhancement
t
feature
t
test
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ktx/pocket_archive#60
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The watchdog test leaves stray processes after running. PID files are not being cleared.
This may be related to the watchdog process itself or to the way the tests are written.
Moving out of the RC milestone, as the only time when this happens is during the automated tests on a development machine. Normally the watchdog starts and shuts down correctly. CI processes tear down the whole VM so there is no need to kill the stray processes.
A better solution to high-level testing of watchdog, HTTP server, and CLI would be to set up integration tests in a different framework.