Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

os/exec: TestExtraFiles is flaky on linux-386-sid builder #25628

Open
ALTree opened this issue May 29, 2018 · 27 comments

Comments

@ALTree
Copy link
Member

@ALTree ALTree commented May 29, 2018

I've seen several of these:

--- FAIL: TestExtraFiles (0.10s)
	exec_test.go:607: Run: exit status 1; stdout "leaked parent file. fd = 66; want 65\n", stderr ""
FAIL
FAIL	os/exec	0.687s

on the linux-386-sid builder in the past weeks. Here's one:

https://build.golang.org/log/b95e0220b4130af6c1bcfed59ec934568717d0ef

@bcmills bcmills added the OS-Linux label May 29, 2018
@ianlancetaylor ianlancetaylor added this to the Go1.11 milestone May 31, 2018
@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

@ianlancetaylor ianlancetaylor commented May 31, 2018

That is odd. The errors show relatively large descriptor numbers. It implies that something in the system is opening a large descriptor before running make.bash.

@bcmills

This comment has been minimized.

Copy link
Member

@bcmills bcmills commented Jun 1, 2018

There is another recurring failure mode in os/exec on linux-386-sid that produces broken pipe instead. Any idea whether they're related?

An example failure (https://build.golang.org/log/cef4b584d2ccb30621e2965de0517f6077aa2f92):

testing: can't write /tmp/go-build619681385/b056/testlog.txt: write /tmp/go-build619681385/b056/testlog.txt: broken pipe
FAIL	os/exec	0.697s
@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Jun 1, 2018

Yes, they could be related. The os/exec package tries to guess which descriptor is being used for testlog.txt; if it guesses wrong, because of an unexpectedly open descriptor, that could cause the broken pipe error.

@ALTree ALTree changed the title os/exec: TestExtraFiles is flaky on linux-386-sid bulder os/exec: TestExtraFiles is flaky on linux-386-sid builder Jun 2, 2018
@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Jun 27, 2018

2018-05-09T00:05:52-c1492b6/linux-386-sid
2018-05-11T14:40:34-e405c9c/linux-386-sid
2018-05-11T23:11:53-e6a9335/linux-386-sid
2018-05-12T06:21:01-f94b5a8/linux-386-sid
2018-05-14T13:45:18-c06f027/linux-386-sid
2018-05-14T14:12:31-7bac2a9/linux-386-sid
2018-05-14T17:59:59-15f2cbf/linux-386-sid
2018-05-15T16:29:04-212c947/linux-386-sid
2018-05-16T12:01:16-4102e6f/linux-386-sid
2018-05-21T13:18:16-f2cde55/linux-386-sid
2018-05-22T14:15:44-b812eec/linux-386-sid
2018-05-22T15:55:01-840f25b/linux-386-sid
2018-05-22T18:47:03-3d15f76/linux-386-sid
2018-05-22T18:49:31-f045ddc/linux-386-sid
2018-05-22T20:27:52-402dd10/linux-386-sid
2018-05-22T20:44:03-3c36b8b/linux-386-sid
2018-05-23T01:45:00-92bdfab/linux-386-sid
2018-05-23T14:13:24-ef880a2/linux-386-sid
2018-05-23T19:01:58-3f89214/linux-386-sid
2018-05-24T17:19:09-8aa57f1/linux-386-sid
2018-05-24T18:03:21-b0b0921/linux-386-sid
2018-05-24T20:26:47-9eb2c43/linux-386-sid
2018-05-24T22:08:00-30b6bc3/linux-386-sid
2018-05-25T08:42:09-e52c1c0/linux-386-sid
2018-05-25T13:09:29-bdaadeb/linux-386-sid
2018-05-27T07:33:08-c1d9d1f/linux-386-sid
2018-05-29T02:39:16-002c764/linux-386-sid
2018-05-29T17:46:19-ef53de8/linux-386-sid
2018-05-29T20:27:03-4790181/linux-386-sid
2018-05-29T21:54:57-210a9e0/linux-386-sid
2018-05-30T09:10:04-7d704a9/linux-386-sid
2018-05-30T13:40:36-e023d5b/linux-386-sid
2018-05-31T13:29:50-caf9686/linux-386-sid
2018-05-31T15:13:02-08e2e88/linux-386-sid
2018-05-31T17:29:10-424c215/linux-386-sid
2018-06-01T17:36:40-6cfeedb/linux-386-sid
2018-06-04T18:33:41-d6c3b0a/linux-386-sid
2018-06-05T00:29:50-75c1aed/linux-386-sid
2018-06-06T17:59:08-11f6cb4/linux-386-sid
2018-06-06T19:20:12-ca8ec69/linux-386-sid
2018-06-07T07:00:46-e5f0c1f/linux-386-sid
2018-06-07T14:31:33-35778aa/linux-386-sid
2018-06-07T15:47:29-0e1517c/linux-386-sid
2018-06-07T16:17:04-7b08e61/linux-386-sid
2018-06-08T22:44:03-77d5c62/linux-386-sid
2018-06-10T05:49:55-a5f8303/linux-386-sid
2018-06-11T12:13:11-30a63ec/linux-386-sid
2018-06-11T17:45:36-9e9ff56/linux-386-sid
2018-06-11T20:58:09-92f8acd/linux-386-sid
2018-06-12T17:05:39-ec98933/linux-386-sid
2018-06-12T20:22:50-44b826b/linux-386-sid
2018-06-12T20:37:02-bd83774/linux-386-sid
2018-06-13T17:55:32-a1b85ee/linux-386-sid
2018-06-13T20:32:08-fb4fb04/linux-386-sid
2018-06-13T21:43:06-1e721cf/linux-386-sid
2018-06-13T21:57:41-fc0e1d2/linux-386-sid
2018-06-13T22:01:28-efddc16/linux-386-sid
2018-06-14T13:21:46-1031380/linux-386-sid
2018-06-15T02:01:04-8998c55/linux-386-sid
2018-06-21T22:55:55-4b34289/linux-386-sid
2018-06-22T14:27:22-00eac89/linux-386-sid

@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Jun 27, 2018

Since this doesn't seem to be happening anywhere else, this is most likely a problem specific to the linux-386-sid builder. Something on that system is causing the os/exec tests to run with an unexpectedly open file descriptor.

@bradfitz Is there anything unusual about the linux-386-sid builder?

@ianlancetaylor ianlancetaylor modified the milestones: Go1.11, Go1.12 Jun 27, 2018
@bradfitz

This comment has been minimized.

Copy link
Member

@bradfitz bradfitz commented Jun 27, 2018

The 386-sid builder is an amd64 Docker container (like all our linux-386-*) builders with the "debian:sid" base layer (https://github.com/golang/build/blob/master/env/linux-x86-sid/Dockerfile). We occasionally re-build it to reflect the ever-changing Debian sid.

Last updates:

  • April 11, 2017
  • Nov 2, 2017
  • May 8, 2018 (current)
@ALTree

This comment has been minimized.

Copy link
Member Author

@ALTree ALTree commented Jul 7, 2018

This was reported to also happen on a linux_386 Virtualbox machine with an updated Ubuntu Mate 18.04 LTS and boostrap Go version 1.4.3 (Issue #26261).

@mikesmitty

This comment has been minimized.

Copy link

@mikesmitty mikesmitty commented Aug 24, 2018

Ran into this issue with 1.11rc2 on Fedora 27 i386 as well:

--- FAIL: TestExtraFiles (0.07s)
    exec_test.go:607: Run: exit status 1; stdout "leaked parent file. fd = 66; want 65\n", stderr ""
FAIL
FAIL	os/exec	1.074s
@bobvanderlinden

This comment has been minimized.

Copy link

@bobvanderlinden bobvanderlinden commented Sep 15, 2018

This happens on NixOS as well. There it seems to be happening reliably as I can reproduce it on my laptop again and again. The NixOS build server also reproduces the error for every build.

This happens on go 1.11.

For reference: https://hydra.nixos.org/build/80999166/nixlog/12

bobvanderlinden added a commit to bobvanderlinden/nixpkgs that referenced this issue Sep 15, 2018
This seems to only happen on i686 on go 1.11. It also happens on
Debian. For more information:

golang/go#25628
@bobvanderlinden bobvanderlinden mentioned this issue Sep 15, 2018
4 of 9 tasks complete
Mic92 added a commit to NixOS/nixpkgs that referenced this issue Sep 16, 2018
This seems to only happen on i686 on go 1.11. It also happens on
Debian. For more information:

golang/go#25628
(cherry picked from commit 0bf6b44)
@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Dec 20, 2018

@bradfitz The test will try to run lsof when it finds a leaked FD. That isn't happening on linux-386-sid. Could we get the lsof package installed on that system?

@bradfitz

This comment has been minimized.

Copy link
Member

@bradfitz bradfitz commented Dec 20, 2018

@ianlancetaylor, I filed #29347 for somebody to do that.

@bcmills

This comment has been minimized.

Copy link
Member

@bcmills bcmills commented Jun 14, 2019

@bcmills

This comment has been minimized.

@andybons andybons modified the milestones: Go1.13, Go1.14 Jul 8, 2019
@bcmills

This comment has been minimized.

Copy link
Member

@bcmills bcmills commented Aug 26, 2019

@ianlancetaylor

The test will try to run lsof when it finds a leaked FD. That isn't happening on linux-386-sid.

According to #29347 (comment), the lsof command is already installed.

I notice that we're dropping the error on the command invocation; perhaps we should write that to os.Stdout on failure?

@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Aug 26, 2019

It can't hurt to print the error.

@rsc rsc modified the milestones: Go1.14, Backlog Oct 9, 2019
@bcmills bcmills added the help wanted label Oct 17, 2019
@gopherbot

This comment has been minimized.

Copy link

@gopherbot gopherbot commented Oct 17, 2019

Change https://golang.org/cl/201717 mentions this issue: os/exec: preserve the process environment when invoking TestHelperProcess

@gopherbot

This comment has been minimized.

Copy link

@gopherbot gopherbot commented Oct 17, 2019

Change https://golang.org/cl/201718 mentions this issue: os/exec: re-enable TestExtraFiles checks skipped on various OSes

gopherbot pushed a commit that referenced this issue Oct 17, 2019
…cess

Also log errors from the lsof command on failure.
(That's how the missing environment was discovered.)

Updates #25628

Change-Id: I71594f60c15d0d254d5d4a86deec7431314c92ff
Reviewed-on: https://go-review.googlesource.com/c/go/+/201717
Run-TryBot: Bryan C. Mills <bcmills@google.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
gopherbot pushed a commit that referenced this issue Oct 17, 2019
The issues associated with these skipped checks are closed.
If they are working around unfixed bugs, the issues should remain open.
If they are working around unfixable properties of the system, the skips
should refer to those properties rather than closed issues.

Updates #2603
Updates #3955
Updates #25628

Change-Id: I3491c69b2ef5bad0fb12001fe8f7e06b424883ca
Reviewed-on: https://go-review.googlesource.com/c/go/+/201718
Run-TryBot: Bryan C. Mills <bcmills@google.com>
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
@bcmills

This comment has been minimized.

Copy link
Member

@bcmills bcmills commented Oct 17, 2019

We have a hit with lsof!

https://build.golang.org/log/36beca237b1c2445d60bc51995da2f83b628b203

--- FAIL: TestExtraFiles (1.18s)
    exec_test.go:659: Run: exit status 1
        --- stdout:
        leaked parent file. fd = 66; want 65
        COMMAND     PID USER   FD      TYPE DEVICE SIZE/OFF   NODE NAME
        exec.test 21020 root  cwd       DIR   0,54      360  23652 /workdir/go/src/os/exec
        exec.test 21020 root  rtd       DIR   0,55     4096 149435 /
        exec.test 21020 root  txt       REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root  mem       REG    8,1          142148 /lib32/libc-2.28.so (path dev=0,55)
        exec.test 21020 root  mem       REG    8,1          142172 /lib32/libpthread-2.28.so (path dev=0,55)
        exec.test 21020 root  mem       REG    8,1          142141 /lib32/ld-2.28.so (path dev=0,55)
        exec.test 21020 root    0r      CHR    1,3      0t0  17741 /dev/null
        exec.test 21020 root    1w     FIFO   0,12      0t0  95732 pipe
        exec.test 21020 root    2w     FIFO   0,12      0t0  95733 pipe
        exec.test 21020 root    3u      REG   0,54       12  95731 /workdir/tmp/216658506
        exec.test 21020 root    4r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root    5u  a_inode   0,13        0   9441 [eventpoll]
        exec.test 21020 root    6r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root    7r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root    8r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root    9r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   10r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   11r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   12r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   13r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   14r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   15r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   16r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   17r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   18r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   19r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   20r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   21r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   22r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   23r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   24r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   25r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   26r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   27r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   28r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   29r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   30r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   31r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   32r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   33r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   34r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   35r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   36r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   37r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   38r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   39r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   40r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   41r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   42r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   43r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   44r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   45r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   46r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   47r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   48r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   49r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   50r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   51r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   52r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   53r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   54r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   55r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   56r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   57r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   58r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   59r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   60r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   61r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   62r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   63r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   64r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        exec.test 21020 root   65r     FIFO   0,12      0t0  96354 pipe
        exec.test 21020 root   66r      REG   0,54  5455872  94891 /workdir/tmp/go-build324177353/b061/exec.test
        --- stderr:
FAIL
FAIL	os/exec	1.703s
@bradfitz

This comment has been minimized.

Copy link
Member

@bradfitz bradfitz commented Oct 17, 2019

Uhhh, what is happening there?

@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Oct 20, 2019

Thanks. What we learn from this is that the read descriptor for a pipe open at descriptor 65. TestExtraFiles does not expect that, so it gives an error. The write descriptor for the pipe is not open in this process though of course it may be open in a different process.

Looking at the test further, it actually closes all descriptors including descriptor 65 before starting the child process. So it seems that simply starting the child process has caused a pipe to be opened at descriptor 65 (closeUnexpectedFds). Starting a child does create a pipe (forkExecPipe in the syscall package). But the pipe is opened O_CLOEXEC, and it wouldn't be at descriptor 65 in any case. It would be more like descriptor 10.

I have no idea what is happening here. If I could get a shell on the system the next step would be to try to run the test under strace -f.

@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Nov 14, 2019

Another failure on linux-386-sid: https://build.golang.org/log/8cf72752dda62b1002d13a8c51932bda15333f0d

Interestingly, this time it is leaked parent file. fd = 67; want 65, but the list shows

        exec.test 20803 root   63r      REG   0,54  5582848  99736 /workdir/tmp/go-build685292074/b061/exec.test
        exec.test 20803 root   64r      REG   0,54  5582848  99736 /workdir/tmp/go-build685292074/b061/exec.test
        exec.test 20803 root   66r     FIFO   0,12      0t0  98166 pipe
        exec.test 20803 root   67r      REG   0,54  5582848  99736 /workdir/tmp/go-build685292074/b061/exec.test

What is interesting here is that there lsof shows no descriptor 65. That suggests that when we opened the new file both descriptors 65 and 66 were open, but by the time we invoked lsof descriptor 65 was closed. At least, I can't think of another explanation.

Note that this failure was after CL 207078 was committed, and that no extra files were reported at the time that the os/exec test started.

@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Nov 14, 2019

@bradfitz How hard would it be to enable SSH access to the linux-386-sid builder? Thanks.

> gomote ssh user-iant-linux-386-sid-1
$ ssh -p 2222 user-iant-linux-386-sid-1@farmer.golang.org # auth using https://github.com/ianlancetaylor.keys
instance "user-iant-linux-386-sid-1" host type "host-linux-sid" does not have SSH configured
Connection to farmer.golang.org closed.
@bradfitz

This comment has been minimized.

Copy link
Member

@bradfitz bradfitz commented Nov 15, 2019

@ianlancetaylor, done in https://go-review.googlesource.com/c/build/+/207459 but it's not deployed yet. I'll do it later tonight when people aren't using AIX slowbots.

@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Nov 15, 2019

Thanks!

@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Nov 15, 2019

(Although AIX is in a dreadful state right now, one can only hope that the slowbots will be able to catch up.)

@bradfitz

This comment has been minimized.

Copy link
Member

@bradfitz bradfitz commented Nov 15, 2019

Deployed. But note that by rebuilding the sid image to add ssh support, the sid environment is now 5-6 months newer than it was before. So if it was a bug in something in Debian, it might be fixed now.

@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Nov 16, 2019

Thanks! 10,000 runs with no failure, but there might be some key difference between what I was doing and what the builders are doing. I guess let's wait a while and see if this happens again after today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
9 participants
You can’t perform that action at this time.