Re: [gonum-dev] Re: Continuous Integration

127 views
Skip to first unread message

Jonathan Lawlor

unread,
Jul 17, 2015, 5:11:10 PM7/17/15
to gonu...@googlegroups.com, jonatha...@gmail.com
Go 1.5 beta2 is out, I'll change the .travis.yml files to match shortly.

Jonathan Lawlor

unread,
Jul 17, 2015, 6:41:56 PM7/17/15
to gonu...@googlegroups.com
I don't know why this went to a new topic, must have pressed the wrong button.

Anyway,  there seems to be an issue with OpenBLAS related builds.  Both lapack and blas are failing in 1.5beta2 when built against OpenBLAS during go get -d -t -v ./... with:

import "C": import path does not begin with hostname

package github.com/gonum/blas/cblas128

imports github.com/gonum/blas/cgo

imports C: unrecognized import path "C"


See:

Jonathan Lawlor

unread,
Jul 17, 2015, 6:45:35 PM7/17/15
to gonu...@googlegroups.com
Seems to be related to godep:


Do you want to roll back to beta1 for now, until godep fixes the issue?

Jonathan Lawlor

unread,
Jul 17, 2015, 6:48:00 PM7/17/15
to gonu...@googlegroups.com
Nevermind, it is an issue with go. They have a patch in the works: https://go-review.googlesource.com/#/c/12322/

Dan Kortschak

unread,
Jul 17, 2015, 6:55:35 PM7/17/15
to Jonathan Lawlor, gonu...@googlegroups.com
Leave it as is and when the go CL goes in we can restart those tests runs.

Jonathan Lawlor

unread,
Jul 30, 2015, 11:12:10 AM7/30/15
to gonum-dev, dan.ko...@adelaide.edu.au
Now updating from beta2 to beta3

Jonathan Lawlor

unread,
Jul 30, 2015, 11:25:17 AM7/30/15
to gonum-dev, dan.ko...@adelaide.edu.au, jonatha...@gmail.com
An issue popped up while testing stat:

runtime: bad pointer in frame github.com/gonum/matrix/mat64.(*SymDense).CopySym at 0xc820024370: 0x40

fatal error: invalid stack pointer


and also in matrix:

runtime: bad pointer in frame github.com/gonum/matrix/mat64.(*Dense).Clone at 0xc8200432a0: 0x4

fatal error: invalid stack pointer


and also in optimize:

=== RUN TestLocal

runtime: bad pointer in frame github.com/gonum/matrix/mat64.Inner at 0xc820046418: 0x2

fatal error: invalid stack pointer

Jonathan Lawlor

unread,
Jul 30, 2015, 11:40:23 AM7/30/15
to gonum-dev, dan.ko...@adelaide.edu.au, jonatha...@gmail.com
I opened an issue on golang: https://github.com/golang/go/issues/11941

Jonathan Lawlor

unread,
Aug 6, 2015, 7:58:31 AM8/6/15
to gonum-dev, dan.ko...@adelaide.edu.au, jonatha...@gmail.com
Builds are passing in 1.5rc1.

Jonathan Lawlor

unread,
Aug 19, 2015, 1:28:34 PM8/19/15
to gonum-dev, dan.ko...@adelaide.edu.au, jonatha...@gmail.com
I'm going to be updating the builds to use the 1.5 release today.

Brendan Tracey

unread,
Aug 19, 2015, 1:33:34 PM8/19/15
to Jonathan Lawlor, gonum-dev, dan.ko...@adelaide.edu.au
Thank you

On Aug 19, 2015, at 11:28 AM, Jonathan Lawlor <jonatha...@gmail.com> wrote:

I'm going to be updating the builds to use the 1.5 release today.

--
You received this message because you are subscribed to the Google Groups "gonum-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gonum-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jonathan Lawlor

unread,
Aug 19, 2015, 2:05:22 PM8/19/15
to gonum-dev, jonatha...@gmail.com, dan.ko...@adelaide.edu.au
Things look good.

Jonathan Lawlor

unread,
Sep 9, 2015, 8:29:59 AM9/9/15
to gonum-dev, jonatha...@gmail.com
Go 1.5.1 is out, I'll change the .travis.yml files to match shortly.

Jonathan Lawlor

unread,
Sep 9, 2015, 10:39:56 AM9/9/15
to gonum-dev, jonatha...@gmail.com
Things look good.

Jonathan Lawlor

unread,
Dec 18, 2015, 8:44:22 AM12/18/15
to gonum-dev, jonatha...@gmail.com
1.6 beta1 has been released.  I'll be forking the repos today, adding it to the build matrix, and seeing how things turn out.

Jonathan Lawlor

unread,
Dec 18, 2015, 11:29:18 AM12/18/15
to gonum-dev, jonatha...@gmail.com
Everything is working in my forks.  Do you want me to add 1.6beta1 to the gonum build matrices?

Dan Kortschak

unread,
Dec 18, 2015, 2:17:13 PM12/18/15
to Jonathan Lawlor, gonum-dev, jonatha...@gmail.com
Yes please.

Would you also update 1.5 -> 1.5.2 where it hasn't been?

thanks
Dan
--
Reply all
Reply to author
Forward
0 new messages