9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Steven Stallion" <sstallion@gmail.com>
To: 9fans@9fans.net
Subject: Building go1.12.14
Date: Wed, 1 Jan 2020 10:20:57 -0600	[thread overview]
Message-ID: <3ac69ebcade3d4c3d6633a6f764dcf03@gunge.quuxotic.net> (raw)

All,

I was updating my golang installation this morning and I ran into a
couple of failures building go1.12.14 - I was curious if any on the
list have run into issues as well:

	--- FAIL: TestContextCancel (1.02s)
	    exec_test.go:1096: echo
	    : 
	    exec_test.go:1122: canceling context did not stop program
	FAIL
	FAIL	os/exec	4.824s

and:

	go test proxy starting
	go proxy_test: invalid module path encoding "example.com/invalidpath/v1": malformed module path "example.com/invalidpath/v1": invalid version
	go test proxy running at GOPROXY=http://127.0.0.1:59211/mod
	panic: test timed out after 9m0s
	:
	FAIL	cmd/go	589.840s

All other tests pass.  I'm running a vanilla labs installation with
patches applied from https://github.com/golang/go/wiki/Plan9.

Assuming this is a new issue with the plan9 port, is there a dashboard
available of working release builds that could be used to avoid
playing update-whackamole?

Any ideas?
Steve


             reply	other threads:[~2020-01-01 16:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-01 16:20 Steven Stallion [this message]
2020-01-01 17:12 ` [9fans] " David du Colombier
2020-01-01 18:08   ` Steven Stallion
2020-01-01 19:04     ` David du Colombier
2020-01-01 19:10       ` David du Colombier
2020-01-01 21:36         ` Steven Stallion
2020-01-01 22:08           ` David du Colombier
2020-01-01 22:58             ` Steven Stallion

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ac69ebcade3d4c3d6633a6f764dcf03@gunge.quuxotic.net \
    --to=sstallion@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).