Bug 1165453 - python-mailmanclient fails to build on 1-core VM
Summary: python-mailmanclient fails to build on 1-core VM
Status: RESOLVED INVALID
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Development (show other bugs)
Version: Current
Hardware: Other openSUSE Factory
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Petr Gajdos
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-02 14:11 UTC by Bernhard Wiedemann
Modified: 2020-06-15 19:50 UTC (History)
3 users (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
log of failed build (135.93 KB, text/plain)
2020-05-15 08:36 UTC, Bernhard Wiedemann
Details
output of osc lbl (86.15 KB, text/plain)
2020-06-15 19:49 UTC, Matej Cepl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Wiedemann 2020-03-02 14:11:36 UTC
While working on reproducible builds for openSUSE, I found that
our python-mailmanclient package fails to build on 1-core VMs

Steps To Reproduce:

osc co openSUSE:Factory/python-mailmanclient && cd $_
osc build -j1 --vm-type=kvm --noservice standard

Actual Results:

[  206s] ---------------------------- Captured stderr setup 
[  206s] --- Logging error ---
[  206s] Traceback (most recent call last):
[  206s]   File "/usr/lib64/python3.7/logging/handlers.py", line 933, in emit
[  206s]     self.socket.send(msg)
[  206s] OSError: [Errno 9] Bad file descriptor
[  206s]
[  206s] During handling of the above exception, another exception occurred:
[  206s]
[  206s] Traceback (most recent call last):
[  206s]   File "/usr/lib64/python3.7/logging/handlers.py", line 936, in emit
[  206s]     self._connect_unixsocket(self.address)
[  206s]   File "/usr/lib64/python3.7/logging/handlers.py", line 854, in _connect_unixsocket
[  206s]     self.socket.connect(address)
[  206s] FileNotFoundError: [Errno 2] No such file or directory
[  206s] Call stack:
[  206s]   File "/usr/bin/py.test-3.7", line 11, in <module>
[  206s]     load_entry_point('pytest==5.3.5', 'console_scripts', 'py.test')()
...
[  206s]   File "/usr/lib/python3.7/site-packages/pluggy/callers.py", line 187, in _multicall
[  206s]     res = hook_impl.function(*args)
[  206s]   File "/usr/lib/python3.7/site-packages/_pytest/fixtures.py", line 958, in pytest_fixture_setup
[  206s]     result = call_fixture_func(fixturefunc, request, kwargs)
[  206s]   File "/usr/lib/python3.7/site-packages/_pytest/fixtures.py", line 788, in call_fixture_func
[  206s]     res = fixturefunc(**kwargs)
[  206s]   File "/home/abuild/rpmbuild/BUILD/mailmanclient-3.3.0/src/mailmanclient/conftest.py", line 48, in mailman_core
[  206s]     request=request,
[  206s]   File "/usr/lib/python3.7/site-packages/pytest_services/service.py", line 71, in watcher_getter_function 
[  206s]     services_log.debug('Starting {0}: {1}'.format(name, arguments))
[  206s] Message: "Starting master: ['-C', 'mailman_test.cfg']"
[  206s] Arguments: ()
[  206s] ============ 15 passed, 1 deselected, 1 error in 154.12s (0:02:34) 


Feel free to move upstream as you see fit.
Comment 1 Petr Gajdos 2020-05-14 14:01:17 UTC
I cannot reproduce:

devel:languages:python:mailman/python-mailman$ osc build -j1 --vm-type=kvm --noservice

[..]

/var/tmp/build-root/openSUSE_Tumbleweed-x86_64/.mount/.build.packages/SRPMS/python-mailman-3.3.1-0.src.rpm

/var/tmp/build-root/openSUSE_Tumbleweed-x86_64/.mount/.build.packages/RPMS/noarch/python3-mailman-3.3.1-0.noarch.rpm

devel:languages:python:mailman/python-mailman$

Am I missing something? Perhaps a temporary condition?
Comment 2 Bernhard Wiedemann 2020-05-15 08:36:27 UTC
Created attachment 837823 [details]
log of failed build

I ran the reproducer a few times on different machines:
on 1 newer SLE-12-SP5 machine it succeeded 4/4
on 2 older Leap-15.1 machines (~2010) it failed 5/5 with varying numbers of failures

So maybe some racy-ness is involved?

> ERROR at setup of TestUnicode.test_repr 
was always among the errors.
Comment 3 Petr Gajdos 2020-05-15 08:51:26 UTC
To be honest, I do not know. Adding Matěj and Tomáš, perhaps they had seen it already?
Comment 4 Petr Gajdos 2020-05-15 08:52:27 UTC
(I am using Tumbleweed system for build.)
Comment 5 Matej Cepl 2020-06-15 19:49:34 UTC
Created attachment 838813 [details]
output of osc lbl

Cannot reproduce here:

$ osc build --clean -j1 --vm-type=kvm --noservice

just works without any problems (see attached build log). With Tumbleweed, true, but nothing else. There must be something strange about your configuration.
Comment 6 Matej Cepl 2020-06-15 19:50:40 UTC
If you find some way how to reliably reproduce, please, reopen this bug. Until then, I cannot keep it open.