Similar, but not complaining about Too many open files in the last part,
instead it's complaining about subprocesses that are still running
[rkieley@z820 4]$ ctest -VV -R c-fdlimit-tests --repeat-until-fail 10
UpdateCTestConfiguration from
:/wip/builds/github.com/apache/qpid-proton/0.37.0-rc2/4/DartConfiguration.tcl
Parse Config
file:/wip/builds/github.com/apache/qpid-proton/0.37.0-rc2/4/DartConfiguration.tcl
UpdateCTestConfiguration from
:/wip/builds/github.com/apache/qpid-proton/0.37.0-rc2/4/DartConfiguration.tcl
Parse Config
file:/wip/builds/github.com/apache/qpid-proton/0.37.0-rc2/4/DartConfiguration.tcl
Test project /wip/builds/github.com/apache/qpid-proton/0.37.0-rc2/4
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 6
Start 6: c-fdlimit-tests
6: Test command: /usr/bin/python3.10
"/wip/src/github.com/apache/qpid-proton/scripts/env.py" "--"
"PATH=/wip/builds/github.com/apache/qpid-proton/0.37.0-rc2/4/c/examples:/home/rkieley/.local/bin:/home/rkieley/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin"
"PYTHO
NPATH=/wip/src/github.com/apache/qpid-proton/tests/py"
"TEST_EXE_PREFIX=/usr/bin/valgrind --tool=memcheck --leak-check=full
--error-exitcode=42 --quiet
--suppressions=/wip/src/github.com/apache/qpid-proton/tests/valgrind.supp"
"TEST_EXE_PREFIX=" "/usr/bin/python3.10" "/
wip/src/github.com/apache/qpid-proton/c/tests/fdlimit.py"
6: Test timeout computed to be: 1500
6: F/usr/lib64/python3.10/subprocess.py:1067: ResourceWarning: subprocess 59241
is still running
6: _warn("subprocess %s is still running" % self.pid,
6: ResourceWarning: Enable tracemalloc to get the object allocation traceback
6: /usr/lib64/python3.10/subprocess.py:1067: ResourceWarning: subprocess 59240
is still running
6: _warn("subprocess %s is still running" % self.pid,
.
.
.
6: ResourceWarning: Enable tracemalloc to get the object allocation traceback
6: /usr/lib64/python3.10/subprocess.py:1067: ResourceWarning: subprocess 58988
is still running
6: _warn("subprocess %s is still running" % self.pid,
6: ResourceWarning: Enable tracemalloc to get the object allocation traceback
6: /usr/lib64/python3.10/subprocess.py:1067: ResourceWarning: subprocess 58987
is still running
6: _warn("subprocess %s is still running" % self.pid,
6: ResourceWarning: Enable tracemalloc to get the object allocation traceback
6: /usr/lib64/python3.10/subprocess.py:1067: ResourceWarning: subprocess 59242
is still running
6: _warn("subprocess %s is still running" % self.pid,
6: ResourceWarning: Enable tracemalloc to get the object allocation traceback
6:
6: ======================================================================
6: FAIL: test_fd_limit_broker (__main__.FdLimitTest)
6: Check behaviour when running out of file descriptors on accept
6: ----------------------------------------------------------------------
6: Traceback (most recent call last):
6: File "/wip/src/github.com/apache/qpid-proton/c/tests/fdlimit.py", line 77,
in test_fd_limit_broker
6: self.assertNotEqual(sender.poll(), 0)
6: AssertionError: 0 == 0
6:
6: ----------------------------------------------------------------------
6: Ran 1 test in 2.162s
6:
6: FAILED (failures=1)
Test #6: c-fdlimit-tests ..................***Failed 2.30 sec
On 2022/03/18 09:28:03 Jiri Daněk wrote:
> On Fri, Mar 18, 2022 at 10:20 AM Roddie Kieley <rkie...@apache.org> wrote:
>
> > Has anyone else been testing with python 3.10? I see that we specify
> > python 3.6+ as per:
> >
> > -- Found Python: /usr/bin/python3.10 (found suitable version "3.10.0",
> > minimum required is "3.6") found components: Interpreter Development
> > Development.Module Development.Embed
> >
> > but on Fedora 34 with python 3.10 installed and built using gcc I see that
> > the c-fdlimits-tests fail intermittently. With clang 12.0.1 + python 3.10
> > the list of failures is larger and more consistent. Should we expect this
> > to be a python 3.10 to be usable at the moment? If this is not an issue
> > specific to my environment, are we able to release note it?
> >
>
> Python 3.10 is default on Fedora 35 as well, so I expect most people here
> will use this version of Python.
>
> Does the fdlimits failure look anything like the former problems with the
> test?
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20PROTON%20AND%20text%20~%20c-fdlimits-tests
>
> What are the other failures? Could it be that newer Python is more
> sensitive to detecting resource leaks?
> --
> Mit freundlichen Grüßen / Kind regards
> Jiri Daněk
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
