PR#7: Test that triggers forward Python3 incompatibility - rpms/m2crypto

rpms / m2crypto

#7 Test that triggers forward Python3 incompatibility

Opened 2 years ago by abitrolly. Modified 2 years ago

rpms/ abitrolly/m2crypto enable-tests into rawhide

Test that triggers forward Python3 incompatibility

Anatoli Babenia • 2 years ago

e0cc138

.fmf/version

file added

		`@@ -0,0 +1,1 @@`
		`+ 1`

plans/smoke.fmf

file added

		`@@ -0,0 +1,8 @@`
		`+ summary: Basic smoke test for python3-m2crypto`
		`+ prepare:`
		`+ - how: install`
		`+ package:`
		`+ - python3-setuptools`
		`+ - python3-m2crypto`
		`+ execute:`
		`+ script: python3 -c "import M2Crypto"`

abitrolly commented 2 years ago

Error:
 Problem: python3-3.11.0~b4-1.fc37.i686 has inferior architecture
  - package python3-setuptools-62.6.0-1.fc37.noarch requires python(abi) = 3.11, but none of the providers can be installed
  - cannot install both python3-3.11.0~b4-1.fc37.x86_64 and python3-3.10.4-1.fc37.x86_64
  - package python3-m2crypto-0.38.0-2.fc35.x86_64 requires python(abi) = 3.10, but none of the providers can be installed
  - conflicting requests

Based on https://docs.fedoraproject.org/en-US/ci/tmt/

zuul commented 2 years ago

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci

check-for-arches : SUCCESS in 52s
rpm-scratch-build : FAILURE in 9m 49s
rpm-scratch-build-s390x : FAILURE in 8m 55s (non-voting)
rpm-scratch-build-ppc64le : FAILURE in 10m 51s (non-voting)
rpm-scratch-build-i686 : FAILURE in 9m 48s (non-voting)
rpm-scratch-build-aarch64 : FAILURE in 10m 20s (non-voting)
rpm-linter : SKIPPED (non-voting)
rpm-rpminspect : SKIPPED (non-voting)
check-for-tests : SKIPPED
check-for-sti-tests : SKIPPED
check-for-fmf-tests : SKIPPED
rpm-install-test : SKIPPED
rpm-test : SKIPPED
rpm-tmt-test : SKIPPED
rpm-sti-test : SKIPPED

churchyard commented 2 years ago

What is the benefit of this test?

abitrolly commented 2 years ago

To catch issues with compilation automatically. Came here after

https://github.com/openSUSE/osc/runs/7515452430?check_suite_focus=true

churchyard commented 2 years ago

issues with compilation are caught automatically during the build.

abitrolly commented 2 years ago

Then why these issues are not created at https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Fedora&component=m2crypto&list_id=12769483&product=Fedora&product=Fedora%20EPEL ?

churchyard commented 2 years ago

They are. It's https://bugzilla.redhat.com/show_bug.cgi?id=2021972

abitrolly commented 2 years ago

But that bug was created manually by Sahana Prasad. And I definitely seen it, but couldn't connect the problem. If understand the role of tmt right, such issues should be created automatically (and probably updated as well).

churchyard commented 2 years ago

I have never heard of automatically created bugzillas when tmt test fails in the CI.

Also, this test will never run, because the package does not build.

abitrolly commented 2 years ago

https://docs.fedoraproject.org/en-US/ci/#_how doesn't list this indeed. But it would be nice, right?

churchyard commented 2 years ago

Sure I guess.

abitrolly commented 2 years ago

Filled RFE https://pagure.io/fedora-ci/general/issue/357