Bug#769250: python-dugong: FTBFS in jessie/i386: dh_auto_test: pybuild --test -i python{version} -p 3.4 --dir . returned exit code 13

2014-11-15 Thread Julien Cristau
On Wed, Nov 12, 2014 at 14:47:41 -0800, Nikolaus Rath wrote:

 On 11/12/2014 10:42 AM, Andrey Rahmatullin wrote:
  On Wed, Nov 12, 2014 at 11:22:55AM +0100, Lucas Nussbaum wrote:
  === FAILURES 
  ===
  _ test_httpcat 
  _
  Traceback (most recent call last):
File /«BUILDDIR»/python-dugong-3.3+dfsg/test/test_examples.py, line 
  53, in test_httpcat
  subprocess.check_call(cmdline, stdout=devnull)
File /usr/lib/python3.4/subprocess.py, line 561, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['/usr/bin/python3.4', 
  '/«BUILDDIR»/python-dugong-3.3+dfsg/test/../examples/httpcat.py', 
  'http://docs.oracle.com/javaee/7/firstcup/doc/creating-example.htm']' 
  returned non-zero exit status 1
  - Captured stderr call 
  -
  301 Moved Permanently
  If it accesses the network it's wrong anyway.
 
 It tries to access the network, and if it fails, the test is skipped.
 
It shouldn't even try.

Cheers,
Julien


signature.asc
Description: Digital signature


Bug#769250: python-dugong: FTBFS in jessie/i386: dh_auto_test: pybuild --test -i python{version} -p 3.4 --dir . returned exit code 13

2014-11-12 Thread Lucas Nussbaum
Source: python-dugong
Version: 3.3+dfsg-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141112 qa-ftbfs
Justification: FTBFS in jessie on i386

Hi,

During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
 make[1]: Entering directory '/«BUILDDIR»/python-dugong-3.3+dfsg'
 dh_auto_build
 I: pybuild base:170: /usr/bin/python3 setup.py build 
 running build
 running build_py
 creating 
 /«BUILDDIR»/python-dugong-3.3+dfsg/.pybuild/pythonX.Y_3.4/build/dugong
 copying ./dugong/__init__.py - 
 /«BUILDDIR»/python-dugong-3.3+dfsg/.pybuild/pythonX.Y_3.4/build/dugong
 # Build docs
 python3 setup.py build_sphinx
 running build_sphinx
 creating /«BUILDDIR»/python-dugong-3.3+dfsg/doc/doctrees
 creating /«BUILDDIR»/python-dugong-3.3+dfsg/doc/html
 Running Sphinx v1.2.3
 loading pickled environment... failed: [Errno 2] No such file or directory: 
 '/«BUILDDIR»/python-dugong-3.3+dfsg/doc/doctrees/environment.pickle'
 loading intersphinx inventory from ../debian/python.inv...
 building [html]: targets for 7 source files that are out of date
 updating environment: 7 added, 0 changed, 0 removed
 reading sources... [ 14%] api
 reading sources... [ 28%] coroutines
 reading sources... [ 42%] index
 reading sources... [ 57%] intro
 reading sources... [ 71%] issues
 reading sources... [ 85%] tutorial
 reading sources... [100%] whatsnew
 
 looking for now-outdated files... none found
 pickling environment... done
 checking consistency... done
 preparing documents... done
 writing output... [ 14%] api
 writing output... [ 28%] coroutines
 writing output... [ 42%] index
 writing output... [ 57%] intro
 writing output... [ 71%] issues
 writing output... [ 85%] tutorial
 writing output... [100%] whatsnew
 
 writing additional files... genindex search
 copying static files... done
 copying extra files... done
 dumping search index... done
 dumping object inventory... done
 build succeeded.
 make[1]: Leaving directory '/«BUILDDIR»/python-dugong-3.3+dfsg'
dh_auto_test -O--buildsystem=pybuild
 I: pybuild base:170: cd 
 /«BUILDDIR»/python-dugong-3.3+dfsg/.pybuild/pythonX.Y_3.4/build; python3.4 -m 
 pytest /«BUILDDIR»/python-dugong-3.3+dfsg/test/
 = test session starts 
 ==
 platform linux -- Python 3.4.2 -- py-1.4.25 -- pytest-2.6.3 -- 
 /usr/bin/python3.4
 collecting ... collected 106 items
 
 ../../../test/test_aio.py::test_aio_future PASSED
 ../../../test/test_dugong.py::test_connect_ssl SKIPPED
 ../../../test/test_dugong.py::test_invalid_ssl SKIPPED
 ../../../test/test_dugong.py::test_get_pipeline[plain] PASSED
 ../../../test/test_dugong.py::test_ssl_info[plain] PASSED
 ../../../test/test_dugong.py::test_blocking_send[plain] PASSED
 ../../../test/test_dugong.py::test_blocking_read[plain] PASSED
 ../../../test/test_dugong.py::test_discard[plain] PASSED
 ../../../test/test_dugong.py::test_discard_chunked[plain] PASSED
 ../../../test/test_dugong.py::test_read_text[plain] PASSED
 ../../../test/test_dugong.py::test_read_text2[plain] PASSED
 ../../../test/test_dugong.py::test_read_text3[plain] PASSED
 ../../../test/test_dugong.py::test_read_identity[plain] PASSED
 ../../../test/test_dugong.py::test_exhaust_buffer[plain] PASSED
 ../../../test/test_dugong.py::test_full_buffer[plain] PASSED
 ../../../test/test_dugong.py::test_readinto_identity[plain] PASSED
 ../../../test/test_dugong.py::test_read_chunked[plain] PASSED
 ../../../test/test_dugong.py::test_read_chunked2[plain] PASSED
 ../../../test/test_dugong.py::test_readinto_chunked[plain] PASSED
 ../../../test/test_dugong.py::test_double_read[plain] PASSED
 ../../../test/test_dugong.py::test_read_raw[plain] PASSED
 ../../../test/test_dugong.py::test_abort_read[plain] PASSED
 ../../../test/test_dugong.py::test_abort_co_read[plain] PASSED
 ../../../test/test_dugong.py::test_abort_write[plain] PASSED
 ../../../test/test_dugong.py::test_write_toomuch[plain] PASSED
 ../../../test/test_dugong.py::test_write_toolittle[plain] PASSED
 ../../../test/test_dugong.py::test_write_toolittle2[plain] PASSED
 ../../../test/test_dugong.py::test_write_toolittle3[plain] PASSED
 ../../../test/test_dugong.py::test_put[plain] PASSED
 ../../../test/test_dugong.py::test_put_separate[plain] PASSED
 ../../../test/test_dugong.py::test_100cont[plain] PASSED
 ../../../test/test_dugong.py::test_100cont_2[plain] PASSED
 ../../../test/test_dugong.py::test_100cont_3[plain] PASSED
 ../../../test/test_dugong.py::test_aborted_write1[plain] PASSED
 ../../../test/test_dugong.py::test_aborted_write2[plain] PASSED
 ../../../test/test_dugong.py::test_tunnel[plain] PASSED
 ../../../test/test_dugong.py::test_read_toomuch[plain] PASSED
 ../../../test/test_dugong.py::test_read_toolittle[plain] PASSED
 ../../../test/test_dugong.py::test_empty_response[plain] PASSED
 ../../../test/test_dugong.py::test_head[plain] PASSED
 

Bug#769250: python-dugong: FTBFS in jessie/i386: dh_auto_test: pybuild --test -i python{version} -p 3.4 --dir . returned exit code 13

2014-11-12 Thread Andrey Rahmatullin
On Wed, Nov 12, 2014 at 11:22:55AM +0100, Lucas Nussbaum wrote:
  === FAILURES 
  ===
  _ test_httpcat 
  _
  Traceback (most recent call last):
File /«BUILDDIR»/python-dugong-3.3+dfsg/test/test_examples.py, line 53, 
  in test_httpcat
  subprocess.check_call(cmdline, stdout=devnull)
File /usr/lib/python3.4/subprocess.py, line 561, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['/usr/bin/python3.4', 
  '/«BUILDDIR»/python-dugong-3.3+dfsg/test/../examples/httpcat.py', 
  'http://docs.oracle.com/javaee/7/firstcup/doc/creating-example.htm']' 
  returned non-zero exit status 1
  - Captured stderr call 
  -
  301 Moved Permanently
If it accesses the network it's wrong anyway.

-- 
WBR, wRAR


signature.asc
Description: Digital signature


Bug#769250: python-dugong: FTBFS in jessie/i386: dh_auto_test: pybuild --test -i python{version} -p 3.4 --dir . returned exit code 13

2014-11-12 Thread Nikolaus Rath
On 11/12/2014 10:42 AM, Andrey Rahmatullin wrote:
 On Wed, Nov 12, 2014 at 11:22:55AM +0100, Lucas Nussbaum wrote:
 === FAILURES 
 ===
 _ test_httpcat 
 _
 Traceback (most recent call last):
   File /«BUILDDIR»/python-dugong-3.3+dfsg/test/test_examples.py, line 53, 
 in test_httpcat
 subprocess.check_call(cmdline, stdout=devnull)
   File /usr/lib/python3.4/subprocess.py, line 561, in check_call
 raise CalledProcessError(retcode, cmd)
 subprocess.CalledProcessError: Command '['/usr/bin/python3.4', 
 '/«BUILDDIR»/python-dugong-3.3+dfsg/test/../examples/httpcat.py', 
 'http://docs.oracle.com/javaee/7/firstcup/doc/creating-example.htm']' 
 returned non-zero exit status 1
 - Captured stderr call 
 -
 301 Moved Permanently
 If it accesses the network it's wrong anyway.

It tries to access the network, and if it fails, the test is skipped.

In this case, it seems that the first attempt to connect succeeded with
status 200, so the test was run. Maybe urllib.request implicitly follows
the 301, I'll look into that.


Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org