[issue46263] FreeBSD buildbots cannot compile Python
Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue46263> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47205] posix.sched_{get|set}affinity(-1) no longer returns ProcessLookup causing test failures on FreeBSD
Change by Kubilay Kocak :
--
title: test_sched_getaffinity and setaffinity fail on FreeBSD buildbit ->
posix.sched_{get|set}affinity(-1) no longer returns ProcessLookup causing test
failures on FreeBSD
___
Python tracker
<https://bugs.python.org/issue47205>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47205] test_sched_getaffinity and setaffinity fail on FreeBSD buildbit
Kubilay Kocak added the comment:
>From one of our base/kernel developers:
--
> koobs wrote:
>
> I don't grok the system call semantics, but it appears the issue is calls
> with the '-1' argument:
>
> mask = posix.sched_getaffinity(0)
> ...
> self.assertRaises(OSError, posix.sched_getaffinity, -1)
> ...
> self.assertRaises(OSError, posix.sched_setaffinity, -1, mask)
>
> This line was added 10 years ago in:
>
> https://github.com/python/cpython/commit/848698727fcbb633246b56ab57080b4d5493c186
>
> It wants an OSError [1] and presumably was getting it before recent
> failures, but isn't anymore:
>
> [1] https://docs.python.org/3/library/exceptions.html#OSError
So this is the difference:
Python 3.11.0a6+ (heads/main:38ae5b8c0c, Apr 5 2022, 03:27:23) [GCC 11.2.0] on
freebsd13
Type "help", "copyright", "credits" or "license" for more information.
>>> import posix
>>> mask = posix.sched_getaffinity(-1)
>>> mask
{0, 1, 2, 3, 4, 5, 6, 7}
Python 3.10.4 (main, Mar 25 2022, 00:00:00) [GCC 11.2.1 20220127 (Red Hat
11.2.1-9)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import posix
>>> mask = posix.sched_getaffinity(-1)
Traceback (most recent call last):
File "", line 1, in
ProcessLookupError: [Errno 3] No such process
FreeBSD always accepted -1 as denoting the current process, while Linux
does not. In fact, Linux uses 0 as current process pid alias.
For FreeBSD, both -1 and 0 works as getpid(), and I do not see it right
to break our traditional API conventions. I believe the test should be
fixed.
--
I am not sure what changed between 3.10 and main that changed/removed
ProcessLookupError as the return for posix.sched_{get|set}affinity
with -1 as the argument, but that appears to be the cause of the current test
failure
--
___
Python tracker
<https://bugs.python.org/issue47205>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue47205] test_sched_getaffinity and setaffinity fail on FreeBSD buildbit
Kubilay Kocak added the comment: Investigating -- stage: patch review -> type: -> behavior ___ Python tracker <https://bugs.python.org/issue47205> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46432] AMD64 FreeBSD Shared 3.x buildbot fails to build: error: error reading 'LASTCFLAGS'
Kubilay Kocak added the comment: I modified the systems /etc/make.conf for unrelated purposes today (adding in LASTCFLAGS among other variables). Why and how Pythons build is inheriting that is the bigger question. I wonder if its buildbot environment related. In the short term I've removed the variables from /etc/make.conf and I have initiated a rebuild. Please leave this issue open -- ___ Python tracker <https://bugs.python.org/issue46432> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44892] [configparser] Module configparser fails when the config file contains a "%" inside a commentary
Change by Kubilay Kocak : -- assignee: terry.reedy -> components: +Library (Lib) -Extension Modules, FreeBSD, IDLE, IO, Installation, Interpreter Core, SSL, Subinterpreters, Tests, Tkinter, Windows, XML, macOS nosy: +lukasz.langa -koobs, ned.deily, paul.moore, ronaldoussoren, steve.dower, terry.reedy, tim.golden, zach.ware title: [configparser] Module configparser fails when the config file contains a0918076336 "100%" inside a commentary -> [configparser] Module configparser fails when the config file contains a "%" inside a commentary type: enhancement -> behavior versions: -Python 3.10, Python 3.11, Python 3.6, Python 3.7, Python 3.8, Python 3.9 ___ Python tracker <https://bugs.python.org/issue44892> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44849] test_os: test_get_set_inheritable_o_path() failed on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: Reference for Linux behaviour: filedesc: don't use ioctl(FIOCLEX) on Linux #62425 https://github.com/rust-lang/rust/pull/62425 Looks like we match the behaviour intentionally (or otherwise). -- ___ Python tracker <https://bugs.python.org/issue44849> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44849] test_os: test_get_set_inheritable_o_path() failed on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: O_PATH support was added in FreeBSD CURRENT April 15: https://reviews.freebsd.org/D29323?id=86257 https://github.com/freebsd/freebsd-src/commit/8d9ed174f3afba5f114742447e622fc1173d4774 @Victor If the failure in this tests suggests either a bug in our implementation, or an incompatibility, please let me know/clarify so I can get our implementation polished -- ___ Python tracker <https://bugs.python.org/issue44849> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44849] test_os: test_get_set_inheritable_o_path() failed on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: There was a recent worker update to latest CURRENT (14). I'll try to identify recent changes or changesets that may have affected behaviour and reference them here -- ___ Python tracker <https://bugs.python.org/issue44849> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36216] CVE-2019-9636: urlsplit does not handle NFKC normalization
Kubilay Kocak added the comment: Fix meta (not incl 2.7 which is no longer available to select). -- components: +Unicode -FreeBSD versions: +Python 3.7, Python 3.8 ___ Python tracker <https://bugs.python.org/issue36216> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43901] Lazy-create an empty annotations dict in all unannotated user classes and modules
Change by Kubilay Kocak : -- components: +Interpreter Core -FreeBSD nosy: -koobs ___ Python tracker <https://bugs.python.org/issue43901> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43233] test_os: test_copy_file_range_offset fails on FreeBSD CURRENT
Kubilay Kocak added the comment: I'll see if I can isolate -- ___ Python tracker <https://bugs.python.org/issue43233> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43068] test_subprocess: test_specific_shell() fails on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: P.S gdb and bash have been rebuilt :) -- ___ Python tracker <https://bugs.python.org/issue43068> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43068] test_subprocess: test_specific_shell() fails on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: Note: Not suggesting dep removals, just a try-except-skip block in the (hopefully) one place the sub-process handler in the test framework that runs then :) -- ___ Python tracker <https://bugs.python.org/issue43068> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13501] Make libedit support more generic; port readline / libedit to FreeBSD
Kubilay Kocak added the comment: @Gregory I'm the worker owner and can coordinate buildbot worker changes with Zach or Victor FreeBSD has: editline (in FreeBSD base, installed in /usr/ ) libedit in ports/packages (installs in /usr/local) readline in ports/packages (installs in /usr/local) Which combination would get us the best coverage? Also, if both libedit and readline are installed from ports, does configure have a preference/default or will it barf? Primary motivation behind the questions is that the Python build system is notoriously flaky with respect to third party libs in various locations (we've had issues with gettext, ssl, expat, among a few others) I'm happy to install whatever you'd like on the workers at your convenience to the tests can be run as a custom build (if they haven't been already) -- ___ Python tracker <https://bugs.python.org/issue13501> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13501] Make libedit support more generic; port readline / libedit to FreeBSD
Kubilay Kocak added the comment: Would we like the freebsd worker CI configurations to be modified to use ports/package versions of libedit (or readline, or whatever) to ensure converage? Right now the defaults are used (whatever edit library that entails) -- ___ Python tracker <https://bugs.python.org/issue13501> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43068] test_subprocess: test_specific_shell() fails on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: Rebuilding bash & gdb now to pickup new/updated ncurses library. Still suggest picking up "subprocess.CalledProcessError" generically in test framework for tests that use subprocess/external commands -- ___ Python tracker <https://bugs.python.org/issue43068> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43068] test_subprocess: test_specific_shell() fails on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: The failure mode is a generic "an external dependency expected by a test suite is not available or doesn't run", applying to many core Python test that invokes an external utilities, and not specific to OS. As far as I'm aware, the best practice and recommendation for these cases is that 'tests should not test dependencies', and to skip/skipif these (external) dependencies are not available or fail to load/run. Of course, the call is yours :) I'll rebuild gdb/bash if you decide you don't want the error to remain to test improving the test suite. -- ___ Python tracker <https://bugs.python.org/issue43068> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43068] test_subprocess: test_specific_shell() fails on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment:
FreeBSD base was updated on the FreeBSD workers, between versions that changes
the way the base curses library was built, and what it built.
The net results was that any software (from ports) linked against base curses
needed to be rebuilt, and until then would fail to load with the following
error:
ld-elf.so.1: Shared object "libncursesw.so.6" not found, required by "foo"
The test suite should guard/test for the inability to execute (successfully
load/run) the required commands/functions.
The following tests also failed for the same reason:
==
ERROR: test_deactivate_with_strict_bash_opts (test.test_venv.BasicTest)
--
Traceback (most recent call last):
File
"/usr/home/buildbot/python/3.9.koobs-freebsd-564d/build/Lib/test/test_venv.py",
line 391, in test_deactivate_with_strict_bash_opts
out, err = check_output([bash, test_script])
File
"/usr/home/buildbot/python/3.9.koobs-freebsd-564d/build/Lib/test/test_venv.py",
line 44, in check_output
raise subprocess.CalledProcessError(
subprocess.CalledProcessError: Command '['/usr/local/bin/bash',
'/var/tmp/tmprk2_yuoe/test_strict.sh']' returned non-zero exit status 1.
0:14:07 load avg: 1.31 Re-running test_gdb in verbose mode
test test_gdb crashed -- Traceback (most recent call last):
File
"/usr/home/buildbot/python/3.9.koobs-freebsd-564d/build/Lib/test/libregrtest/runtest.py",
line 270, in _runtest_inner
refleak = _runtest_inner2(ns, test_name)
File
"/usr/home/buildbot/python/3.9.koobs-freebsd-564d/build/Lib/test/libregrtest/runtest.py",
line 221, in _runtest_inner2
the_module = importlib.import_module(abstest)
File
"/usr/home/buildbot/python/3.9.koobs-freebsd-564d/build/Lib/importlib/__init__.py",
line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 790, in exec_module
File "", line 228, in _call_with_frames_removed
File
"/usr/home/buildbot/python/3.9.koobs-freebsd-564d/build/Lib/test/test_gdb.py",
line 48, in
gdb_version, gdb_major_version, gdb_minor_version = get_gdb_version()
File
"/usr/home/buildbot/python/3.9.koobs-freebsd-564d/build/Lib/test/test_gdb.py",
line 29, in get_gdb_version
raise Exception(f"Command {' '.join(cmd)!r} failed "
Exception: Command 'gdb -nx --version' failed with exit code 1: stdout=''
stderr='ld-elf.so.1: Shared object "libncursesw.so.6" not found, required by
"gdb"\n'
Would you like me to rebuild bash/gdb to fix the error, or wait for the tests
to be fixed so that they can handle the error condition?
--
___
Python tracker
<https://bugs.python.org/issue43068>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42960] resources module, FreeBSD update adding RLIMIT_KQUEUES constant
New submission from Kubilay Kocak : Thank you for the PR David. If there's anything I can do to help support you with respect to Python on FreeBSD (such as accounts on the official freebsd python buildbot workers) let me know :) -- ___ Python tracker <https://bugs.python.org/issue42960> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41013] test_os.test_memfd_create() fails on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: @Kyle Yes, msg373597 freebsd CURRENT buildbot passes, but freebsd 12/stable does not (cannot, since stable/12 wont get the syscall) That means the Python memfd functions and tests need to account for this -- ___ Python tracker <https://bugs.python.org/issue41013> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41013] test_os.test_memfd_create() fails on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: I've updated the FreeBSD CURRENT buildbot past base/r363065 [1] which implements SHM_GROW_ON_WRITE: https://svnweb.freebsd.org/changeset/base/363065 https://reviews.freebsd.org/D25502 Also worth noting that I don't believe stable/12 (FreeBSD 12.x) will be getting this syscall (correct me if im wrong Kyle), so these tests may still fail on the FreeBSD 12.x worker, and the tests should be updated to account for that in some manner. -- ___ Python tracker <https://bugs.python.org/issue41013> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38576] CVE-2019-18348: CRLF injection via the host part of the url passed to urlopen()
Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue38576> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39503] [security][CVE-2020-8492] Denial of service in urllib.request.AbstractBasicAuthHandler
Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue39503> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41013] test_os.test_memfd_create() fails on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: memfd_create came in via: https://github.com/freebsd/freebsd/commit/575e351fdd996f72921b87e71c2c26466e887ed2 via review: https://reviews.freebsd.org/D21393 via kevans (cc'd) -- nosy: +kevans ___ Python tracker <https://bugs.python.org/issue41013> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37224] [subinterpreters] test__xxsubinterpreters fails randomly
Kubilay Kocak added the comment:
Failure on AMD64 FreeBSD Shared 3.x (full log attached):
==
FAIL: test_subinterpreter (test.test__xxsubinterpreters.IsRunningTests)
--
Traceback (most recent call last):
File
"/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/test/test__xxsubinterpreters.py",
line 478, in test_subinterpreter
self.assertTrue(interpreters.is_running(interp))
AssertionError: False is not true
...
2 tests failed:
test__xxsubinterpreters test_interpreters
...
test_already_running (test.test_interpreters.TestInterpreterRun) ... spam
Stderr:
Exception in thread Thread-19:
Traceback (most recent call last):
File
"/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/threading.py", line
950, in _bootstrap_inner
self.run()
File
"/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/threading.py", line
888, in run
self._target(*self._args, **self._kwargs)
File
"/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/test/test_interpreters.py",
line 45, in run
interp.run(dedent(f"""
File
"/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/test/support/interpreters.py",
line 94, in run
_interpreters.run_string(self._id, src_str)
RuntimeError: unrecognized interpreter ID 111
FAIL
...
test test_interpreters failed
test_send_recv_same_interpreter (test.test_interpreters.TestSendRecv) ... ok
==
FAIL: test_still_running (test.test_interpreters.TestInterpreterDestroy)
--
Traceback (most recent call last):
File
"/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/test/test_interpreters.py",
line 309, in test_still_running
interp.close()
AssertionError: RuntimeError not raised
==
FAIL: test_subinterpreter (test.test_interpreters.TestInterpreterIsRunning)
--
Traceback (most recent call last):
File
"/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/test/test_interpreters.py",
line 207, in test_subinterpreter
self.assertTrue(interp.is_running())
AssertionError: False is not true
==
FAIL: test_already_running (test.test_interpreters.TestInterpreterRun)
--
Traceback (most recent call last):
File
"/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/test/test_interpreters.py",
line 383, in test_already_running
self.interp.run('print("spam")')
AssertionError: RuntimeError not raised
Stderr:
Exception in thread Thread-19:
Traceback (most recent call last):
File
"/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/threading.py", line
950, in _bootstrap_inner
self.run()
File
"/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/threading.py", line
888, in run
self._target(*self._args, **self._kwargs)
File
"/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/test/test_interpreters.py",
line 45, in run
interp.run(dedent(f"""
File
"/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/test/support/interpreters.py",
line 94, in run
_interpreters.run_string(self._id, src_str)
RuntimeError: unrecognized interpreter ID 111
--
Ran 40 tests in 20.251s
FAILED (failures=3)
1 test failed again:
test_interpreters
== Tests result: FAILURE then FAILURE ==
...
1 test failed:
test_interpreters
...
2 re-run tests:
test__xxsubinterpreters test_interpreters
--
nosy: +koobs
Added file:
https://bugs.python.org/file49224/3.x.koobs-freebsd-564d-build-973-test-stdio.txt
___
Python tracker
<https://bugs.python.org/issue37224>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40900] uuid module build fix on FreeBSD proposal
Kubilay Kocak added the comment: Another example, this time for lzma: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209355 -- ___ Python tracker <https://bugs.python.org/issue40900> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40900] uuid module build fix on FreeBSD proposal
Kubilay Kocak added the comment: FreeBSD base provides uuid.h (uuid(3)) but uuid libraries/headers can be provided by e2fsprogs-libuuid (for example) in another location, for example /usr/local/ Pythons build system doesn't provide sufficient granularity to pass include/library locations for *specific* components of the build in every circumstance. The following is a bug related to Python 3.7+ and the uuid.h / linking problem: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229562 The current patch just ignores the third-party (/usr/local) version of uuid.h, allowing the build to proceed with the headers provided by base: https://bz-attachments.freebsd.org/attachment.cgi?id=200603 The proper/permanent solution might be to allow a --with-uuid= style build argument This issue of conflicting / multiple library versions and include order has also come up in various forms for other third party library support in Python, such as gettext (libintl), expat, ssl, libffi, curses) See the following FreeBSD Python port block for the libintl example: https://svnweb.freebsd.org/ports/head/lang/python37/Makefile?revision=536776=markup#l71 -- ___ Python tracker <https://bugs.python.org/issue40900> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39321] AMD64 FreeBSD Non-Debug 3.x: out of swap space (test process killed by signal 9)
Kubilay Kocak added the comment: Added 8gb swap disk to each BB worker -- resolution: -> fixed status: open -> closed ___ Python tracker <https://bugs.python.org/issue39321> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39321] AMD64 FreeBSD Non-Debug 3.x: out of swap space (test process killed by signal 9)
Kubilay Kocak added the comment: Provisioning new/additional swap to both of FreeBSD BB workers in the next few days. Apologies for the delay -- ___ Python tracker <https://bugs.python.org/issue39321> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40018] test_ssl fails with OpenSSL 1.1.1e
Kubilay Kocak added the comment: Confirming: test_ssl passes with 1.1.1e + reverted EOF change -- ___ Python tracker <https://bugs.python.org/issue40018> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40018] test_ssl fails with OpenSSL 1.1.1e
Kubilay Kocak added the comment: Updating the koobs-freebsd-564d buildbots FreBSD openssl port now which has had the 1.1.1e EOF change reverted. Will run the last 3.x build again and report here whether it passes (it should) or not. -- ___ Python tracker <https://bugs.python.org/issue40018> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39982] FreeBSD: SCTP tests of test_socket fails on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: +1 to mutually beneficial relationships :) -- ___ Python tracker <https://bugs.python.org/issue39982> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39982] FreeBSD: SCTP tests of test_socket fails on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: koobs-freebsd-564d (CURRENT) BB has been updated past https://svnweb.freebsd.org/base?view=revision=359302 test_socket is no longer failing -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue39982> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32692] [3.6] test_threading.test_set_and_clear fails in AppVeyor CI
Kubilay Kocak added the comment: Seeing the following on the freebsd CURRENT bb: == FAIL: test_set_and_clear (test.test_threading.EventTests) -- Traceback (most recent call last): File "/usr/home/buildbot/python/3.8.koobs-freebsd-9e36.nondebug/build/Lib/test/lock_tests.py", line 418, in test_set_and_clear self.assertEqual(results, [True] * N) AssertionError: Lists differ: [False, False, False, True, True] != [True, True, True, True, True] First differing element 0: False True - [False, False, False, True, True] + [True, True, True, True, True] -- Ran 168 tests in 29.254s FAILED (failures=1) test test_threading failed Full log attached -- nosy: +koobs Added file: https://bugs.python.org/file49006/freebsd-current-non-debug-3.8-build-176.txt ___ Python tracker <https://bugs.python.org/issue32692> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40018] test_ssl fails with OpenSSL 1.1.1e
Kubilay Kocak added the comment: Confirming on FreeBSD CURRENT buildbot worker which had its openssl updated to 1.1.1e a number of days ago. I reverted back to 1.1.1d Full log of the failing build/tests with 1.1.1e attached -- nosy: +koobs Added file: https://bugs.python.org/file48997/amd64.freebsd.shared.3.x.build.450.test.stdio.txt ___ Python tracker <https://bugs.python.org/issue40018> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40039] [CVE-2020-10796] Python multiprocessing Remote Code Execution vulnerability
Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue40039> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39982] FreeBSD: SCTP tests of test_socket fails on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: I've been in touch with the FreeBSD SCTP maintainer and will continue to investigate that avenue. In the meantime, I'm re-running the last successful 3.x build (382 [1]) to see if that fails or not to isolate Cpython code changes as contributing causes [1] https://buildbot.python.org/all/#/builders/152/builds/382 -- ___ Python tracker <https://bugs.python.org/issue39982> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39982] FreeBSD: SCTP tests of test_socket fails on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: Update to BB complete. Rebuilding: https://buildbot.python.org/all/#/builders/18/builds/162 and https://buildbot.python.org/all/#/builders/152/builds/409 -- ___ Python tracker <https://bugs.python.org/issue39982> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39982] FreeBSD: SCTP tests of test_socket fails on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: Saw the following commit which *may* be related: "Log: sendfile() does currently not support SCTP sockets. Therefore, fail the call. " https://svnweb.freebsd.org/changeset/base/358965 I'm updating FreeBSD base on the BB worker to include that commit and will re-run the failing build -- ___ Python tracker <https://bugs.python.org/issue39982> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39954] test_subprocess: test_specific_shell() fails on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: The current test runs a try/finally without any exception handling, so even minimal exception handling will cover a large swatch of potential issues. CalledProcessError [1] returned by check_call() or check_output() appears to be handy [1] https://docs.python.org/3/library/subprocess.html#subprocess.CalledProcessError -- ___ Python tracker <https://bugs.python.org/issue39954> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39954] test_subprocess: test_specific_shell() fails on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: Not suggesting it's the *best* way, but for example, isn't there a way to handle return codes from shell executions such as: https://docs.python.org/3/library/subprocess.html#subprocess.CalledProcessError -- ___ Python tracker <https://bugs.python.org/issue39954> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39954] test_subprocess: test_specific_shell() fails on AMD64 FreeBSD Shared 3.x
Kubilay Kocak added the comment: Updated FreeBSD CURRENT base, which removed libncurses. The bash port installation needed to be rebuilt. @Victor Can tests be skipped on the basis of required dependencies failing to load/run? -- status: open -> pending ___ Python tracker <https://bugs.python.org/issue39954> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39933] test_gdb fails on AMD64 FreeBSD Shared 3.x: ptrace: Operation not permitted
Kubilay Kocak added the comment: Testing with security.bsd.unprivileged_proc_debug=1 -- ___ Python tracker <https://bugs.python.org/issue39933> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39321] AMD64 FreeBSD Non-Debug 3.x: main regrtest process killed by SIGKILL (Signal 9)
Kubilay Kocak added the comment: Investigating -- ___ Python tracker <https://bugs.python.org/issue39321> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36184] test_gdb.test_threads() is specific to _POSIX_THREADS, fail on FreeBSD
Kubilay Kocak added the comment: For our future reference/selves, GDB (currently 9.1 w/ python bindings) is now installed on the two FreeBSD buildbot workers -- ___ Python tracker <https://bugs.python.org/issue36184> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24666] Buffered I/O does not take file position into account when reading blocks
Change by Kubilay Kocak : -- assignee: docs@python -> components: -2to3 (2.x to 3.x conversion tool), Build, Cross-Build, Documentation, Extension Modules, FreeBSD, Installation, Interpreter Core, Library (Lib), SSL, Tests, Unicode, ctypes nosy: -docs@python, koobs ___ Python tracker <https://bugs.python.org/issue24666> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24666] Buffered I/O does not take file position into account when reading blocks
Change by Kubilay Kocak : -- nosy: -Alex.Willmer, ezio.melotti, vstinner ___ Python tracker <https://bugs.python.org/issue24666> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39321] AMD64 FreeBSD Non-Debug 3.x: main regrtest process killed by SIGKILL (Signal 9)
Kubilay Kocak added the comment: Looks OK now: https://buildbot.python.org/all/#/builders/214 If it fails again in the same manner, please re-open -- assignee: -> koobs resolution: -> fixed ___ Python tracker <https://bugs.python.org/issue39321> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39321] AMD64 FreeBSD Non-Debug 3.x: main regrtest process killed by SIGKILL (Signal 9)
Kubilay Kocak added the comment: Rebuilding now -- ___ Python tracker <https://bugs.python.org/issue39321> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39321] AMD64 FreeBSD Non-Debug 3.x: main regrtest process killed by SIGKILL (Signal 9)
Kubilay Kocak added the comment: Identified a kernel/userland mismatch which may have caused this. Have restarted the server and worker, and will rebuild https://buildbot.python.org/all/#/builders/214/builds/152 -- ___ Python tracker <https://bugs.python.org/issue39321> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38815] test_ssl: test_min_max_version() fails on FreeBSD and Fedora
Kubilay Kocak added the comment: @Christian As current assignee, are you able to produce a test that fixes the remaining issue (per msg357792)? I can rebuild OpenSSL on the worker at your direction at any time to make the test fail again or provide you with an SSH account to assist -- stage: patch review -> needs patch ___ Python tracker <https://bugs.python.org/issue38815> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39059] Getting incorrect results in rounding procedures
Change by Kubilay Kocak : -- nosy: -koobs ___ Python tracker <https://bugs.python.org/issue39059> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38815] test_ssl: test_min_max_version() fails on FreeBSD and Fedora
Kubilay Kocak added the comment: I had to rebuild the openssl (1.1.x) port on the worker that had test_ssl failing in order to bring it back to green, so as not to hide new test failures. If/when someone is able to produce a fix for the failing test, I am happy to revert the openssl build to its prior (failing config) state at any time to verify the test fix. -- ___ Python tracker <https://bugs.python.org/issue38815> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38815] test_ssl: test_min_max_version() fails on FreeBSD and Fedora
Kubilay Kocak added the comment: In case it's relevant, I note the following: The ssl module is built with -I/usr/local/include in the compile line. Leaving aside: - the warts of the build system, and - the lack of specific --with-foo= semantics to allow providing well(narrowly)-scoped include/library paths - how and whether the default python build using -I/usr/local/include is 'good' or not ... it means that the build is finding openssl111 on FreeBSD provided by ports, not base (base also includes openssl 1.1.1 @ /usr/include|lib) More specifically, our openssl111 port happens to have many options that allow enabling/disabling various software features, including encryption algorithms and protocol versions The current (installed) build of openssl111 on the buildbot worker that is failing, has the following options set/unset: OPTIONS_FILE_UNSET+=CT OPTIONS_FILE_UNSET+=MAN3 OPTIONS_FILE_UNSET+=RFC3779 OPTIONS_FILE_SET+=SHARED OPTIONS_FILE_UNSET+=ZLIB OPTIONS_FILE_UNSET+=ARIA OPTIONS_FILE_UNSET+=DES OPTIONS_FILE_UNSET+=GOST OPTIONS_FILE_UNSET+=IDEA OPTIONS_FILE_UNSET+=SM2 OPTIONS_FILE_UNSET+=SM3 OPTIONS_FILE_UNSET+=SM4 OPTIONS_FILE_UNSET+=RC2 OPTIONS_FILE_UNSET+=RC4 OPTIONS_FILE_UNSET+=RC5 OPTIONS_FILE_UNSET+=MD2 OPTIONS_FILE_UNSET+=MD4 OPTIONS_FILE_UNSET+=MDC2 OPTIONS_FILE_UNSET+=RMD160 OPTIONS_FILE_SET+=ASM OPTIONS_FILE_SET+=SSE2 OPTIONS_FILE_SET+=THREADS OPTIONS_FILE_SET+=EC OPTIONS_FILE_SET+=NEXTPROTONEG OPTIONS_FILE_UNSET+=SCTP OPTIONS_FILE_UNSET+=SSL3 OPTIONS_FILE_UNSET+=TLS1 OPTIONS_FILE_UNSET+=TLS1_1 OPTIONS_FILE_SET+=TLS1_2 In summary, this build only has TLS 1.2 and TLS 1.3 enabled (but with other various things disabled, not the defaults of the upstream openssl build), and may be indicated in this test failure, possibly only one example of many other similar issues of the same class, something like "tests assume certain features" Relatedly, this method of disabling various default options in openssl, is how a number [1] of issues in the Python cryptography package were found: https://github.com/pyca/cryptography/issues/5065 * Another issue is a build failure with NPN disabled, yet to be reported -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue38815> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38960] DTrace FreeBSD build fix
New submission from Kubilay Kocak : Thank you for the heads-up David. If you need OS support and don't have access to a FreeBSD install, I can provide you with an SSH account to the servers that run the Python buildbots if that would be helpful either now or in the future -- ___ Python tracker <https://bugs.python.org/issue38960> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38744] python 3.8 hang in multiprocessing.Pool() locking on FreeBSD
Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue38744> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38515] regrtest main process timed out after 5 min on AMD64 FreeBSD CURRENT Shared 3.8
Kubilay Kocak added the comment: @Victor The guest running the worker was: - running a FreeBSD build world (-j8)concurrently which is what was creating additional load, though I've done this before and it hasn't caused timeouts. - suspended/resumed (virtualbox save/restore) which may have affected timings -- ___ Python tracker <https://bugs.python.org/issue38515> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37531] Fix regrtest timeout for subprocesses: regrtest -jN --timeout=SECONDS
Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue37531> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38234] The value of Py_SetPath is not used to populate the configuration
Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue38234> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38183] test_idle fails on AMD64 FreeBSD CURRENT Shared 3.x: GetUserCfgDir() fails with PermissionError
Kubilay Kocak added the comment: @Victor Yes. I restarted the worker to re-create reproduction conditions. It looks like default, 3.8 and 3.7 are OK now after Terry;s commits, with 2.7 failing (expected): https://buildbot.python.org/all/#/builders/169/builds/170 It would be nice to fix the bug in all supported branches until they are EoL -- ___ Python tracker <https://bugs.python.org/issue38183> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38183] test_idle fails on AMD64 FreeBSD CURRENT Shared 3.x: GetUserCfgDir() fails with PermissionError
Kubilay Kocak added the comment: Thanks Terry, I've restarted the worker under sudo The following builds are underway: https://buildbot.python.org/all/#/builders/168/builds/1467 (default) https://buildbot.python.org/all/#/builders/212/builds/218 (3.8) https://buildbot.python.org/all/#/builders/173/builds/589 (3.7) -- ___ Python tracker <https://bugs.python.org/issue38183> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38183] test_idle fails on AMD64 FreeBSD CURRENT Shared 3.x: GetUserCfgDir() fails with PermissionError
Kubilay Kocak added the comment: I can restart the worker to create the environment that reproduces the issue at any time to confirm the test passes, just let me know -- ___ Python tracker <https://bugs.python.org/issue38183> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38183] test_idle fails on AMD64 FreeBSD CURRENT Shared 3.x: GetUserCfgDir() fails with PermissionError
Kubilay Kocak added the comment: I've restarted the worker via sudo service(8), which shouldn't have the same (environment) issue as starting the rc script directly under sudo https://buildbot.python.org/all/#/builders/168/builds/1462 is running now Let me know if you need any further information from my end to assist resolution of test_idle under reproduction conditions -- ___ Python tracker <https://bugs.python.org/issue38183> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38183] test_idle fails on AMD64 FreeBSD CURRENT Shared 3.x: GetUserCfgDir() fails with PermissionError
Kubilay Kocak added the comment: This is related to issue 37400 and issue 27838 in that specific invocations of the buildbot service (like via sudo) cause the environment to be setup differently. In this case, I had just started the buildbot worker via sudo prior to the build starting and failing. In the #37400 and #27838 cases (see msg295486), sudo was also used, where HOME ends up being /root, which is not writeable by the user the worker is run under (buildbot). The test should either mock, or should write to a known temp directory (possibly one it creates), either in the build dir, or /tmp or similar, though I'd lean towards keeping all test writes within the scope of the temporary build location I can either 1) if the issue cannot be resolved in short order, restart the worker now to clear the problem, until this issue has a changeset against it to resolve it 2) if it can be resolved in short order, leave the worker in this state until fixed -- ___ Python tracker <https://bugs.python.org/issue38183> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38061] FreeBSD: Optimize subprocess.Popen(close_fds=True) using closefrom()
Kubilay Kocak added the comment: On "close_except", close_range and posix_spawn(close_fds=True), I'll talk to my interested FreeBSD colleagues about potential inroads in that regard. In the meantime, we're good on closefrom(2) anywhere it can be used in Python -- ___ Python tracker <https://bugs.python.org/issue38061> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38061] FreeBSD: Optimize subprocess.Popen(close_fds=True) using closefrom()
Kubilay Kocak added the comment: > Would it be possible to modify FreeBSD to enable it by default? Or is there a > reason to not enable it by default? That's very unlikely to happen. I believe it was added as an opt-in feature for some linux compatibility situations. The correct solution is to use closefrom(2), as it is the optimal current solution, and in our case, safe to use. > Which patch? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221700#c3 or > something else? Yep, that one. > It seems like closefrom() is available on: Per #8052 there was some concerns about closefrom(2) not being async-signal safe. [1] I can't speak to other implementations, but this is what I requested clarity from our FreeBSD developers on, and confirmed that our implementation is indeed safe. That is the reason why I thought scoping closefrom(2) to __FreeBSD__ may be warranted, just like like the linux specific bits in https://hg.python.org/cpython/rev/61aa484a3e54 from #8052 But I'll leave the decision as to how its implemented (configure checkls, ifdef'd or not) in your capable hands. Summary: FreeBSD's closefrom(2) is safe to anywhere in Python where it needs to close a range of fd's, including the subprocess module. [1] https://bugs.python.org/issue8052#msg132307 -- ___ Python tracker <https://bugs.python.org/issue38061> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38061] FreeBSD: Optimize subprocess.Popen(close_fds=True) using closefrom()
Kubilay Kocak added the comment: @Victor I mounted fdescfs on the buildbot workers to make the tests run faster. You're correct that it's not enabled by default. If we could look at the initial support being as simple as possible, we can look to backport this to 2.7 as well -- ___ Python tracker <https://bugs.python.org/issue38061> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38061] FreeBSD: Optimize subprocess.Popen(close_fds=True) using closefrom()
Kubilay Kocak added the comment: We're tracking this in our downstream bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221700 There's a patch there you may base something upstream on Open question: closefrom(2) test in ./configure && ifdef __FreeBSD__ ? -- ___ Python tracker <https://bugs.python.org/issue38061> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot
Kubilay Kocak added the comment: Possibly, but unlikely as the system had been freshly installed and rebooted before the worker was restarted. The worker processes, however, had not been stopped prior to, or during the upgrade, so it's possible that the worker had an inconsistent build state that had resumed, or used before-upgrade information, code or objects during tests -- ___ Python tracker <https://bugs.python.org/issue37959> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot
Kubilay Kocak added the comment: Ran rebuild (in the BB UI) on that failed build (#1356), and test_os now passes: 0:22:52 load avg: 8.38 [339/419] test_os passed Victor independently logged into the host and ran a from scratch build/test and test_os passes for him too (verifying my from scratch test results) Only thing I can think of is a cached/inconsistent BB build environment after the host FreeBSD update, that cleared itself after the first build -- ___ Python tracker <https://bugs.python.org/issue37959> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot
Kubilay Kocak added the comment:
Hmm... a test checkout of master/default on the host in question has
test_copy_file_range{_*} passing:
[user@CURRENT-amd64:/usr/home/user/repos/cpython] ./python -m test -vvv test_os
|grep range
...
test_copy_file_range (test.test_os.FileTests) ... ok
test_copy_file_range_invalid_values (test.test_os.FileTests) ... ok
test_copy_file_range_offset (test.test_os.FileTests) ... ok
...
Ran 280 tests in 2.503s
OK (skipped=45)
--
___
Python tracker
<https://bugs.python.org/issue37959>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot
Kubilay Kocak added the comment: See Also: #26826 -- ___ Python tracker <https://bugs.python.org/issue37959> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37157] shutil: add reflink=False to file copy functions to control clone/CoW copies (use copy_file_range)
Kubilay Kocak added the comment: See Also: #26826 -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue37157> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot
Kubilay Kocak added the comment: Possibly related: https://reviews.freebsd.org/D20584 - Add a linux compatible copy_file_range(2) syscall https://lists.freebsd.org/pipermail/freebsd-current/2019-July/073747.html -- ___ Python tracker <https://bugs.python.org/issue37959> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot
Kubilay Kocak added the comment: @Pablo Upgrade to latest CURRENT revision a few hours ago. Some system software is still updating. I'll push a rebuild on BB once complete. Stand by :) -- ___ Python tracker <https://bugs.python.org/issue37959> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37811] [FreeBSD, OSX] Socket module: incorrect usage of poll(2)
Kubilay Kocak added the comment: See Also: #31334 -- ___ Python tracker <https://bugs.python.org/issue37811> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37811] [FreeBSD, OSX] Socket module: incorrect usage of poll(2)
Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue37811> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37788] fix for bpo-36402 (threading._shutdown() race condition) causes reference leak
Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue37788> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37664] Update bundled pip and setuptools
Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue37664> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37679] test_with_pip fails on FreeBSD 10 bot
Kubilay Kocak added the comment: Since this is likely a regression from issue 37664, which is still open, and also contains the report, I'd close this issue in favour of the former. Having regression reports in separate issues for still open in new/separate issues tends to results in them not being addressed in a timely manner. If it turns out this is not related to the commits from issue 37664, this can be re-opened. Having said that, these bots have been stable and green for a substantial amount of time, so in almost all cases (upgrades to the bots not withstanding), new regressions/failures are almost certainly newly introduced -- resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue37679> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37471] mmap module: add MAP_ALIGNED_SUPER FreeBSD constant
Kubilay Kocak added the comment: Thanks for clarifying Victor -- ___ Python tracker <https://bugs.python.org/issue37471> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37471] mmap module, add MAP_ALIGNED_SUPER FreeBSD constant
Change by Kubilay Kocak : -- title: mmap module, adding new constant -> mmap module, add MAP_ALIGNED_SUPER FreeBSD constant ___ Python tracker <https://bugs.python.org/issue37471> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37471] mmap module, adding new constant
New submission from Kubilay Kocak : Thanks David! Can this be backported to earlier 3.x's and 2.7? -- ___ Python tracker <https://bugs.python.org/issue37471> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37400] test_os: test_chown() started to fail on AMD64 FreeBSD 10-STABLE Non-Debug 3.* buildbots
Kubilay Kocak added the comment: And I just remembered that I had to restart the build worker service on that host (koobs-freebsd10) this morning as I was receiving messaging that the worker had gone missing. I ran `[koobs@10-STABLE-amd64:~] sudo /usr/local/etc/rc.d/buildslave restart` which is the same as the prevailing reproduction case in #27838 I could restart the worker to make the issue go away, but I think the underlying issue should be fixed instead. Should we close this as a dupe and reopen the original? -- ___ Python tracker <https://bugs.python.org/issue37400> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37400] test_os: test_chown() started to fail on AMD64 FreeBSD 10-STABLE Non-Debug 3.* buildbots
Kubilay Kocak added the comment: This looks like a reincarnation of #27838 -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue37400> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36402] threading._shutdown() race condition: test_threading test_threads_join_2() fails randomly
Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue36402> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36624] cleanup the stdlib and tests with regard to sys.platform usage
Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue36624> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34521] Multiple tests (test_socket, test_multiprocessing_*) fail due to incorrect recvmsg(2) buffer lengths, causing failures on FreeBSD CURRENT
Kubilay Kocak added the comment: Access to the buildbot has been restored (a while ago), and this issue being resolved (merge to 2.7) is the only test failing to get 2.7 back to green, which has been failing for months. Can we test with Victors proposed patch in msg330654 ? I don't believe the change/fix/merge will be difficult, given the very small change scope of the master commits. -- ___ Python tracker <https://bugs.python.org/issue34521> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36707] The "m" ABI flag of SOABI for pymalloc is no longer needed
Kubilay Kocak added the comment: Those script names would already have code to handle name changes based on existing abiflags/soabi string (as FreeBSD does), and would be trivial to modify for 'm' removal. For third party stuff: we use setuptools --record for 'everything', so as long as filenames are 'correct' for the files that are actually installed, and downstreams are clear what the scope of the changes are, 'm' removal is not an issue when it come so packaging third party packages/extensions. A new file extension format or substantially more complex magic would be, on the other hand. A new minor is a good time to make these changes, and there's nothing really blocking about a new python38 port/package, and nothing consumes it yet in downstream OS's -- ___ Python tracker <https://bugs.python.org/issue36707> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36707] The "m" ABI flag of SOABI for pymalloc is no longer needed
Kubilay Kocak added the comment:
For FreeBSD Python language ports, the change doesn't have a big negative
impact for the Python language/interpreter ports themselves
We have the following block in lang/python3? ports:
.if ${PORT_OPTIONS:MPYMALLOC}
ABIFLAGS:= m${ABIFLAGS}
.endif
.if ${PORT_OPTIONS:MDEBUG}
ABIFLAGS:= d${ABIFLAGS}
.endif
We then use the variable to substitute the correct suffix into the pkg-plist
items:
.if !empty(ABIFLAGS)
PLIST_FILES+= bin/python${PYTHON_VER}${ABIFLAGS} \
bin/python${PYTHON_VER}${ABIFLAGS}-config \
libdata/pkgconfig/python-${PYTHON_VER}${ABIFLAGS}.pc
${INSTALL_DATA} ${WRKSRC}/Tools/gdb/libpython.py \
${STAGEDIR}${PREFIX}/lib/libpython${PYTHON_VER}${ABIFLAGS}.so.1.0-gdb.py
One question I have is, can/does SOABI flag removal affect any third party
package/extension builds in any way, particularly affecting the names of files
they produce?
We have a ton of python packages/extensions in the ports tree, so anything that
affected their builds, particularly when it comes to setuptools --record output
changes, would be a blocker for supporting 3.8
For example, we had to produce custom ports framework code to account for
PEP488 [1] and PEP3147 [2] filename suffixes, for these filename differences,
which was painful at the time:
# PEP 0488 (https://www.python.org/dev/peps/pep-0488/)
.if ${PYTHON_REL} < 3500
PYTHON_PYOEXTENSION=pyo
.else
PYTHON_PYOEXTENSION=opt-1.pyc
.endif
.if ${PYTHON_REL} >= 3200 && defined(_PYTHON_FEATURE_PY3KPLIST)
# When Python version is 3.2+ we rewrite all the filenames
# of TMPPLIST that end with .py[co], so that they conform
# to PEP 3147 (see https://www.python.org/dev/peps/pep-3147/)
PYMAGICTAG= ${PYTHON_CMD} -c 'import sys;
print(sys.implementation.cache_tag)'
_USES_stage+= 935:add-plist-python
add-plist-python:
@${AWK} '\
/\.py[co]$$/ && !($$0 ~ "/" pc "/") {id = match($$0,
/\/[^\/]+\.py[co]$$/); if (id != 0) {d = substr($$0, 1, RSTART - 1); dirs[d] =
1}; sub(/\.pyc$$/, "." mt "&"); sub(/\.pyo$$/, "." mt "." pyo);
sub(/[^\/]+\.py[co]$$/, pc "/&"); print; next} \
/^@dirrm / {d = substr($$0, 8); if (d in dirs) {print $$0 "/"
pc}; print $$0; next} \
/^@dirrmtry / {d = substr($$0, 11); if (d in dirs) {print $$0
"/" pc}; print $$0; next} \
{print} \
' \
pc="__pycache__" mt="$$(${PYMAGICTAG})" pyo="opt-1.pyc" \
${TMPPLIST} > ${TMPPLIST}.pyc_tmp
@${MV} ${TMPPLIST}.pyc_tmp ${TMPPLIST}
[1] https://www.python.org/dev/peps/pep-0488/
[2] https://www.python.org/dev/peps/pep-3147/
--
___
Python tracker
<https://bugs.python.org/issue36707>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.
Kubilay Kocak added the comment: Again, happy to provide ssh access to the koobs-freebsd-current worker to help analysis, just PM me ssh public keys on IRC (koobs @ #python-dev freenode) -- ___ Python tracker <https://bugs.python.org/issue33608> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35621] asyncio.create_subprocess_exec() only works with main event loop
Change by Kubilay Kocak : -- resolution: fixed -> status: closed -> open ___ Python tracker <https://bugs.python.org/issue35621> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35621] asyncio.create_subprocess_exec() only works with main event loop
Kubilay Kocak added the comment: New buildbot failure on koobs-freebsd10 that appears related to (includes) this changeset Full log attached -- nosy: +koobs Added file: https://bugs.python.org/file48384/koobs-freebsd-10-non-debug-3x-build-1170.txt ___ Python tracker <https://bugs.python.org/issue35621> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36889] Merge StreamWriter and StreamReader into just asyncio.Stream
Kubilay Kocak added the comment: @Andrew That would be great, as having failing buildbots can hide new regressions that end up taking much longer to identify and fix as they are hidden, and is better for you than reverting implementation code -- ___ Python tracker <https://bugs.python.org/issue36889> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36889] Merge StreamWriter and StreamReader into just asyncio.Stream
Kubilay Kocak added the comment: Seeing a test_ayncio failure on koobs-freebsd-current: Timeout (0:25:00)! Thread 0x000800abb000 (most recent call first): File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/selectors.py", line 558 in select File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/asyncio/base_events.py", line 1813 in _run_once File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/asyncio/base_events.py", line 563 in run_forever File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/asyncio/base_events.py", line 595 in run_until_complete File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/test_asyncio/test_streams.py", line 1531 in test_stream_server_abort Some errors (warnings?) later in the re-run (which passes), may be related/indicative: Future exception was never retrieved future: Traceback (most recent call last): File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/asyncio/subprocess.py", line 173, in _feed_stdin await self.stdin.drain() File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/asyncio/streams.py", line 1415, in drain await self._protocol._drain_helper() File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/asyncio/streams.py", line 594, in _drain_helper await waiter BrokenPipeError Full log attached -- nosy: +koobs resolution: fixed -> status: closed -> open Added file: https://bugs.python.org/file48376/koobs-freebsd-current-3.x-build-168.stdio.txt ___ Python tracker <https://bugs.python.org/issue36889> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30458] [security][CVE-2019-9740][CVE-2019-9947] HTTP Header Injection (follow-up of CVE-2016-5699)
Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue30458> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.
Kubilay Kocak added the comment: @Eric Happy to give you SSH access to one of the FreeBSD buildbots that's experienced the crash if it helps. Just flick me a pubkey, I'm on IRC (koobs @ freenode / #python-dev) -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue33608> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36632] test_multiprocessing_forkserver: test_rapid_restart() leaked a dangling process on AMD64 FreeBSD 10-STABLE Non-Debug 3.x
Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue36632> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35755] On Unix, shutil.which() and subprocess no longer look for the executable in the current directory if PATH environment variable is not set
Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker <https://bugs.python.org/issue35755> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
