Skip to content

tasks status turned to queued for 1 second before turned into success. #8349

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
karajan1001 opened this issue Sep 23, 2022 · 0 comments · Fixed by #8369
Closed

tasks status turned to queued for 1 second before turned into success. #8349

karajan1001 opened this issue Sep 23, 2022 · 0 comments · Fixed by #8369
Assignees
@karajan1001
Labels
A: experiments Related to dvc exp

Comments

@karajan1001
Copy link
Contributor

Originally posted by @karajan1001 in #8158 (comment)
@karajan1001 karajan1001 self-assigned this Sep 23, 2022
karajan1001 added a commit to karajan1001/dvc that referenced this issue Sep 27, 2022
@karajan1001
Use celery status as the exp show status
4f4a91e 
fix: iterative#8349
`tasks status turned to queued for 1 second before turned into success.`
is because in previous the status is using the output of
`get_running_exps` in `repo.expereiments` and when entering the
collect result progress, the `get_running_exps` will mark the tasks to
be not running because the `info.result` is not None. Here we use the
output of the celery queue as the universal standard for the tasks
status.

1. Use celery status as the exp show status
@karajan1001 karajan1001 mentioned this issue Sep 27, 2022
Merged
2 tasks
@karajan1001 karajan1001 added this to DVC Sep 27, 2022
@karajan1001 karajan1001 moved this from Backlog to In Progress in DVC Sep 27, 2022
@karajan1001 karajan1001 moved this to Backlog in DVC Sep 27, 2022
karajan1001 added a commit to karajan1001/dvc that referenced this issue Oct 7, 2022
@karajan1001
Use celery status as the exp show status
34361bb 
fix: iterative#8349
`tasks status turned to queued for 1 second before turned into success.`
is because in previous the status is using the output of
`get_running_exps` in `repo.expereiments` and when entering the
collect result progress, the `get_running_exps` will mark the tasks to
be not running because the `info.result` is not None. Here we use the
output of the celery queue as the universal standard for the tasks
status.

1. Use celery status as the exp show status
karajan1001 added a commit to karajan1001/dvc that referenced this issue Oct 11, 2022
@karajan1001
Use celery status as the exp show status
6b0ce94 
fix: iterative#8349
`tasks status turned to queued for 1 second before turned into success.`
is because in previous the status is using the output of
`get_running_exps` in `repo.expereiments` and when entering the
collect result progress, the `get_running_exps` will mark the tasks to
be not running because the `info.result` is not None. Here we use the
output of the celery queue as the universal standard for the tasks
status.

1. Use celery status as the exp show status
@karajan1001 karajan1001 mentioned this issue Oct 11, 2022
Merged
2 tasks
karajan1001 added a commit to karajan1001/dvc that referenced this issue Oct 11, 2022
@karajan1001
Use celery status as the exp show status
7c64a46 
fix: iterative#8349
`tasks status turned to queued for 1 second before turned into success.`
is because in previous the status is using the output of
`get_running_exps` in `repo.expereiments` and when entering the
collect result progress, the `get_running_exps` will mark the tasks to
be not running because the `info.result` is not None. Here we use the
output of the celery queue as the universal standard for the tasks
status.

1. Use celery status as the exp show status
karajan1001 added a commit to karajan1001/dvc that referenced this issue Oct 11, 2022
@karajan1001
Use celery status as the exp show status
0ca9e30 
fix: iterative#8349
`tasks status turned to queued for 1 second before turned into success.`
is because in previous the status is using the output of
`get_running_exps` in `repo.expereiments` and when entering the
collect result progress, the `get_running_exps` will mark the tasks to
be not running because the `info.result` is not None. Here we use the
output of the celery queue as the universal standard for the tasks
status.

1. Use celery status as the exp show status
karajan1001 added a commit to karajan1001/dvc that referenced this issue Oct 11, 2022
@karajan1001
Use celery status as the exp show status
d5ab506 
fix: iterative#8349
`tasks status turned to queued for 1 second before turned into success.`
is because in previous the status is using the output of
`get_running_exps` in `repo.expereiments` and when entering the
collect result progress, the `get_running_exps` will mark the tasks to
be not running because the `info.result` is not None. Here we use the
output of the celery queue as the universal standard for the tasks
status.

1. Use celery status as the exp show status
@karajan1001 karajan1001 moved this from In Progress to Review In Progress in DVC Oct 11, 2022
karajan1001 added a commit to karajan1001/dvc that referenced this issue Oct 11, 2022
@karajan1001
Use celery status as the exp show status
6b501da 
fix: iterative#8349
`tasks status turned to queued for 1 second before turned into success.`
is because in previous the status is using the output of
`get_running_exps` in `repo.expereiments` and when entering the
collect result progress, the `get_running_exps` will mark the tasks to
be not running because the `info.result` is not None. Here we use the
output of the celery queue as the universal standard for the tasks
status.

1. Use celery status as the exp show status
karajan1001 added a commit to karajan1001/dvc that referenced this issue Oct 14, 2022
@karajan1001
Use celery status as the exp show status
b072451 
fix: iterative#8349
`tasks status turned to queued for 1 second before turned into success.`
is because in previous the status is using the output of
`get_running_exps` in `repo.expereiments` and when entering the
collect result progress, the `get_running_exps` will mark the tasks to
be not running because the `info.result` is not None. Here we use the
output of the celery queue as the universal standard for the tasks
status.

1. Use celery status as the exp show status
karajan1001 added a commit to karajan1001/dvc that referenced this issue Oct 24, 2022
@karajan1001
Use celery status as the exp show status
de93781 
fix: iterative#8349
`tasks status turned to queued for 1 second before turned into success.`
is because in previous the status is using the output of
`get_running_exps` in `repo.expereiments` and when entering the
collect result progress, the `get_running_exps` will mark the tasks to
be not running because the `info.result` is not None. Here we use the
output of the celery queue as the universal standard for the tasks
status.

1. Use celery status as the exp show status
karajan1001 added a commit that referenced this issue Oct 24, 2022
@karajan1001
Use celery status as the exp show status
ed2ccaf 
fix: #8349
`tasks status turned to queued for 1 second before turned into success.`
is because in previous the status is using the output of
`get_running_exps` in `repo.expereiments` and when entering the
collect result progress, the `get_running_exps` will mark the tasks to
be not running because the `info.result` is not None. Here we use the
output of the celery queue as the universal standard for the tasks
status.

1. Use celery status as the exp show status
Repository owner moved this from Review In Progress to Done in DVC Oct 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@karajan1001 karajan1001

Labels
A: experiments Related to dvc exp
Projects
DVC
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use celery status as the exp show status karajan1001/dvc
1 participant
@karajan1001