Bug 1630169 - package python34 can not be mock rebuild because of failuire in unit test
Summary: package python34 can not be mock rebuild because of failuire in unit test
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python34
Version: epel7
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Nobody
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-18 06:24 UTC by Tengent Yang
Modified: 2024-07-09 02:34 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-07-09 02:34:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
mock build logs in /var/log/mock/epel-7-x86_64/results (416.65 KB, application/x-gzip)
2018-09-18 06:24 UTC, Tengent Yang
no flags Details
epel-7-x86_64.cfg for mock in /etc/mock (2.34 KB, text/plain)
2018-09-18 06:29 UTC, Tengent Yang
no flags Details

Description Tengent Yang 2018-09-18 06:24:50 UTC
Created attachment 1484250 [details]
mock build logs in /var/log/mock/epel-7-x86_64/results

Description of problem:
I tried to rebuild python34(both 3.4.8-2, 3.4.9-1) with Mock 1.4.11 (on a fedora 27 machine) but the build was failed. I check the build.log file which shows that there were 22 tests failed, and below is the list
-------------------------------------------------------------------------
22 tests failed:
    test_posix test_pydoc test_quopri test_readline test_script_helper
    test_shutil test_signal test_site test_source_encoding
    test_subprocess test_sys test_tarfile test_tempfile test_threading
    test_tools test_traceback test_tracemalloc test_unicodedata
    test_venv test_warnings test_weakref test_zipimport_support
-------------------------------------------------------------------------

Because the compile is done while the unit test is not pass through, I just wanna figure out if I make some mistake or miss some options to rebuild this source package,  thanks for your guys help !


Version-Release number of selected component (if applicable):
python34-3.4.8-2.el7.src.rpm
python34-3.4.9-1.el7.src.rpm

How reproducible:
Try to rebuild the package using mock

1. install mock and check version
$ dnf install -y mock
$ rpm -qa|grep mock
mock-1.4.11-1.fc27.noarch
mock-core-configs-28.4-1.fc27.noarch

2. mock rebuild
$ sudo mock -r epel-7-x86_64 --rebuild python34-3.4.8-2.el7.src.rpm

Actual results:
package building ends in failure

Expected results:
package rebuilt successfully

Additional info:
directory '/var/lib/mock/epel-7-x86_64/results' is packaged as an attachment in which build.log shows all failed tests.

Comment 1 Tengent Yang 2018-09-18 06:29:13 UTC
Created attachment 1484252 [details]
epel-7-x86_64.cfg for mock in /etc/mock

Comment 2 Miro Hrončok 2018-09-18 08:55:57 UTC
I'm running the following locally now to see if it builds:

$ fedpkg clone python34
$ fedpkg switch-branch epel7
$ fedpkg mockbuild

Do you get the saem test failures with 3.4.8 and 3.4.9?

As a side not, plese don't sudo mock, follow https://github.com/rpm-software-management/mock/wiki#setup instead.

Comment 3 Miro Hrončok 2018-09-18 09:50:03 UTC
It seems that I lack the RAM needed to test this. Had to shutdown my workstation manually.

Comment 4 Tengent Yang 2018-09-18 14:38:02 UTC
Thanks for your advice , Miro

Yes, same failure with both 3.4.9 and 3.4.8

I check my log and koji build @ https://kojipkgs.fedoraproject.org//packages/python34/3.4.9/1.el7/data/logs/x86_64/build.log

both 2 building skip huge RAM test  like 
 47705 test_huge_bytes_32b (test.test_pickle.InMemoryPickleTests) ... skipped 'not enough memory: 5.0G minimum needed'
 47706 test_huge_bytes_64b (test.test_pickle.InMemoryPickleTests) ... skipped 'not enough memory: 10.0G minimum needed'
...
57497 test_oversized_digit_strings (test.test_strtod.StrtodTests) ... skipped 'not enough memory: 6.0G minimum needed'

Comment 5 Petr Viktorin (pviktori) 2019-01-21 13:32:47 UTC
This bug has low priority for me. If you'd like to take it, please go ahead!

Comment 6 Tomas Orsava 2019-10-29 14:44:12 UTC
I'm swamped with other priorities. If anybody's interested, please take over.

Comment 7 Troy Dawson 2024-07-09 02:34:12 UTC
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.


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