Skip to content
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.

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

State sometimes does not match state of last build #343

Open
ellert opened this issue Jan 26, 2022 · 1 comment
Open

State sometimes does not match state of last build #343

ellert opened this issue Jan 26, 2022 · 1 comment

Comments

@ellert
Copy link

ellert commented Jan 26, 2022

The state reported for a package in a release is sometimes different from the state reported for the last build. E.g.

Here the result of the last build is reported as a failed, but the state is reported as ok:
koschei-root-rawhide

Here the result of the last build is reported as ok, but the state is reported as failing.
koschei-roort-epel7

@mizdebsk
Copy link
Member

Confirmed, there is inconsistency in database.
Package state should always be equal to state of the latest build.

For performance package state is stored in database as denormalized field, which may outdated as the following query shows:

koschei=> select count(*) from package p join build b on b.id=p.last_build_id where p.last_complete_build_state<>b.state;
 count 
-------
    25
(1 row)

The count is changing quite often (several times per minute).
This needs further investigation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants