Your message dated Fri, 22 Jun 2018 22:43:38 -0700
with message-id <[email protected]>
and subject line Re: Bug#900459: dask: Debci regression
has caused the Debian Bug report #900459,
regarding dask: Debci regression
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
900459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900459
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: dask
Version: 0.17.4-1
User: [email protected]
Usertags: regression
Hi Maintainer
Since the upload of 0.17.4-1, dask has been failing its own
autopkgtest [1] with the following error:
________________ ERROR collecting dask/bytes/tests/test_http.py ________________
ImportError while importing test module
'/usr/lib/python3/dist-packages/dask/bytes/tests/test_http.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/dask/bytes/tests/test_http.py:3: in <module>
import requests
E ModuleNotFoundError: No module named 'requests'
!!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection !!!!!!!!!!!!!!!!!!!!
Regards
Graham
[1] https://ci.debian.net/packages/d/dask/unstable/amd64/
--- End Message ---
--- Begin Message ---
Source: dask
Version: 0.17.5-2
On Fri, 2018-06-22 at 07:52 +0200, Matthias Klose wrote:
> Control: severity -1 important
> Control: tags -1 sid buster
>
> ping? it's almost a month. and the distutils issues were sorted out
> within a few
> days.
Hello,
Thank you for reminding me be about this. I got distracted with other
problems.
I pushed the fixes for 0.17.5 for the really obvious CI failure
reported in this bug..
(apparently pbuilder's autopkgtests runner isn't as clean of a state as
it should be).
There is another later problem where the CI tests have a non-zero exit,
due to a resource cleanup problem (Though py.test has already reported
its banner saying all tests passed).
Diane
--- End Message ---
_______________________________________________
Python-modules-team mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
