So, first question (and I ask it only b/c I've done it myself many
times) are you sure you've done make install for your proto area.
Right now, once a depo fails to shut down, as happened prior to test
TestApiSearchMulti.test_bug_2955 that's basically game over until Dan's
test improvements get back.
I'd also suggest setting PRIVATE_BUILD=1 in your environment as this
makes sure the paths given in any stack trace is correct.
Other than that, I'll admit I'm a little stumped by the versioning problem.
Interestingly, when I try to run coverage, I get:
/export/home/bpytlik/IPS/bug-13059/proto/root_i386/usr/lib/python2.6/vendor-packages/coverage/collector.py:7:
RuntimeWarning: Python C API version mismatch for module
coverage.tracer: This Python has API version 1012, module
coverage.tracer has version 1013.
from coverage.tracer import Tracer
Traceback (most recent call last):
File "run.py", line 52, in ?
import cli.testutils
File "./cli/testutils.py", line 45, in ?
from pkg.misc import EmptyI
File
"/export/home/bpytlik/IPS/bug-13059/proto/root_i386/usr/lib/python2.6/vendor-packages/pkg/misc.py",
line 30, in ?
import hashlib
ImportError: No module named hashlib
So perhaps there's something to be worked out here?
Brock
Drew Fisher wrote:
I'm seeing some version mismatch stuff, but I have my PYTHONPATH set
to the proto area. I don't understand why the coverage stuff seems to
ignore this.
[r...@xvm-4200m2-01 vendor-packages] # env
TERM=xterm
SHELL=/usr/bin/bash
SSH_CLIENT=172.20.24.132 51691 22
OLDPWD=/export/home/ips/src/tests
SSH_TTY=/dev/pts/1
USER=root
PAGER=less
MAIL=/var/mail/root
PATH=/usr/bin:/usr/sbin:/usr/ccs/bin:/opt/SunStudioExpress/bin
PWD=/export/home/ips/proto/root_i386/usr/lib/python2.6/vendor-packages
PACKAGE_MANAGER_ROOT=/export/home/ips/proto/root_i386/
LANG=C
WS=/export/home/ips
TZ=US/Mountain
PS1=[\[\033[0;31m\...@\[\033[0;36m\]\h\[\033[00m\]
\[\033[0;33m\]\W\[\033[00m\]] #
SHLVL=1
HOME=/root
PYTHONPATH=/export/home/ips/proto/root_i386/usr/lib/python2.6/vendor-packages
LOGNAME=root
SSH_CONNECTION=172.20.24.132 51691 10.10.46.29 22
_=/usr/bin/env
I have attached the entire output from ./run.py -c
-Drew
On 01/12/10 10:18, Danek Duvall wrote:
Drew Fisher wrote:
Are there any extra steps or packages needed to get the coverage flag
to not generate a ton of errors?
./run.py -c
<snip>
FAILED (successes=79, failures=66, errors=281, mismatches=347)
This is a fresh build of the gate with a make clobber ; make ; make
packages done first.
Make sure you're running as root; there are a lot of "pkg verify" calls
which expect filesystem objects to be installed as root/bin.
If that's not the issue, then some samples of what errors you're running
into (use the -v flag to see them as they happen) would help diagnose
what's going on.
Danek
------------------------------------------------------------------------
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
