Check service: Counters saved to database are always 0 #795
Labels
Comments
Zlopez
added a commit
to Zlopez/anitya
that referenced
this issue
Jul 16, 2019
Statistics were saved to database before the actual check was finished. This commit is adding wait for every thread executed in the pool. Fixes fedora-infra#795 Signed-off-by: Michal Konečný <[email protected]>
Zlopez
added a commit
to Zlopez/anitya
that referenced
this issue
Jul 16, 2019
Statistics were saved to database before the actual check was finished. This commit is adding wait for every thread executed in the pool. Fixes fedora-infra#795 Signed-off-by: Michal Konečný <[email protected]>
Zlopez
added a commit
that referenced
this issue
Jul 16, 2019
Statistics were saved to database before the actual check was finished. This commit is adding wait for every thread executed in the pool. Fixes #795 Signed-off-by: Michal Konečný <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With new version deployed on staging which contains new service for checking, I noticed that the
runstable always contains 0 on counters.This probably means, that insert to db is done before the projects are actually checked. We will probably need some wait for the thread pool to solve this issue.
The text was updated successfully, but these errors were encountered: