We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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:
Here the result of the last build is reported as ok, but the state is reported as failing.
The text was updated successfully, but these errors were encountered:
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.
Sorry, something went wrong.
No branches or pull requests
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:

Here the result of the last build is reported as ok, but the state is reported as failing.

The text was updated successfully, but these errors were encountered: