Bug 2097130 - dlrn test run hangs with the latest setuptools version
Summary: dlrn test run hangs with the latest setuptools version
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: dlrn
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Javier Peña
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2064842
TreeView+ depends on / blocked
 
Reported: 2022-06-14 21:58 UTC by Charalampos Stratakis
Modified: 2022-06-16 13:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-16 13:38:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Charalampos Stratakis 2022-06-14 21:58:29 UTC
dlrn test run hangs with the latest setuptools version.

For the build logs, see:
https://download.copr.fedorainfracloud.org/results/cstratak/setuptools-62.4.0-final/fedora-rawhide-x86_64/04534441-dlrn/

For all our attempts to build dlrn with the latest setuptools, see:
https://copr.fedorainfracloud.org/coprs/cstratak/setuptools-62.4.0-final/package/dlrn/

Testing and rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with latest setuptools version:
https://copr.fedorainfracloud.org/coprs/cstratak/setuptools-62.4.0-final/

Let us know here if you have any questions.

Comment 1 Javier Peña 2022-06-15 08:37:33 UTC
It looks like testrepository is creating this issue, and switching to stestr for tests will fix it. I'm testing it.

Comment 2 Javier Peña 2022-06-15 08:45:16 UTC
Ok, dlrn-0.14.0-10 shoud fix the issue. Rawhide build in https://koji.fedoraproject.org/koji/taskinfo?taskID=88286493, waiting for copr build to confirm.

Comment 3 Javier Peña 2022-06-16 13:38:32 UTC
I can see the latest build passed in https://copr.fedorainfracloud.org/coprs/cstratak/setuptools-62.4.0-final/package/dlrn/, closing the bug.


Note You need to log in before you can comment on or make changes to this bug.