My guess is that you pulled down the new test but forgot to install the
new version of pkgtarfile.py in your proto area.  If you run a make
install and then re-run the api-complete.py, do you still get the error?

-j

On Tue, Mar 04, 2008 at 08:21:42PM -0600, Shawn Walker wrote:
> On Tue, Mar 4, 2008 at 8:02 PM,  <[EMAIL PROTECTED]> wrote:
> > Author: johansen <[EMAIL PROTECTED]>
> >  Repository: /hg/pkg/gate
> >  Latest revision: ca9993d3aaea618a4d9979b98ee5aecfe91cb38f
> >  Total changesets: 1
> >  Log message:
> >  440 pkgtarfile doesn't prevent tarfile ignoring real errors
> >
> >
> >  Files:
> >         create: src/tests/api/t_pkgtarfile.py
> >         update: src/modules/pkgtarfile.py
> >         update: src/tests/api-complete.py
> 
> This change broke "make test" for me:
> 
> ...............................................................F............................
> ======================================================================
> FAIL: testerrorlevelIsCorrect (api.t_pkgtarfile.TestPkgTarFile)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/export/home/swalker/devel/pkg/src/tests/api/t_pkgtarfile.py",
> line 69, in testerrorlevelIsCorrect
>     extractpath)
> AssertionError: IOError not raised
> 
> ----------------------------------------------------------------------
> 
> Thoughts?
> 
> -- 
> Shawn Walker, Software and Systems Analyst
> http://binarycrusader.blogspot.com/
> 
> "To err is human -- and to blame it on a computer is even more so." -
> Robert Orben
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to