Define srpm_build_deps in the packit config

[psss]

Seems we need to define the srpm_build_deps key in the packit config to enable srpm building in copr. See the following two links to learn more about the change:

• https://packit.dev/docs/configuration/#srpm_build_deps
• https://packit.dev/posts/copr-srpms/#deployment-phases

[psss]

/packit test

[psss]

@lachmanfrantisek, @jpopelka, @TomasTomecek, I'm trying to enable the srpm building in copr but ran into this:

Submit of the build failed: Cmd('git') failed due to: exit code(128) cmdline:
git fetch -v origin +refs/pull/1760/head:refs/remotes/origin/pr-changes/1760 stderr:
'fatal: couldn't find remote ref refs/pull/1760/head' 

Could this be caused by enable_net: False? Or is this something else?

[jpopelka]

@psss I can see 40 such events (from other projects) in Sentry from 4-7 pm yesterday, so there was probably some outage. Can you try again now?

[psss]

/packit test

[psss]

@jpopelka, thanks, looks good now. Trying to look at the logs, I follow the fedora-37-x86_64 job links:

• https://github.com/teemtee/tmt/pull/1760/checks?check_run_id=10085377169
• https://dashboard.packit.dev/results/testing-farm/154500
• https://dashboard.packit.dev/results/copr-builds/559612
• https://dashboard.packit.dev/results/srpm-builds/103821
• https://copr.fedorainfracloud.org/coprs/packit/teemtee-tmt-1760-internal-wow/build/5144031/

The last links brings me to packit/teemtee-tmt-1760-internal-wow, is that expected?

[jpopelka]

The last links brings me to packit/teemtee-tmt-1760-internal-wow, is that expected?

not able to answer, @lbarcziova perhaps? ^

[lachmanfrantisek]

The last links brings me to packit/teemtee-tmt-1760-internal-wow, is that expected?

@psss Yes, it's correct. The name should look like packit/{namespace}-{repository}-{PR-number} or packit/{namespace}-{repository}-{PR-number}-{identifier} if identifier is set.

It's for this job definition:

- job: tests
  trigger: pull_request
  identifier: "internal-wow"
  targets:
  - fedora-latest-stable
  use_internal_tf: True

So yes, I would say it's correct. The identifier is used in the status names as well:

[psss]

So yes, I would say it's correct. The identifier is used in the status names as well:

The thing is that the identifier is set for another job:

• fedora-37-x86_64: https://github.com/teemtee/tmt/runs/10089561526
• fedora-37-x86_64:internal-wow: https://github.com/teemtee/tmt/runs/10089659456

The links lead to:

• https://dashboard.packit.dev/results/testing-farm/154616
• https://dashboard.packit.dev/results/testing-farm/154617

But from here Details point to the same url:

• https://dashboard.packit.dev/results/copr-builds/559803

I'd expect to be able to get the to srpm build logs of each of the tmt jobs:

• https://copr.fedorainfracloud.org/coprs/packit/teemtee-tmt-1760/builds/
• https://copr.fedorainfracloud.org/coprs/packit/teemtee-tmt-1760-internal-wow/builds/
• https://copr.fedorainfracloud.org/coprs/packit/teemtee-tmt-1760-internal-plugins/builds/

@lachmanfrantisek, what do you think?

[lachmanfrantisek]

@psss Aha, you are right.

The question is if it should do a single build and share it or run three Copr builds. Now the dashboard shows what actually happened ... this one uses the packit/teemtee-tmt-1760-internal-wow Copr repo.

It's yet another issue with the implicit Copr build for tests and identifiers and this should be fixed by packit/packit-service#1775 and packit/packit-service#1720

Is this ok for you that it works like that? (Before we fix those two issues.)

[lbarcziova]

@psss, as Franta pointed out, this is a bug because of the implicit Copr builds for tests.

Would adding the explicit Copr build definition to your config:

- job: copr_build
  trigger: pull_request
  targets:
  - fedora-all
  - epel-8
  - epel-9
  enable_net: False

work for you? The build would be then run only once and reused by all test jobs. (With the issues linked by Franta, we are going that direction anyways)