On Sat, Aug 4, 2018 at 7:35 AM Anthony Fok wrote:
> For some reasons, however, I have been unable to reproduce this test
> FAIL on my own machine.
>
It always fails on my cpu-busy server(same in upstream issue report)
> So, yes, skipping TestExecutableDelete is the entirely pragmatic thing
> to
HI Shengjing,
On Thu, Aug 2, 2018 at 8:49 AM, Shengjing Zhu wrote:
> Hi Go team,
>
> On Tue, Jun 26, 2018 at 10:52:52PM +, Santiago Vila wrote:
>> === RUN TestExecutableDelete
>> --- FAIL: TestExecutableDelete (0.00s)
>> osext_test.go:135: Child returned
>> "/tmp/go-build962600465/b0
Hi team,
Here is the patch to skip this test.
--
Shengjing Zhu
diff -Nru
golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/changelog
golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/changelog
--- golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/changelo
Hi Go team,
On Tue, Jun 26, 2018 at 10:52:52PM +, Santiago Vila wrote:
> === RUN TestExecutableDelete
> --- FAIL: TestExecutableDelete (0.00s)
> osext_test.go:135: Child returned
> "/tmp/go-build962600465/b001/osext.test (deleted)", not the same file as
> "/tmp/go-build962600465/b001
Package: src:golang-github-kardianos-osext
Version: 0.0~git20170510.0.ae77be6-5
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:
[...]
5 matches
Mail list logo