`dvc queue status` shows tasks as running even after system restart.
See original GitHub issueBug Report
dvc queue status
shows tasks as running instead of failed.
And tasks are not removed and their status also didn’t change even after running dvc queue stop --kill
multiple times.
I started jobs and then restarted the system.
dvc queue stop --kill --verbose
show:
Even after running it multiple times.
Reproduce
Queue and start jobs and then restart the system. Then do dvc queue status
All tasks should show status as “failed” however, some show “running” but they are not running. This didn’t update even after running dvc queue stop --kill
Issue Analytics
- State:
- Created 9 months ago
- Comments:6
Top Results From Across the Web
queue status | Data Version Control
Shows the status of queued and running experiments in the queue, as well as the status of running workers (see dvc queue start...
Read more >ALL Scheduled Tasks are triggered after a server reboot
This is most likely due to restarting Scheduled Task Hander service with tasks that have next run times of before the restart. What...
Read more >vtune-profiler-user-guide.pdf
Verify Intel® VTune™ Profiler Installation on a Linux* System.......................... ... This command makes a temporary change that is lost after reboot.
Read more >dvc Changelog - pyup.io
build(deps-dev): Bump dvc-task from 0.1.4 to 0.1.5 by dependabot in ... queue status: show final experiment name (8104) karajan1001 - exp run: Use...
Read more >IBM Tivoli Monitoring: IBM i OS Agent User's Guide
Total AUX Storage, added to the System Status attribute group. ... Messages related to the Monitoring Agent for IBM i OS while it...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, the problem is quite simple, I had already created a PR for it.
Great 😃