Dan Kortschak
unread,Jul 31, 2017, 7:24:50 PM7/31/17Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to gonu...@googlegroups.com
Travis has been causing a lot of problems for go1.6 builds since we
merged all the repos into gonum/gonum. Part of this is our fault, and
that is the only thing we can do anything about.
Because we are now testing significantly more code in a single build
cycle sometimes travis' builds timeout before completion (open source
projects are given 50 minutes). This happens because we do several
complete builds/tests, testing each of the important build tags to
ensure build consistency. However, it only seems to happen with go1.6
(compile time?, SSA optimisations? who knows).
This is a bit of a problem.
Things we can do:
1. Wait until go1.6 goes away (soon) and see if that solves the
problem.
2. Don't use the travis build matrix, but rather engineer our own (or
figure out how to use travis in a more refined way) so that only
packages with these build tags are multiply tested.
At the moment, I'm leaning towards 1., but 2. might be necessary.
Dan