koobs added the comment:
Attaching an initial patch with the following changes:
- Update comment
- Add original (#1600860) and current issue ID references
- Remove sys.platform conditional
- Remove NOOP sysconfig.get_config_var call (Reported by: birkenfeld)
This results in all platforms
koobs added the comment:
Concur, and then also, why special case linux, gnu and sunos?
The comment is:
# Python's library directory [[must]] be appended to library_dirs (emphasis
mine)
Is the real question then "in what cases should the library path NOT be added?"
?
I also
koobs added the comment:
Confirming identical failures on all branches:
tip: /usr/bin/ld: cannot find -lpython3.4m
3.3: /usr/bin/ld: cannot find -lpython3.3m
3.2: /usr/bin/ld: cannot find -lpython3.2m
3.1: /usr/bin/ld: cannot find -lpython3.1
2.7: /usr/bin/ld: cannot find -lpython2.7
2.6: /usr
koobs added the comment:
Adding reference to failing tests on koobs-freebsd9 and koobs-freebsd10
buildbots:
==
FAIL: test_is_alive_after_fork (test.test_threading.ThreadTests
koobs added the comment:
For reference, this test is successfuly identifying failures on koobs-freebsd
and koobs-freebsd10 buildbots:
==
FAIL: test_is_alive_after_fork (test.test_threading.ThreadTests
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue15018>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue6299>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue11973>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
koobs added the comment:
Antoine, did you see: #18762 ? It references the samee failures on 9.x as well.
Do you want to close this as a dupe, or maintain separate issues for each OS?
--
___
Python tracker
<http://bugs.python.org/issue18
koobs added the comment:
Commit looks good, confirming test suite passing for 3.x, 3.3 and 2.7.on
http://buildbot.python.org/all/buildslaves/koobs-freebsd10
Thank you for picking this up and finishing it off Christian.
--
___
Python tracker
<h
koobs added the comment:
I'm not sure if this issue is/was related, but it seems the commit addressing
#18178 has taken care of the test_finalize_runnning_thread failure.
I note that your description specifies test_finalize_"with_trace", perhaps
suggesting your reproduct
koobs added the comment:
2 more cases seen here:
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%2010.0%203.x/builds/227/steps/test/logs/stdio
Note: cc on FreeBSD 10.0-CURRENT is clang
and here:
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%209.0%20dtrace%2Bclang%203.x
koobs added the comment:
As per our IRC conversation, our 'koobs-freebsd10' bot also reproduces the
failure and can be used to test the patch.
--
___
Python tracker
<http://bugs.python.o
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue16463>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
koobs added the comment:
I've added a new FreeBSD 10.0-CURRENT buildbot to the pool (thanks antoine)
that reproduces the issue and should provide sufficient coverage for testing
the proposed patch:
http://buildbot.python.org/all/buildslaves/koobs-freebsd10
I'll upgrade the FreeBS
koobs added the comment:
I recently updated the buildbot host to the latest 9-STABLE sources (changeset
delta is approximately 4-6 weeks)
On a hunch I asked our src committers if there had been any sendfile related
changes and was pointed to 3 changesets that were merged from current (MFC) to
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue18296>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
koobs added the comment:
Apologies for the noise Terry, rebuilding passes.
Unsetting versions: 3.3
Is the failure on the build I reported worth opening an issue for?
--
versions: -Python 3.3
___
Python tracker
<http://bugs.python.org/issue16
koobs added the comment:
Commit to 3.3 broke at least my FreeBSD buildbot:
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%209.0%20dtrace%203.3/builds/641/steps/test/logs/stdio
Also setting +Version: Python 3.3 on this.
--
nosy: +koobs
versions: +Python 3.3
koobs added the comment:
I'm happy to move them back upon request, or create a FreeBSD/ZFS buildslave
specially for the job, just let me know.
--
___
Python tracker
<http://bugs.python.org/is
koobs added the comment:
I've moved both of the FreeBSD buildbot slaves off their ZFS-backed home
directories and back to good old UFS.
I want to ensure FreeBSD support continues to improve, and having slaves get
noticed when they fail or regress with ongoing development is a big pa
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:
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:
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:
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:
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:
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:
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:
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:
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
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:
Thanks for the quick response. I'd be happy for it to be FreeBSD
conditional/specific if that's more suitable, safer?
Having said that, our buildbot OS coverage is pretty good, no?
--
___
Python trac
koobs added the comment:
Stefan, can we merge this to the 2.7 branch as well please?
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%209.0%20dtrace%2Bclang%202.7/builds/308/steps/compile/logs/stdio
--
nosy: +koobs
___
Python tracker
<h
koobs added the comment:
This was noted by Dmitry Sivachenko during tests of my python33 port for
FreeBSD, with the following commits going to HEAD (CURRENT) and RELENG_9
(9-STABLE) respectively:
http://svnweb.freebsd.org/base?view=revision&revision=243032
http://svnweb.freebsd.org/base?
koobs added the comment:
I have just upgraded the buildbot host to FreeBSD 9.1-RELEASE and cannot see
failures in the 3.x and 3.3 branches over the last couple of builds.
I have been unable to isolate the commit that fixed it, but the relevant
revision log is here if anybody wants to cast an
koobs added the comment:
Give me till the end of the weekend, will ping you for the skipIf then if I
haven't made progress. Thank you again.
--
___
Python tracker
<http://bugs.python.org/is
koobs added the comment:
I'll take care of upstream and report back with PR numbers. Happy with the
skipIf until resolved. Thanks for your time and patience jcea, much appreciated.
--
___
Python tracker
<http://bugs.python.org/is
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue16605>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
koobs added the comment:
Confirming successful 2.7 build post Victors commit on both buildbots (standard
& clang)
--
___
Python tracker
<http://bugs.python.org/iss
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue15599>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
koobs added the comment:
I think this needs a backport to 2.7, my FreeBSD buildbots are failing on that
branch since moving buildbots home directory onto a ZFS fs:
==
ERROR: test_chflags (test.test_posix.PosixTester
koobs added the comment:
Correction, the PR mentioned in the previous comment has been submitted for
devel/libffi in the FreeBSD ports tree (update from 3.0.9 -> 3.0.11), not
lang/python27
--
___
Python tracker
<http://bugs.python.org/issu
koobs added the comment:
This is also an issue for clang builds of Python on FreeBSD and results in the
_ctypes extension failing to compile (See: koobs-freebsd-clang buildbot)
The original mozilla patch (see References below) did not make it into the
libffi 3.0.11 release, which has already
koobs added the comment:
Back to green for all branches on FreeBSD, thank you Victor
--
___
Python tracker
<http://bugs.python.org/issue16218>
___
___
Python-bug
koobs added the comment:
If there's not another revision of the test patch in the wings, can
56df0d4f0011 also be applied to 3.3, as tests are still failing on at least
koobs-freebsd and koobs-freebsd-clang buildbots.
--
nosy: +koobs
___
P
koobs added the comment:
Incase it helps at all, I'm seeing the test failure preparing for adding
python33 to the FreeBSD ports tree.
On FreeBSD 9.0-RELEASE-p3 (amd64), with /etc/hosts configured as follows:
::1 localhost.domain localhost
127.
koobs added the comment:
uname -rs: FreeBSD 9.0-RELEASE-p3 (AMD64)
python -V: Python 2.7.3
`python readline.py:
read : ['oink', 'oink']
readlines: ['oink\n', 'oink\n']
readline :
Without the patch:
read : []
readlines: []
readline :
Is the
koobs added the comment:
FYI, Added two FreeBSD based buildslaves to the cluster not long ago, one is
dedicated to python+CLANG
http://buildbot.python.org/all/buildslaves/koobs-freebsd-clang
--
nosy: +koobs
___
Python tracker
<h
koobs added the comment:
And to clarify the no-follow-symlinks case on FreeBSD:
extattr_{get,set,list,delete}_link "system calls behave in the same way as
their _file counterparts, except that they do not follow sym-links." as per the
koobs added the comment:
FreeBSD (at least on 7.x, 8.x and 9.x) has the following syscalls available in
its API:
extattr_{get,set,list,delete}_{fd,file,link}
And also has: EXTATTR_MAXNAMELEN
http://www.freebsd.org/cgi/man.cgi?query=extattr&sektion=2&manpath=FreeBSD+9.0
201 - 250 of 250 matches
Mail list logo
