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:
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:
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:
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
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:
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
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
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:
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
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:
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:
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:
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
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue11973>
___
___
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/issue15018>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
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
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:
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
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:
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:
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:
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.
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue17975>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue20210>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
Confirming that altinstall installs libpython3.so
--
___
Python tracker
<http://bugs.python.org/issue17975>
___
___
Python-bugs-list m
koobs added the comment:
These are a good step toward bringing the otherwise neglected Python build
system back to the real world in terms of standard functionality, and will
among other things, make life an absolute pleasure for downstreams and users
alike.
"User-Serviceable" o
koobs added the comment:
More precisely:
Python 3.3 fails at anything > -j1 (switching to gmake makes this go away)
Python 3.4 has not failed up to -j8 (with bsd make)
--
___
Python tracker
<http://bugs.python.org/issu
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue21082>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
New submission from koobs:
python-3.4.0-docs-pdf-letter.{zip,tar.bz2}
python-3.4.0-docs-pdf-letter.{zip,tar.bz2}
are missing from:
https://www.python.org/ftp/python/doc/3.4.0/
/current/ also still points to 3.3.x documentation:
https://www.python.org/ftp/python/doc/current
koobs added the comment:
Missing files was supposed to read:
python-3.4.0-docs-pdf-a4.{zip,tar.bz2}
python-3.4.0-docs-pdf-letter.{zip,tar.bz2}
python-3.4.0-docs-epub.{zip,tar.bz2}
--
___
Python tracker
<http://bugs.python.org/issue21
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue20397>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
Uploading gdb output at Victors request
--
nosy: +koobs
Added file: http://bugs.python.org/file34749/gdb.log
___
Python tracker
<http://bugs.python.org/issue21
koobs added the comment:
Interestingly, I note the following lines from the gdb log:
#5 0x000801ae1e99 in PyModule_Create2 () from
/usr/local/lib/libpython3.4m.so.1
#6 0x000801840de8 in PyInit__heapq () from
/usr/local/lib/python3.4/lib-dynload/_heapq.so
I had installed Python 3.4
koobs added the comment:
Clarification:
a) I had just installed Python 3.4 (at the system level, via ports)
a) Removing Python 3.4 from the system and (forcing a rebuild of the buildbot)
makes the issue go away.
--
___
Python tracker
<h
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue20128>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue20123>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
koobs-freebsd9 (3.4) buildbot has also been failing for a while on what seems
to be this changeset:
==
ERROR: test_synopsis_sourceless (test.test_pydoc.PydocDocTest
koobs added the comment:
test_synopsis_sourceless is also failing on koobs-freebsd9 (3.4) and has been
for a while. Failing test inlined here, for full buildlog, see msg215997 in
#20123
==
ERROR: test_synopsis_sourceless
koobs added the comment:
Updating versions to match branches fix was committed in
--
nosy: +koobs
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issue20
koobs added the comment:
I'd like to put the buildbot slave instances back onto ZFS for broader Disk/IO
test coverage for Python and other projects as well as to gain some
administrative disk utilisation flexibility.
These two issues have unfortunately precluded that, and there's
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:
Back to green for all branches on FreeBSD, thank you Victor
--
___
Python tracker
<http://bugs.python.org/issue16218>
___
___
Python-bug
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:
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:
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
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:
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/issue16605>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
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
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 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:
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:
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:
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:
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:
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:
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
New submission from koobs:
Test failure observed on koobs-freebsd9 on default branch with changeset:
220b34cbd711c28938ea5d980636202c51ab1fbb
Subsequent forced rebuild succeeded with no failure.
==
FAIL: test_with_statement
koobs added the comment:
Tests fail for 2.7 on the koobs-freebsd9 and koobs-freebsd10 buildbots since
a9f967c8d002db364021a5fb1c9926a27029e849
Taking a snapshot of the output here for reference:
test_aifc
test test_aifc produced unexpected output
koobs added the comment:
There are 5 unique test failures that have come up in the koobs-freebsd*
buildbots post the test_asyncio import. Would we prefer to create a meta issue
to track them, or put them here?
--
nosy: +koobs
___
Python tracker
Changes by koobs :
Added file:
http://bugs.python.org/file32166/koobs-freebsd10-amd64-py3x-build588.log
___
Python tracker
<http://bugs.python.org/issue19030>
___
___
koobs added the comment:
Multiple test_pydoc failures found on koobs-freebsd* buildbots after
39b06c3fbe2e6ef78a540513d4b81f2d095d1e62
Attaching complete logs from both bots to this issue, will reference #16938 as
well
--
nosy: +koobs
Added file:
http://bugs.python.org/file32165
koobs added the comment:
Some test failures have cropped, I have attached buildbot logs and referenced
them in #19030
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue16
Changes by koobs :
Added file: http://bugs.python.org/file32199/koobs-freebsd9-py3x-build180.log
___
Python tracker
<http://bugs.python.org/issue19262>
___
___
Python-bug
koobs added the comment:
Summary of 4 test failures below, will attach the complete buildbot logs for
detail.
==
FAIL: test_call_later (test.test_asyncio.test_events.SelectEventLoopTests
Changes by koobs :
Added file: http://bugs.python.org/file32200/koobs-freebsd9-py3x-build182.log
___
Python tracker
<http://bugs.python.org/issue19262>
___
___
Python-bug
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue13405>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
Marc, you just reminded me I need to ask antoine to re-create the custom DTrace
builder that passes --with-dtrace, thanks :)
I've been keeping both of the FreeBSD (9.x and 10.x) buildslaves as close to
HEAD as possible with frequent world updates, which have
koobs added the comment:
antoine, is it possible test/pass --with-dtrace on a buildbot without including
it in the master build configuration?
If not, I'm happy to create a special (dedicated) slave for Jesús so he can
continue to test his branch at leisure without messing up the exi
koobs added the comment:
@Guido, another expected delay test failure:
==
FAIL: test_run_until_complete
(test.test_asyncio.test_events.KqueueEventLoopTests
koobs added the comment:
This also affects Python 2.7 / 3.1 on FreeBSD 10.x with CC=clang
Referencing the PR here: http://www.freebsd.org/cgi/query-pr.cgi?pr=182952
Would like to see the commit backported as well.
--
nosy: +koobs
___
Python tracker
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue969718>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
_curses and _curses_panel fail to build after this commit on koobs-freebsd10
buildslave, with some lovely clang warnings too.
Attaching full log here.
--
nosy: +koobs
Added file: http://bugs.python.org/file32217/koobs-freebsd10-py3x-build-610.log
koobs added the comment:
You rock Antoine.
--
___
Python tracker
<http://bugs.python.org/issue19305>
___
___
Python-bugs-list mailing list
Unsubscribe:
koobs added the comment:
@Ethan, not sure if you've already seen them, but there are 4 pydoc failures
since 2f09a6980e1a
Attaching another complete log from build #245 on the koobs-freebsd9 buildslave
here for posterity
--
Added file: http://bugs.python.org/file32275/koobs-fre
koobs added the comment:
The original report and build logs were attached to the original issue covering
the import of asyncio: #19262
Also attaching here.
--
nosy: +koobs
Added file: http://bugs.python.org/file32294/koobs-freebsd9-py3x-build180.log
koobs added the comment:
@antoine, would love some direction/guidance on ways to isolate.
For what it's worth, the incidence of this failure dropped sharply over the
subsequent 24 hours after the initial report. Could the relaxation of the
timers in 042deeeb703 have had an effect?
Thu
koobs added the comment:
Correct changeset ID: e042deeeb703
--
___
Python tracker
<http://bugs.python.org/issue19334>
___
___
Python-bugs-list mailing list
Unsub
New submission from koobs:
At Christians request:
RLIMIT_SBSIZE
The maximum size (in bytes) of socket buffer usage for
this user. This limits the amount of network memory, and
hence the amount of mbufs, that this user may hold at any
time.
RLIMIT_SWAP
The maximum size (in bytes) of the swap
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue19554>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
I'm not sure how I missed this, but our FreeBSD ports that build out-of-tree
required adding a local patchthat reverts the Makefile.pre.in change in
ab6ab44921b2 when we updated each port to the latest releases of 2.7, 3.2 and
3.3:
https://svnweb.freebsd.org/
koobs added the comment:
2.7 builds are failing on koobs-freebsd9 buildbot since ba7d53b5f3de
test_multiprocessing
[74777 refs]
test test_multiprocessing failed -- Traceback (most recent call last):
File
"/usr/home/buildbot/python/2.7.koobs-freebsd9/build/Lib
koobs added the comment:
koobs-freebsd10 (2.7) is also seeing identical test failures since the change
(slightly more intermittent than freebsd9)
Is the increased sleep period now bumping against a test timing threshold (0.2
koobs added the comment:
@Richard, reporting all green on koobs-freebsd{9,10} 2.7 since 086865ceefe1
Thank you! :)
--
___
Python tracker
<http://bugs.python.org/issue19
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue19757>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
Is this similar/related to #15745?
I took both of my buildbots (koobs-freebsd9, koobs-freebsd10) off ZFS until it
could be resolved
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue19
koobs added the comment:
Sorry Claudiu I missed the issue reference in your comment
--
___
Python tracker
<http://bugs.python.org/issue19838>
___
___
Python-bug
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue18885>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue21704>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue20981>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
Thank you for taking care of this Charles-François :) Requesting backport to
3.3 and 2.7 too please, both are open for fixes.
--
___
Python tracker
<http://bugs.python.org/issue19
koobs added the comment:
Updating versions to reflect branch changes. Will come in handy for those
tracking for manual packaging backports
--
versions: +Python 2.7, Python 3.5 -Python 3.3
___
Python tracker
<http://bugs.python.org/issue19
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue11445>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
David, reproducible on 3.4 and default?
We can use Version to reflect where changes need to be committed
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue17
koobs added the comment:
:DDD
This was an awesome experience working with you Ned, thanks for all the help.
Attaching my debugging & isolation steps for additional detail, posterity and
reference.
--
Added file:
http://bugs.python.org/file36356/python-buildbot-broken-debugging
koobs added the comment:
For reference and breadcrumbs, this also occurs when:
checking for sem_open... yes
checking for sem_timedwait... yes
checking for sem_getvalue... yes
checking for sem_unlink... yes
checking whether POSIX semaphores are enabled... no
checking for broken sem_getvalue
koobs added the comment:
See also:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192365
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue17
koobs added the comment:
The issue applies and is reproducible for all versions 2.6 through 3.5.
This is the changeset we applied to all FreeBSD Ports to fix the issue:
https://svnweb.freebsd.org/ports?view=revision&revision=326729
One specific example (Python 3.3):
1) Use CPPFLAGS
koobs added the comment:
Setting versions to correctly reflect those affected.
--
versions: +Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python
3.5
___
Python tracker
<http://bugs.python.org/issue6
1 - 100 of 250 matches
Mail list logo
