Skip to content

epel9-next branch PRs never start tests, only scrathcbuilds #3064

@hroncok

Description

@hroncok

Description

In https://src.fedoraproject.org/rpms/python3-rpm/pull-request/33 the Packit - scratch build - epel9-next [2778594] job completed successfully, but other jobs (namely Packit - custom - epel9-next [2778594]) are stuck in pending state seemingly forever.

Image

Probably, this was omitted somewhere as a possible PR target. The testing farm OS should be c9s with epel and epel-next enabled.

Thanks.

Importance

I think this worked before with other CIs. It is unfortaneta that it doe snot work, but the epel9-next branch is not heavily used by packagers, so not sure.

Workaround

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/fedora-ciRelated to the Fedora CI servicecomplexity/single-taskRegular task; should be done within daysgain/highBrings a lot of value to usersimpact/lowAffects only few of the userskind/bugAn unexpected problem or behavior

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions