Update 2: elpy-promise-wait-should-return-early-for-resolved-promise
fails 30% to 40% of the time in an schroot with Python 3.6.7rc1 as
/usr/bin/python3. I changed the symlink to point to
/usr/bin/python3.7 (Python 3.7.1rc1) and this test passed 100% of the
time. I ran the test 50 times.
I
Update: I just tried packaging elpy-1.2.5 and
`elpy-promise-wait-should-return-early-for-resolved-promise` failed in
4/10 builds (failed on 1,3,6,9). So something changed in sid between
the 4th of September and now. On the upside, this means I will be
able to get a debug shell tomorrow and
Control: forwarded -1 https://github.com/jorgenschaefer/elpy/issues/1477
Hi Helmut,
On Thu, Oct 04, 2018 at 07:34:31PM +0200, Helmut Grohne wrote:
> Source: elpy
> Version: 1.24.0-1
> Severity: serious
> Tags: ftbfs
>
> elpy fails to build from source randomly. A build log contains:
I'm aware
Source: elpy
Version: 1.24.0-1
Severity: serious
Tags: ftbfs
elpy fails to build from source randomly. A build log contains:
| Test elpy-promise-wait-should-return-early-for-resolved-promise backtrace:
| (if (unwind-protect (setq value-774 (apply fn-772 args-773)) (setq f
| (let
4 matches
Mail list logo
