koobs added the comment:
Adding a patch for reference only
--
keywords: +patch
Added file: http://bugs.python.org/file33902/python-issue6299.patch
___
Python tracker
<http://bugs.python.org/issue6
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue20631>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
Breadcrumb: this was reported against 3.2 and 3.1, but never backported to the
latter.
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue8
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue20246>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by koobs :
--
versions: +Python 3.3, Python 3.4, Python 3.5
___
Python tracker
<http://bugs.python.org/issue20767>
___
___
Python-bugs-list mailin
koobs added the comment:
Details on how clang 3.4 changes behaviour for compiler flags:
http://llvm.org/releases/3.4/tools/clang/docs/ReleaseNotes.html#new-compiler-flags
--
___
Python tracker
<http://bugs.python.org/issue20
koobs added the comment:
Attaching patch against default
--
keywords: +patch
type: -> compile error
Added file: http://bugs.python.org/file34253/python-issue20767.diff
___
Python tracker
<http://bugs.python.org/issu
koobs added the comment:
Can somebody backport the fixes for the test breakages to 3.1 and 3.2 please,
it seems they were forgotten.
The original CVE fix includes changes to test_socket.py so I cant imagine
security-only-fix policy applies.
Thanks
koobs added the comment:
Thank you Stefan
--
___
Python tracker
<http://bugs.python.org/issue20246>
___
___
Python-bugs-list mailing list
Unsubscribe:
koobs added the comment:
Regressions on FreeBSD buildbots (test_coding)
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%2010.0%203.3/builds/626/steps/test/logs/stdio
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue20
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue19966>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue20374>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue20251>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
It would be great if this could make it into 3.4, extended to include other
OS's if necessary at a later date.
--
___
Python tracker
<http://bugs.python.org/is
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue20896>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
3.3 is supported for security related fixes until September 2017 [1], but only
3.4, 3.5 and 2.7 have received the backport, reopen for outstanding merge
[1] https://docs.python.org/devguide/#status-of-python-branches
Update summary to reflect the RedHat CVE that was
Changes by koobs :
--
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issue22928>
___
___
Python-bugs-list mailing list
Unsubscribe:
koobs added the comment:
==
ERROR: test_path_with_null_unicode (test.test_posix.PosixTester)
--
Traceback (most recent call last):
File
"/usr/home/bui
koobs added the comment:
koobs-freebsd{9,10,current) failing after
30099abdb3a46d0e306a4cf995b95fa8cfb8b78a merge to 2.7
--
nosy: +koobs
resolution: fixed ->
status: closed -> open
___
Python tracker
<http://bugs.python.org/i
koobs added the comment:
Thank you Benjamin :)
--
versions: +Python 3.5
___
Python tracker
<http://bugs.python.org/issue24557>
___
___
Python-bugs-list mailin
koobs added the comment:
Also failing on all freebsd buildbots, all tests failing with:
FileNotFoundError: [Errno 2] No such file or directory:
'/usr/share/zoneinfo/Iran'
--
nosy: +koobs
resolution: fixed ->
___
Python t
koobs added the comment:
I can help providing information on the koobs-* freebsd buildbots (I run them).
In a default installation, the timezone entries are available in
/usr/share/zoneinfo (see attachment for contents)
Iran is not in the root directory, 'Tehran' is in Asia/ su
koobs added the comment:
See Also:
non standard (standard?) timezones.
https://lists.freebsd.org/pipermail/freebsd-hackers/2015-May/047765.html
I don't know to what extent these links are considered standard, but I'll talk
to Julian about whether we can get these links installed
koobs added the comment:
koobs-freebsd-* 3.x builds are now passing, but I'd like to make an additional
(trivial) proposal, and that is:
If the tests that were previously failling, aren't *specifically* testing for
'backward compatible' timezone definitions, that the test
koobs added the comment:
@David
The symptoms from FreeBSD look a little different:
Only gethostbyname affected only on 2.7 and 3.3 on all freebsd versions (9, 10,
11).
Python 3.2 was not tested (freebsd port was deleted), but likely affected as
well
Feels/Appears like a gethostbyname fix
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue26662>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
This just failed on 3.x (default) on koobs-freebsd{9,10} bots:
==
FAIL: test_article_head_body (test.test_nntplib.NetworkedNNTP_SSLTests
Changes by koobs :
--
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/issue19613>
___
___
Python-bugs-list mailing list
Unsubscribe:
koobs added the comment:
Forgive me for asking a question that may have already been asked, or beaten to
death, but what is preventing Python from requiring libffi as an
external/required dependency, rather than keeping it and taking on the burden
of fixes/backporting in lieu of updates or
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue26852>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue23968>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
Thank you Alexander, consider me satisfied :)
--
___
Python tracker
<http://bugs.python.org/issue24773>
___
___
Python-bugs-list mailin
koobs added the comment:
Nothing is required (as far as I'm aware) other than commit/merge on a two line
change scoped only to FreeBSD.
The issue was reported for and on FreeBSD and the patch has been carried
locally in all FreeBSD Python ports/packages (2.7, 3.3, 3.4, 3.5) for ove
koobs added the comment:
@Stefan I've notified our FreeBSD Clang/LLVM people of the upstream bug status,
though there are indications that the "-Wl,-rpath" method is considered the
recommended/canonical/future way to do
koobs added the comment:
@Stefan I'll touch base with Antoine (OP) and confirm that this is a
root-cause, permanent solution
--
stage: commit review -> patch review
___
Python tracker
<http://bugs.python.org
koobs added the comment:
Not sure why the stage field changed on last submission. Restore accordingly to
previous state
--
stage: patch review -> commit review
___
Python tracker
<http://bugs.python.org/issu
koobs added the comment:
@Brett / Ned I'm happy to carry the proposed patch in the FreeBSD
ports/packages until the next releases if that helps your confidence levels.
--
versions: +Python 3.5, Python 3.6
___
Python tracker
<http://bugs.py
koobs added the comment:
For posterity, the following failure was observed on all (9/10/11(current)
FreeBSD buildbots:
==
FAIL: testFraction (test.test_statistics.Test_Nth_Root
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue26040>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by koobs :
--
nosy: +koobs
versions: +Python 3.5, Python 3.6
___
Python tracker
<http://bugs.python.org/issue27831>
___
___
Python-bugs-list mailin
koobs added the comment:
This appears to have spontaneously resolved itself after build #957 after many
failures. For reference, other builders on the same host were failing as well:
AMD64 FreeBSD CURRENT Debug 3.5 (#567, #568)
AMD64 FreeBSD CURRENT Non-Debug 3.5 (#8, #9)
And possibly others
koobs added the comment:
These break what was addressed in #11729 for default, 3,x and 3.3.
2.7 seems to have made it through unscathed.
I'm not sure where or how the old code was introduced, but the clang fix has
been upstreamed and is correct in the pure libffi 3.0.13 sources
Failu
koobs added the comment:
heads-up: Tests are still failing on FreeBSD (gcc & clang) buildbots:
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%209.0%20dtrace%202.7/builds/472/steps/test/logs/stdio
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%209.0%20dtrace%2Bclang%2
New submission from koobs:
test_expanduser in test.test_posixpath.PosixPathTest fails when the users $HOME
ends with "/"
==
FAIL: test_expanduser (test.test_posixpath.Pos
koobs added the comment:
There's some work that's been in the FreeBSD bleachers since Jul 2012 to add
futimens() and utimensat(), with some recent activity:
RFC: futimens(2) and utimensat(2) - Jul 2012
http://lists.freebsd.org/pipermail/freebsd-arch/2012-February/012409.html
RFC:
koobs added the comment:
After some sleuthing with Ezio (thank you for the help) and some amateur
debugging, all conditions in expanduser return the the home directory after
stripping trailing slashes.
The assertion in Lib/test/test_posixpath.py:264 compares expanduser(path) with
a path
koobs added the comment:
Ready to confirm on buildbots when this lands
Also, libffi-3.0.13 is installed on my buildbots if you want to use -custom to
have a play, I can be pinged anytime on IRC if I can be of any assistance.
koobs @ #python-dev
koobs added the comment:
I am seeing a similar set of test failures buildbots for 2.7 that are
relatively recent too:
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%209.0%20dtrace%2Bclang%202.7/builds/479/steps/test/logs/stdio
I cant account for test_html_doc failure but I have seen
koobs added the comment:
The attached patch strips the trailing slash from the home directory obtained
from pw_dir in test_expanduser
./python -m test -j3 test_posixpath
[1/1] test_posixpath
1 test OK.
Can someone take care of the commit please, and thank you again Ezio for the
assistance
koobs added the comment:
Thanks Antoine, I'm removing the 'Library' component on this one given the
proposed resolution.
Additionally, given the trivial nature and isolation of the change strictly to
the test, I'd like to request this go into 3.2 as well.
For any futu
koobs added the comment:
Spoil Ezio and learn me some python dev guide conventions, with an updated
patch generated via hg diff, containing a comment, and including a bug #ID
reference
--
Added file: http://bugs.python.org/file30174/test_posixpath_v2.diff
koobs added the comment:
This broke a FreeBSD buildbot (koobs-freebsd10), complete log attached.
--
nosy: +koobs
Added file: http://bugs.python.org/file36893/koobs-freebsd10-build-742.log
___
Python tracker
<http://bugs.python.org/issue13
koobs added the comment:
koobs@10-STABLE-amd64:~ % locale
LANG=
LC_CTYPE="C"
LC_COLLATE="C"
LC_TIME="C"
LC_NUMERIC="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_ALL=
--
__
koobs added the comment:
This change looks to be implicated in a buildbot breakage on koobs-freebsd9
(3.4).
I couldn't reproduce the test failure by re-running the build, so possibly
intermittent or non-deterministic.
Full build log attached.
I'll leave the issue closed for now,
koobs added the comment:
Builds failing on koobs-freebsd9 buildbot for:
3.x: since revision b2c17681404f80edae2ee4846db701104d942cc4
3.4: since revision 246c9570a75798a4757001620cf92cc8d2eba684
Attaching both initial build failure test logs.
--
nosy: +koobs
Added file:
http
koobs added the comment:
koobs-freebsd10 buildbot broken on all branches since:
2.7: e80cb046e7641fb8a71dda8254d2e619cdd64480
3.4: ba4b31ed2952b65ca447f57fbd6d540ebc4b749c
3.x: 3e4f3cc4f1f9dbee8e0ed5df47f77baae2ad310c
Full (2.7) log attached
koobs added the comment:
I only attached the 2.7 build log because the failures from 3.4 and 3.x are
identical, copying them here for completeness:
>From 3.4:
==
ERROR: test_arp_getnode (test.test_uuid.TestU
koobs added the comment:
I don't have the environment to test here. Can you run a custom build on the
buildbots?
--
___
Python tracker
<http://bugs.python.org/is
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue21356>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by koobs :
Added file:
http://bugs.python.org/file37281/koobs-freebsd10-python34-build-598.log
___
Python tracker
<http://bugs.python.org/issue22685>
___
___
koobs added the comment:
Buildbot failures observed on koobs-freebsd9 and koobs-freebsd10 for 3.x and
3.4, respectively.
Both logs are attached, inlined failure below:
==
FAIL: test_pause_reading
koobs added the comment:
@lemburg, does reverting this patch fix the regression for you?
--
nosy: +koobs
type: -> compile error
___
Python tracker
<http://bugs.python.org/issu
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue23085>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue13655>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
FreeBSD buildbots broken since fbe87fb071a67cb5e638b3496362b5aedc0fc9a7
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue22
koobs added the comment:
Oops, incomplete comment, apologies. Just noticed haypo has reported the issue
here already
--
___
Python tracker
<http://bugs.python.org/issue22
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue22947>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by koobs :
--
title: libpython3.so conflicts between $VERSIONs -> altinstall should not
install libpython3.so (conflict between multiple $VERSIONs)
___
Python tracker
<http://bugs.python.org/issu
koobs added the comment:
Adding 3.2 so I (and other downstream packagers) don't forget to backport the
fix.
--
versions: +Python 3.2
___
Python tracker
<http://bugs.python.org/is
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue22176>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue23346>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
7e7c825f75ad832d973542bfcf9ecd6e5dd3f981 broke koobs-freebsd9 and
koobs-freebsd10, with:
==
FAIL: test_main_exception (test.test_timeit.TestTimeit
Changes by koobs :
--
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/issue11578>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue10910>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
New submission from koobs:
test_with_pip fails since revision 0d0989359bbbff9aa502158e362eb298e1a8ba7c
with the following output:
==
FAIL: test_with_pip (test.test_venv.EnsurePipTest
koobs added the comment:
My mistake, revision 1ca30423b0c99c9599d5d4654323eeeae4a03804 or
revision 29b95625a07cc5bb22e260c983500ed9efed67bf
--
___
Python tracker
<http://bugs.python.org/issue24
koobs added the comment:
See also:
Issue 16287 (Solaris)
Issue 15745 (Related to FreeBSD/ZFS, has patch)
3.4 and 3.x are still failing
--
title: Test failure in test_utime on FreeBSD -> Sporadic test_utime() failures
on FreeBSD
___
Python trac
Changes by koobs :
--
components: +Cross-Build
___
Python tracker
<http://bugs.python.org/issue22359>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by koobs :
--
stage: resolved -> needs patch
___
Python tracker
<http://bugs.python.org/issue22359>
___
___
Python-bugs-list mailing list
Unsubscrib
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue22359>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
We've (FreeBSD) seen and received several random and intermittent reports of
failures during this stage of the build for all versions of Python, resulting
in errors such as, among others:
Parser/pgen.o: file not recognized: File truncated
*** [Parser/pgen] Error
koobs added the comment:
martin: yes, if the incorrect usage of recursive make is in the 2.7 and 3.4
branches and the fix is relevant to the issues I reported. Of course all
subsequent changes (fixing cross-builds) should be applied there too
koobs added the comment:
test_utime is now consistently failing on 3.4, 3.5 and default
--
priority: normal -> high
title: Sporadic test_utime() failures on FreeBSD -> Consistent test_utime()
failures on FreeBSD
versions: +Python 3.6
___
koobs added the comment:
I have tested both patches (test_os by trent) and almostequaltime by harrison
on the default branch, and *both* result in test_os passing.
They also resolve the test_utime failure reported in bug 24175 and very likely
16287 (born from this issue)
--
versions
koobs added the comment:
Hmm, that was supposed to be: issue 24175 and very likely issue 16287
--
___
Python tracker
<http://bugs.python.org/issue15745>
___
___
koobs added the comment:
Larry: The same two hosts that the FreeBSD Python buildslaves run on :)
--
___
Python tracker
<http://bugs.python.org/issue15745>
___
___
koobs added the comment:
Additionally on koobs-freebsd9, in my home directory (which is on ZFS)
The buildbot home directories are on UFS
--
___
Python tracker
<http://bugs.python.org/issue15
koobs added the comment:
Can a test be made to show a message (similar to a skipIf reason=) mentioning
that a reduced precision is being used for certain tests?
It would be nice not to have to remember this issue as platform support changes
(reads: improves) over time.
Not withstanding, it&#
Changes by koobs :
--
components: +Build
keywords: +needs review
___
Python tracker
<http://bugs.python.org/issue7352>
___
___
Python-bugs-list mailing list
Unsub
koobs added the comment:
Initial commit to default is done. Backport to 2.7 & 3.4 branches remains to do
--
components: -Cross-Build
keywords: +easy
___
Python tracker
<http://bugs.python.org/iss
koobs added the comment:
Add 3.5 to list of versions merging required for
--
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/issue22359>
___
___
koobs added the comment:
Incorrect recursive use of make will be fixed in default, 3.5, 3.4 (?), 2.7 in
issue 22359, reflect the versions correctly here so they're not forgotten.
--
nosy: +koobs
versions: +Python 2.7, Python 3.4, Pytho
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue13501>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
Observed the following test_smtplib failure on koobs-freebsd10, noting that the
timeout parameter is still 3
test test_smtplib failed -- Traceback (most recent call last):
File
"/usr/home/buildbot/python/2.7.koobs-freebsd10/build/Lib/test/test_smtplib.py&qu
Changes by koobs :
--
keywords: +needs review
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue24520>
___
___
Python-bugs-list mailing list
Unsub
Changes by koobs :
--
components: +Build, Library (Lib)
keywords: +easy, needs review
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue24557>
___
___
koobs added the comment:
One of the FreeBSD buildbots (koobs-freebsd9) just failed on a 2.7 build due to
this issue.
Full log attached, as the bug is intermittent and non-deterministic (though
appears more likely during high build host loads).
This issue no longer 'needs patch' as
New submission from koobs:
3.5.0 rc3 tarballs appear to be missing on:
https://www.python.org/ftp/python/3.5.0/
--
messages: 250159
nosy: koobs
priority: normal
severity: normal
status: open
title: Missing 3.5.0 RC3 tarballs (FTP)
versions: Python 3.5
New submission from koobs:
In my current attempt to create a FreeBSD port for python35, I've come across a
patch rejection for the fcntlmodule.c for a local port patch we've been
carrying since Python 2.6:
https://svnweb.freebsd.org/ports/head/lang/python27/files/patch-Modules__fcn
koobs added the comment:
Thanks for the insight Serhiy. A few questions ..
Is clinic code updated based on *.c declarations at build time? If not when/how
is the best place/method to run this for our ports/package builds?
Does your suggestion to switch unsigned_int to unsigned_long imply that
101 - 200 of 250 matches
Mail list logo
