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.

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

Incorrect reporting for test jobs with same identifier but different package name #2707

Open
lbarcziova opened this issue Feb 7, 2025 · 0 comments
Open

Incorrect reporting for test jobs with same identifier but different package name #2707

lbarcziova opened this issue Feb 7, 2025 · 0 comments
Labels
area/testing-farm Related to Testing Farm integration. complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/low This issue impacts only a few users. kind/bug Something isn't working. workaround-exists There is an existing workaround that can be used in the meantime of implementing the issue.

Comments

@lbarcziova
Copy link
Member

lbarcziova commented Feb 7, 2025 •
edited
Loading

When there are 2 test jobs configured with the same identifier (and probably also no identifier), but different package_name, reporting can be incorrect and lead to a check being stuck in pending state, even when the DB (=>dashboard) has the correct (completed) state. This was reported by @lsm5 recently. We should probably implement a pre-check similar to this:

packit-service/packit_service/worker/checker/copr.py

Line 81 in bcaa612

class IsPackageMatchingJobView(Checker, GetCoprSRPMBuildMixin):

@lbarcziova lbarcziova added kind/bug Something isn't working. workaround-exists There is an existing workaround that can be used in the meantime of implementing the issue. labels Feb 7, 2025
@lbarcziova lbarcziova added the complexity/single-task Regular task, should be done within days. label Feb 7, 2025
@lbarcziova lbarcziova added the area/testing-farm Related to Testing Farm integration. label Feb 7, 2025
@lachmanfrantisek lachmanfrantisek moved this from new to backlog in Packit Kanban Board Feb 10, 2025
@lachmanfrantisek lachmanfrantisek added impact/low This issue impacts only a few users. gain/low This doesn't bring that much value to users. labels Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/testing-farm Related to Testing Farm integration. complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/low This issue impacts only a few users. kind/bug Something isn't working. workaround-exists There is an existing workaround that can be used in the meantime of implementing the issue.
Projects
Packit Kanban Board
Status: backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lachmanfrantisek @lbarcziova