Skip to content

Reporting errors on GitLab #2325

Closed
@mfocko

Description

@mfocko

What happened? What is the problem?

Packit failed to notify user via comment about the failure on GitLab when there's no access to the repository to set the commit statuses.

What did you expect to happen?

Fallback to the comment notification.

Example URL(s)

MR: https://gitlab.com/efedin/compose-tests/-/merge_requests/1
Comment: https://gitlab.com/efedin/compose-tests/-/merge_requests/1#note_1750278441

Steps to reproduce

1. MR got triggered via the comment `/packit test`
2. Logic part on our side deduced there are no tests
3. Reports the error via commit (visible in the logs):
   https://github.com/packit/packit-service/blob/7337498d73eed935e6196696a518d3ea69ef4ad7/packit_service/worker/helpers/testing_farm.py#L935-L942
4. Since Packit is not present in the repo, it fails.

What is the impacted category (job)?

Testing Farm tests

Workaround

  • There is an existing workaround that can be used until this issue is fixed.

Participation

  • I am willing to submit a pull request for this issue. (Packit team is happy to help!)

Metadata

Metadata

Assignees

Labels

area/gitlabRelated to GitLab implementation.area/testing-farmRelated to Testing Farm integration.complexity/single-taskRegular task, should be done within days.gain/highThis brings a lot of value to (not strictly a lot of) users.impact/lowThis issue impacts only a few users.kind/bugSomething isn't working.

Type

No type

Projects

  • Status

    done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions