Re: lang/go failes to build with poudriere, since 2018-04-05

2018-07-05 Thread Steven Hartland 
Yes thanks, sorry its taken a while to get round to looking at this; I 
didn't get the ktrace output file, only the log file you sent attached 
on the 27th.


    Regards
    Steve

On 28/04/2018 06:57, Bjarne wrote:

Hi Steven

I trust you have recieved the logfiles.
let me know if you need more tests.



On 27-04-2018 10:32, Steven Hartland wrote:
Thanks for that does seem like your machine can readily reproduce in 
just a few seconds which is good. Here it usually takes days to 
trigger, which is why its been so hard to make any progress on 
isolating the issue; which its not clear if its go or kernel related.


Can you see if you can trigger the failure with:
ktrace -tfw+ -i -f ktrace-test.out ./test

:snip





___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: lang/go failes to build with poudriere, since 2018-04-05

2018-04-27 Thread Bjarne 

Hi Steven

I trust you have recieved the logfiles.
let me know if you need more tests.



On 27-04-2018 10:32, Steven Hartland wrote:
Thanks for that does seem like your machine can readily reproduce in just a few seconds which is 
good. Here it usually takes days to trigger, which is why its been so hard to make any progress on 
isolating the issue; which its not clear if its go or kernel related.


Can you see if you can trigger the failure with:
ktrace -tfw+ -i -f ktrace-test.out ./test

:snip



--
mvh,
Bjarne

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: lang/go failes to build with poudriere, since 2018-04-05

2018-04-27 Thread Steven Hartland 
Thanks for that does seem like your machine can readily reproduce in 
just a few seconds which is good. Here it usually takes days to trigger, 
which is why its been so hard to make any progress on isolating the 
issue; which its not clear if its go or kernel related.


Can you see if you can trigger the failure with:
ktrace -tfw+ -i -f ktrace-test.out ./test

On 27/04/2018 08:57, Bjarne wrote:

Hello Steve

The host machine is homebuilt with:
motherboard:  ASRock Z97 Pro3 - Z97Pro3
cpu:  Intel(R) Core(TM) i5-4460  CPU @ 3.20GHz
Ram: 32GB

poudriere is running on zfs.


So this is what I did:

Previously on your suggestions, I lowered the number af of cpu's to 1 
and was able to build a go version, meaning I have a go package.

Installing that version:

go version go1.10.1 freebsd/amd64
Just to test how to test, I tried your suggetions before patching 
anything.


with 4 cpu's.
go build main.go
go build -o test main.go

# build crash , can't build, core dump

# reducing to  1 cpu

# go build -o test main.go
# command-line-arguments
./main.go:15:13: undefined: syscall.ForkOnlyBSDTest


ok, now  patching to insert debug syscalls.

And your test program produces the attached log

Hope that helps.



On 27-04-2018 01:04, Steven Hartland wrote:

Thanks for the information, next question is what it the host machine?

As your currently unable to build go we may have to get a binary dist 
on the machine to start debugging, I can provide that if needed.


Once you have a working go installs you can try building and running 
the following:


The attached golang patch can be used to add new debug syscall, if 
you can build go from ports (try outside of poudriere).


Then you can compile main.go from a directory named test using "go 
build" and then from the same directory run the test.sh and lets see 
what you get?


    Regards
    Steve


On 26/04/2018 19:23, Bjarne wrote:

Hi Steven

Thanks for getting back on this.

The os is 11.1-RELEASE-p9  and the ports tree is HEAD.
The build machine is a virtual server ,
5120 M RAM
4 cpu
on top of  xen :
release    : 4.4.104-39-default
version    : #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912)


It seems I have a reliable test environment. I have just 
reconfigured to 4 cpus and tested a rebuild and got same error as 
before.

Anything i can do to assist in debugging?

Bear in mind I dont know anything of lang/go and am still a beginner 
regading poudriere.
I have frozen the build machine so it wont download new versions of 
anything.




On 26-04-2018 01:31, Steven Hartland wrote:
That happens very rarely, so rarely its been really hard to make 
any progress debugging it.


If you believe you have reliable reproduction case I'd be very 
interested in it.


One thing I noticed when re-reading your original post is that you 
say you tested on 11.1 but then your output mentions HEAD, are you 
running 11.1-RELEASE or 11-STABLE, if so what revision?


Also of interest is the hardware and related configuration?

    Regards
    Steve

On 25/04/2018 22:09, Derek (freebsd lists) wrote:

Ah, you'll note: fork/exec implicated here.

Looks like this guy strikes again:
https://github.com/golang/go/issues/15658

It pains me to say but Go on FreeBSD is (and has always been) 
broken.  Should be fine if you don't exec. Something that might 
help, is setting GOMAXPROCS=1.


Derek

On 18-04-25 07:45 AM, Steven Hartland wrote:

Builds fine on 11.1-RELEASE-p6 here:

[00:04:02] Committing packages to repository
[00:04:02] Removing old packages
[00:04:02] Built ports: lang/go
[ports11-1-multiplay] [2018-04-25_11h37m16s] [committing:] 
Queued: 1 Built: 1  Failed: 0  Skipped: 0 Ignored: 0  Tobuild: 
0   Time: 00:04:01
[00:04:02] Logs: 
/usr/local/poudriere/data/logs/bulk/ports11-1-multiplay/2018-04-25_11h37m16s 


[00:04:02] Cleaning up

svn info
Path: .
Working Copy Root Path: /usr/local/poudriere/ports/multiplay
URL: https://svn.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 468275
Node Kind: directory
Schedule: normal
Last Changed Author: tobik
Last Changed Rev: 468275
Last Changed Date: 2018-04-25 11:08:41 + (Wed, 25 Apr 2018)


 Regards
 Steve

On 25/04/2018 12:07, Bjarne wrote:
I got a job to rebuild all packages every night, but since 
2018-04-05 building /usr/ports/lang/go is failing.


Apparently 2018-04-05  some major changed was introduced, since 
331 pakackes was rebuilt. Not sure what it was, I saw nothing in 
UPATING.


Top of logfile:


Building lang/go

:snip





___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to 
"freebsd-ports-unsubscr...@freebsd.org"








--
mvh,
Bjarne




--
mvh,
Bjarne


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/l

Re: lang/go failes to build with poudriere, since 2018-04-05

2018-04-27 Thread Bjarne 

Hello Steve

The host machine is homebuilt with:
motherboard:  ASRock Z97 Pro3 - Z97Pro3
cpu:  Intel(R) Core(TM) i5-4460  CPU @ 3.20GHz
Ram: 32GB

poudriere is running on zfs.


So this is what I did:

Previously on your suggestions, I lowered the number af of cpu's to 1 and was able to build a go 
version, meaning I have a go package.

Installing that version:

go version go1.10.1 freebsd/amd64
Just to test how to test, I tried your suggetions before patching anything.

with 4 cpu's.
go build main.go
go build -o test main.go

# build crash , can't build, core dump

# reducing to  1 cpu

# go build -o test main.go
# command-line-arguments
./main.go:15:13: undefined: syscall.ForkOnlyBSDTest


ok, now  patching to insert debug syscalls.

And your test program produces the attached log

Hope that helps.



On 27-04-2018 01:04, Steven Hartland wrote:

Thanks for the information, next question is what it the host machine?

As your currently unable to build go we may have to get a binary dist on the machine to start 
debugging, I can provide that if needed.


Once you have a working go installs you can try building and running the 
following:

The attached golang patch can be used to add new debug syscall, if you can build go from ports 
(try outside of poudriere).


Then you can compile main.go from a directory named test using "go build" and then from the same 
directory run the test.sh and lets see what you get?


    Regards
    Steve


On 26/04/2018 19:23, Bjarne wrote:

Hi Steven

Thanks for getting back on this.

The os is 11.1-RELEASE-p9  and the ports tree is HEAD.
The build machine is a virtual server ,
5120 M RAM
4 cpu
on top of  xen :
release    : 4.4.104-39-default
version    : #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912)


It seems I have a reliable test environment. I have just reconfigured to 4 cpus and tested a 
rebuild and got same error as before.

Anything i can do to assist in debugging?

Bear in mind I dont know anything of lang/go and am still a beginner regading 
poudriere.
I have frozen the build machine so it wont download new versions of anything.



On 26-04-2018 01:31, Steven Hartland wrote:

That happens very rarely, so rarely its been really hard to make any progress 
debugging it.

If you believe you have reliable reproduction case I'd be very interested in it.

One thing I noticed when re-reading your original post is that you say you tested on 11.1 but 
then your output mentions HEAD, are you running 11.1-RELEASE or 11-STABLE, if so what revision?


Also of interest is the hardware and related configuration?

    Regards
    Steve

On 25/04/2018 22:09, Derek (freebsd lists) wrote:

Ah, you'll note: fork/exec implicated here.

Looks like this guy strikes again:
https://github.com/golang/go/issues/15658

It pains me to say but Go on FreeBSD is (and has always been) broken.  Should be fine if you 
don't exec.  Something that might help, is setting GOMAXPROCS=1.


Derek

On 18-04-25 07:45 AM, Steven Hartland wrote:

Builds fine on 11.1-RELEASE-p6 here:

[00:04:02] Committing packages to repository
[00:04:02] Removing old packages
[00:04:02] Built ports: lang/go
[ports11-1-multiplay] [2018-04-25_11h37m16s] [committing:] Queued: 1 Built: 1  Failed: 0  
Skipped: 0  Ignored: 0 Tobuild: 0   Time: 00:04:01

[00:04:02] Logs: 
/usr/local/poudriere/data/logs/bulk/ports11-1-multiplay/2018-04-25_11h37m16s
[00:04:02] Cleaning up

svn info
Path: .
Working Copy Root Path: /usr/local/poudriere/ports/multiplay
URL: https://svn.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 468275
Node Kind: directory
Schedule: normal
Last Changed Author: tobik
Last Changed Rev: 468275
Last Changed Date: 2018-04-25 11:08:41 + (Wed, 25 Apr 2018)


 Regards
 Steve

On 25/04/2018 12:07, Bjarne wrote:
I got a job to rebuild all packages every night, but since 2018-04-05 building 
/usr/ports/lang/go is failing.


Apparently 2018-04-05  some major changed was introduced, since 331 pakackes was rebuilt. Not 
sure what it was, I saw nothing in UPATING.


Top of logfile:


Building lang/go

:snip





___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"







--
mvh,
Bjarne




--
mvh,
Bjarne

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: lang/go failes to build with poudriere, since 2018-04-05

2018-04-26 Thread Steven Hartland 

Thanks for the information, next question is what it the host machine?

As your currently unable to build go we may have to get a binary dist on 
the machine to start debugging, I can provide that if needed.


Once you have a working go installs you can try building and running the 
following:


The attached golang patch can be used to add new debug syscall, if you 
can build go from ports (try outside of poudriere).


Then you can compile main.go from a directory named test using "go 
build" and then from the same directory run the test.sh and lets see 
what you get?


    Regards
    Steve


On 26/04/2018 19:23, Bjarne wrote:

Hi Steven

Thanks for getting back on this.

The os is 11.1-RELEASE-p9  and the ports tree is HEAD.
The build machine is a virtual server ,
5120 M RAM
4 cpu
on top of  xen :
release    : 4.4.104-39-default
version    : #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912)


It seems I have a reliable test environment. I have just reconfigured 
to 4 cpus and tested a rebuild and got same error as before.

Anything i can do to assist in debugging?

Bear in mind I dont know anything of lang/go and am still a beginner 
regading poudriere.
I have frozen the build machine so it wont download new versions of 
anything.




On 26-04-2018 01:31, Steven Hartland wrote:
That happens very rarely, so rarely its been really hard to make any 
progress debugging it.


If you believe you have reliable reproduction case I'd be very 
interested in it.


One thing I noticed when re-reading your original post is that you 
say you tested on 11.1 but then your output mentions HEAD, are you 
running 11.1-RELEASE or 11-STABLE, if so what revision?


Also of interest is the hardware and related configuration?

    Regards
    Steve

On 25/04/2018 22:09, Derek (freebsd lists) wrote:

Ah, you'll note: fork/exec implicated here.

Looks like this guy strikes again:
https://github.com/golang/go/issues/15658

It pains me to say but Go on FreeBSD is (and has always been) 
broken.  Should be fine if you don't exec.  Something that might 
help, is setting GOMAXPROCS=1.


Derek

On 18-04-25 07:45 AM, Steven Hartland wrote:

Builds fine on 11.1-RELEASE-p6 here:

[00:04:02] Committing packages to repository
[00:04:02] Removing old packages
[00:04:02] Built ports: lang/go
[ports11-1-multiplay] [2018-04-25_11h37m16s] [committing:] Queued: 
1 Built: 1  Failed: 0  Skipped: 0  Ignored: 0 Tobuild: 0   Time: 
00:04:01
[00:04:02] Logs: 
/usr/local/poudriere/data/logs/bulk/ports11-1-multiplay/2018-04-25_11h37m16s 


[00:04:02] Cleaning up

svn info
Path: .
Working Copy Root Path: /usr/local/poudriere/ports/multiplay
URL: https://svn.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 468275
Node Kind: directory
Schedule: normal
Last Changed Author: tobik
Last Changed Rev: 468275
Last Changed Date: 2018-04-25 11:08:41 + (Wed, 25 Apr 2018)


 Regards
 Steve

On 25/04/2018 12:07, Bjarne wrote:
I got a job to rebuild all packages every night, but since 
2018-04-05 building /usr/ports/lang/go is failing.


Apparently 2018-04-05  some major changed was introduced, since 
331 pakackes was rebuilt. Not sure what it was, I saw nothing in 
UPATING.


Top of logfile:


Building lang/go

:snip





___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to 
"freebsd-ports-unsubscr...@freebsd.org"








--
mvh,
Bjarne


--- /dev/null   2017-03-24 16:44:00.0 +
+++ src/syscall/exec_bsd_debug.go   2017-03-15 16:28:55.0 +
@@ -0,0 +1,41 @@
+// +build darwin dragonfly freebsd netbsd openbsd
+
+package syscall
+
+func ForkOnlyBSDTest() (err error) {
+   var r1 uintptr
+   var pid int
+   var err1 Errno
+   var wstatus WaitStatus
+
+   ForkLock.Lock()
+   runtime_BeforeFork()
+
+   r1, _, err1 = RawSyscall(SYS_FORK, 0, 0, 0)
+   if err1 != 0 {
+   runtime_AfterFork()
+   ForkLock.Unlock()
+   return err1
+   }
+
+   if r1 == 0 {
+   // in child, die die die my darling
+   for {
+   RawSyscall(SYS_EXIT, 253, 0, 0)
+   }
+   }
+
+   runtime_AfterFork()
+   ForkLock.Unlock()
+
+   pid = int(r1)
+
+   // Prime directive, exterminate
+   // Whatever stands left
+   _, err = Wait4(pid, &wstatus, 0, nil)
+   for err == EINTR {
+   _, err = Wait4(pid, &wstatus, 0, nil)
+   }
+
+   return
+}
#!/bin/sh

rm -f test.log
while true; do 
echo " NEW RUN $(date) "
echo
#time sh -c 'export GOGC=5; export GODEBUG=gctrace=2,schedtrace=100; 
./test'
#time sh -c 'export GOGC=5; ./test'
#time sh -c 'export GOGC=5; export GODEBUG=gcstackbarrierall=1; ./test'
#ti

Re: lang/go failes to build with poudriere, since 2018-04-05

2018-04-26 Thread Bjarne 

Hi Steven

Thanks for getting back on this.

The os is 11.1-RELEASE-p9  and the ports tree is HEAD.
The build machine is a virtual server ,
5120 M RAM
4 cpu
on top of  xen :
release    : 4.4.104-39-default
version    : #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912)


It seems I have a reliable test environment. I have just reconfigured to 4 cpus and tested a rebuild 
and got same error as before.

Anything i can do to assist in debugging?

Bear in mind I dont know anything of lang/go and am still a beginner regading 
poudriere.
I have frozen the build machine so it wont download new versions of anything.



On 26-04-2018 01:31, Steven Hartland wrote:

That happens very rarely, so rarely its been really hard to make any progress 
debugging it.

If you believe you have reliable reproduction case I'd be very interested in it.

One thing I noticed when re-reading your original post is that you say you tested on 11.1 but then 
your output mentions HEAD, are you running 11.1-RELEASE or 11-STABLE, if so what revision?


Also of interest is the hardware and related configuration?

    Regards
    Steve

On 25/04/2018 22:09, Derek (freebsd lists) wrote:

Ah, you'll note: fork/exec implicated here.

Looks like this guy strikes again:
https://github.com/golang/go/issues/15658

It pains me to say but Go on FreeBSD is (and has always been) broken.  Should be fine if you 
don't exec.  Something that might help, is setting GOMAXPROCS=1.


Derek

On 18-04-25 07:45 AM, Steven Hartland wrote:

Builds fine on 11.1-RELEASE-p6 here:

[00:04:02] Committing packages to repository
[00:04:02] Removing old packages
[00:04:02] Built ports: lang/go
[ports11-1-multiplay] [2018-04-25_11h37m16s] [committing:] Queued: 1 Built: 1  Failed: 0  
Skipped: 0  Ignored: 0 Tobuild: 0   Time: 00:04:01

[00:04:02] Logs: 
/usr/local/poudriere/data/logs/bulk/ports11-1-multiplay/2018-04-25_11h37m16s
[00:04:02] Cleaning up

svn info
Path: .
Working Copy Root Path: /usr/local/poudriere/ports/multiplay
URL: https://svn.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 468275
Node Kind: directory
Schedule: normal
Last Changed Author: tobik
Last Changed Rev: 468275
Last Changed Date: 2018-04-25 11:08:41 + (Wed, 25 Apr 2018)


 Regards
 Steve

On 25/04/2018 12:07, Bjarne wrote:
I got a job to rebuild all packages every night, but since 2018-04-05 building 
/usr/ports/lang/go is failing.


Apparently 2018-04-05  some major changed was introduced, since 331 pakackes was rebuilt. Not 
sure what it was, I saw nothing in UPATING.


Top of logfile:


Building lang/go

:snip





___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"







--
mvh,
Bjarne

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: lang/go failes to build with poudriere, since 2018-04-05

2018-04-26 Thread Steven Hartland 

That will just slow things down, its not a fix.

If you want to try its just an environment variable that needs to set 
before you run the app

e.g.
setenv GOMAXPROCS 1
./my-go-app

If you could have a look at my other reply and answer the questions 
there that would be appreciated.


    Regards
    Steve

On 26/04/2018 17:08, Bjarne wrote:

Hi Derek

Thank you very much for replying. it seems you hit it right on target!

Unfortunately I dont know anything about go, but it is a requirement 
of sysutils/beats. 



Googling around i can see GOMAXPROCS is something with max number of 
cpu's used.
Since i dont know where to set that parameter and the fact i am 
working with a virtual environment, I reduced the numbe of cpu's  from 
4 to 1  on the build machine.

Now go is building and all is well again.

Where would I set GOMAXPROCS=1?
I might want to go back to 4 cpu's again.



On 25-04-2018 23:09, Derek (freebsd lists) wrote:

Ah, you'll note: fork/exec implicated here.

Looks like this guy strikes again:
https://github.com/golang/go/issues/15658

It pains me to say but Go on FreeBSD is (and has always been) 
broken.  Should be fine if you don't exec.  Something that might 
help, is setting GOMAXPROCS=1.


Derek

On 18-04-25 07:45 AM, Steven Hartland wrote:

Builds fine on 11.1-RELEASE-p6 here:

[00:04:02] Committing packages to repository
[00:04:02] Removing old packages
[00:04:02] Built ports: lang/go
[ports11-1-multiplay] [2018-04-25_11h37m16s] [committing:] Queued: 1 
Built: 1  Failed: 0  Skipped: 0  Ignored: 0 Tobuild: 0   Time: 00:04:01
[00:04:02] Logs: 
/usr/local/poudriere/data/logs/bulk/ports11-1-multiplay/2018-04-25_11h37m16s 


[00:04:02] Cleaning up

svn info
Path: .
Working Copy Root Path: /usr/local/poudriere/ports/multiplay
URL: https://svn.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 468275
Node Kind: directory
Schedule: normal
Last Changed Author: tobik
Last Changed Rev: 468275
Last Changed Date: 2018-04-25 11:08:41 + (Wed, 25 Apr 2018)


 Regards
 Steve

On 25/04/2018 12:07, Bjarne wrote:
I got a job to rebuild all packages every night, but since 
2018-04-05 building /usr/ports/lang/go is failing.


Apparently 2018-04-05  some major changed was introduced, since 331 
pakackes was rebuilt. Not sure what it was, I saw nothing in UPATING.


Top of logfile:


Building lang/go

:snip




--
mvh,
Bjarne


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: lang/go failes to build with poudriere, since 2018-04-05

2018-04-26 Thread Bjarne 

Hi Derek

Thank you very much for replying. it seems you hit it right on target!

Unfortunately I dont know anything about go, but it is a requirement of sysutils/beats. 



Googling around i can see GOMAXPROCS is something with max number of cpu's used.
Since i dont know where to set that parameter and the fact i am working with a virtual environment, 
I reduced the numbe of cpu's from 4 to 1  on the build machine.

Now go is building and all is well again.

Where would I set GOMAXPROCS=1?
I might want to go back to 4 cpu's again.



On 25-04-2018 23:09, Derek (freebsd lists) wrote:

Ah, you'll note: fork/exec implicated here.

Looks like this guy strikes again:
https://github.com/golang/go/issues/15658

It pains me to say but Go on FreeBSD is (and has always been) broken.  Should be fine if you don't 
exec.  Something that might help, is setting GOMAXPROCS=1.


Derek

On 18-04-25 07:45 AM, Steven Hartland wrote:

Builds fine on 11.1-RELEASE-p6 here:

[00:04:02] Committing packages to repository
[00:04:02] Removing old packages
[00:04:02] Built ports: lang/go
[ports11-1-multiplay] [2018-04-25_11h37m16s] [committing:] Queued: 1 Built: 1  Failed: 0  
Skipped: 0  Ignored: 0  Tobuild: 0   Time: 00:04:01

[00:04:02] Logs: 
/usr/local/poudriere/data/logs/bulk/ports11-1-multiplay/2018-04-25_11h37m16s
[00:04:02] Cleaning up

svn info
Path: .
Working Copy Root Path: /usr/local/poudriere/ports/multiplay
URL: https://svn.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 468275
Node Kind: directory
Schedule: normal
Last Changed Author: tobik
Last Changed Rev: 468275
Last Changed Date: 2018-04-25 11:08:41 + (Wed, 25 Apr 2018)


 Regards
 Steve

On 25/04/2018 12:07, Bjarne wrote:
I got a job to rebuild all packages every night, but since 2018-04-05 building  
/usr/ports/lang/go is failing.


Apparently 2018-04-05  some major changed was introduced, since 331 pakackes was rebuilt. Not 
sure what it was, I saw nothing in UPATING.


Top of logfile:


Building lang/go

:snip




--
mvh,
Bjarne

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: lang/go failes to build with poudriere, since 2018-04-05

2018-04-25 Thread Steven Hartland 
That happens very rarely, so rarely its been really hard to make any 
progress debugging it.


If you believe you have reliable reproduction case I'd be very 
interested in it.


One thing I noticed when re-reading your original post is that you say 
you tested on 11.1 but then your output mentions HEAD, are you running 
11.1-RELEASE or 11-STABLE, if so what revision?


Also of interest is the hardware and related configuration?

    Regards
    Steve

On 25/04/2018 22:09, Derek (freebsd lists) wrote:

Ah, you'll note: fork/exec implicated here.

Looks like this guy strikes again:
https://github.com/golang/go/issues/15658

It pains me to say but Go on FreeBSD is (and has always been) broken.  
Should be fine if you don't exec.  Something that might help, is 
setting GOMAXPROCS=1.


Derek

On 18-04-25 07:45 AM, Steven Hartland wrote:

Builds fine on 11.1-RELEASE-p6 here:

[00:04:02] Committing packages to repository
[00:04:02] Removing old packages
[00:04:02] Built ports: lang/go
[ports11-1-multiplay] [2018-04-25_11h37m16s] [committing:] Queued: 1 
Built: 1  Failed: 0  Skipped: 0  Ignored: 0  Tobuild: 0   Time: 00:04:01
[00:04:02] Logs: 
/usr/local/poudriere/data/logs/bulk/ports11-1-multiplay/2018-04-25_11h37m16s 


[00:04:02] Cleaning up

svn info
Path: .
Working Copy Root Path: /usr/local/poudriere/ports/multiplay
URL: https://svn.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 468275
Node Kind: directory
Schedule: normal
Last Changed Author: tobik
Last Changed Rev: 468275
Last Changed Date: 2018-04-25 11:08:41 + (Wed, 25 Apr 2018)


 Regards
 Steve

On 25/04/2018 12:07, Bjarne wrote:
I got a job to rebuild all packages every night, but since 
2018-04-05 building  /usr/ports/lang/go is failing.


Apparently 2018-04-05  some major changed was introduced, since 331 
pakackes was rebuilt. Not sure what it was, I saw nothing in UPATING.


Top of logfile:


Building lang/go

build started at Thu Apr  5 03:04:07 UTC 2018
port directory: /usr/ports/lang/go
package name: go-1.10.1,1
building for: FreeBSD freebsd_11-1-HEAD-job-03 11.1-RELEASE-p9 
FreeBSD 11.1-RELEASE-p9 amd64

maintained by: jlaff...@freebsd.org
Makefile ident:  $FreeBSD: head/lang/go/Makefile 466249 
2018-04-02 18:58:11Z jlaffaye $

Poudriere version: 3.2.6
Host OSVERSION: 1101001
Jail OSVERSION: 1101001

actually  build fails both on freebsd 10.3 and 11.1

Running poudriere testport -j freebsd_11-1 -p HEAD -i -o lang/go :


===>
=== 


=>> Recording filesystem state for prebuild... done
===
===>   go-1.10.1,1 depends on package: go14>=1.4 - found
===>  Configuring for go-1.10.1,1
=== 


===
===>  Building for go-1.10.1,1
cd /wrkdirs/usr/ports/lang/go/work/go/src && 
GOROOT=/wrkdirs/usr/ports/lang/go/work/go GOROOT_FINAL=/usr/local/go 
GOROOT_BOOTSTRAP=/usr/local/go14 GOBIN= GOARCH=amd64 GOOS=freebsd 
GO386=  /bin/sh make.bash

-ap: not found
go: not found
Building Go cmd/dist using /usr/local/go14.
Building Go toolchain1 using /usr/local/go14.
Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
Building Go toolchain2 using go_bootstrap and Go toolchain1.
runtime: gp: gp=0xc420499380, goid=38, gp->atomicstatus=2
runtime:  g:  g=0xc42c00, goid=0,  g->atomicstatus=0
fatal error: bad g->status in ready

runtime stack:
runtime.throw(0x6f776b, 0x16)
    /usr/local/go/src/runtime/panic.go:616 +0x81
runtime.ready(0xc420499380, 0x5, 0xc420499201)
    /usr/local/go/src/runtime/proc.go:601 +0x27b
runtime.goready.func1()
    /usr/local/go/src/runtime/proc.go:302 +0x38
runtime.systemstack(0x0)
    /usr/local/go/src/runtime/asm_amd64.s:409 +0x79
runtime.mstart()
    /usr/local/go/src/runtime/proc.go:1175

goroutine 37 [running]:
runtime.systemstack_switch()
    /usr/local/go/src/runtime/asm_amd64.s:363 fp=0xc4204a06c0 
sp=0xc4204a06b8 pc=0x450c00

runtime.goready(0xc420499380, 0x5)
    /usr/local/go/src/runtime/proc.go:301 +0x4b fp=0xc4204a06f0 
sp=0xc4204a06c0 pc=0x42a74b

runtime.readyWithTime(0xc4201a4c00, 0x5)
    /usr/local/go/src/runtime/sema.go:83 +0x41 fp=0xc4204a0710 
sp=0xc4204a06f0 pc=0x43a071

runtime.semrelease1(0x8885e4, 0x0)
    /usr/local/go/src/runtime/sema.go:194 +0x12d fp=0xc4204a0768 
sp=0xc4204a0710 pc=0x43a54d

sync.runtime_Semrelease(0x8885e4, 0xc4204a0700)
    /usr/local/go/src/runtime/sema.go:66 +0x34 fp=0xc4204a0788 
sp=0xc4204a0768 pc=0x439f84

sync.(*Mutex).Unlock(0x8885e0)
    /usr/local/go/src/sync/mutex.go:201 +0x75 fp=0xc4204a07b0 
sp=0xc4204a0788 pc=0x4674d5

sync.(*RWMutex).Unlock(0x8885e0)
    /usr/local/go/src/sync/rwmutex.go:132 +0x7e fp=0xc4204a07e0 
sp=0

Re: lang/go failes to build with poudriere, since 2018-04-05

2018-04-25 Thread Derek (freebsd lists) 

Ah, you'll note: fork/exec implicated here.

Looks like this guy strikes again:
https://github.com/golang/go/issues/15658

It pains me to say but Go on FreeBSD is (and has always been) 
broken.  Should be fine if you don't exec.  Something that might 
help, is setting GOMAXPROCS=1.


Derek

On 18-04-25 07:45 AM, Steven Hartland wrote:

Builds fine on 11.1-RELEASE-p6 here:

[00:04:02] Committing packages to repository
[00:04:02] Removing old packages
[00:04:02] Built ports: lang/go
[ports11-1-multiplay] [2018-04-25_11h37m16s] [committing:] 
Queued: 1 Built: 1  Failed: 0  Skipped: 0  Ignored: 0  Tobuild: 
0   Time: 00:04:01
[00:04:02] Logs: 
/usr/local/poudriere/data/logs/bulk/ports11-1-multiplay/2018-04-25_11h37m16s 


[00:04:02] Cleaning up

svn info
Path: .
Working Copy Root Path: /usr/local/poudriere/ports/multiplay
URL: https://svn.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 468275
Node Kind: directory
Schedule: normal
Last Changed Author: tobik
Last Changed Rev: 468275
Last Changed Date: 2018-04-25 11:08:41 + (Wed, 25 Apr 2018)


     Regards
     Steve

On 25/04/2018 12:07, Bjarne wrote:
I got a job to rebuild all packages every night, but since 
2018-04-05 building  /usr/ports/lang/go is failing.


Apparently 2018-04-05  some major changed was introduced, since 
331 pakackes was rebuilt. Not sure what it was, I saw nothing 
in UPATING.


Top of logfile:


Building lang/go

build started at Thu Apr  5 03:04:07 UTC 2018
port directory: /usr/ports/lang/go
package name: go-1.10.1,1
building for: FreeBSD freebsd_11-1-HEAD-job-03 11.1-RELEASE-p9 
FreeBSD 11.1-RELEASE-p9 amd64

maintained by: jlaff...@freebsd.org
Makefile ident:  $FreeBSD: head/lang/go/Makefile 466249 
2018-04-02 18:58:11Z jlaffaye $

Poudriere version: 3.2.6
Host OSVERSION: 1101001
Jail OSVERSION: 1101001

actually  build fails both on freebsd 10.3 and 11.1

Running poudriere testport -j freebsd_11-1 -p HEAD -i -o lang/go :


===>
=== 


=>> Recording filesystem state for prebuild... done
===>

===>   go-1.10.1,1 depends on package: go14>=1.4 - found
===>  Configuring for go-1.10.1,1
=== 


===
===>  Building for go-1.10.1,1
cd /wrkdirs/usr/ports/lang/go/work/go/src && 
GOROOT=/wrkdirs/usr/ports/lang/go/work/go 
GOROOT_FINAL=/usr/local/go GOROOT_BOOTSTRAP=/usr/local/go14 
GOBIN= GOARCH=amd64 GOOS=freebsd GO386=  /bin/sh make.bash

-ap: not found
go: not found
Building Go cmd/dist using /usr/local/go14.
Building Go toolchain1 using /usr/local/go14.
Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
Building Go toolchain2 using go_bootstrap and Go toolchain1.
runtime: gp: gp=0xc420499380, goid=38, gp->atomicstatus=2
runtime:  g:  g=0xc42c00, goid=0,  g->atomicstatus=0
fatal error: bad g->status in ready

runtime stack:
runtime.throw(0x6f776b, 0x16)
    /usr/local/go/src/runtime/panic.go:616 +0x81
runtime.ready(0xc420499380, 0x5, 0xc420499201)
    /usr/local/go/src/runtime/proc.go:601 +0x27b
runtime.goready.func1()
    /usr/local/go/src/runtime/proc.go:302 +0x38
runtime.systemstack(0x0)
    /usr/local/go/src/runtime/asm_amd64.s:409 +0x79
runtime.mstart()
    /usr/local/go/src/runtime/proc.go:1175

goroutine 37 [running]:
runtime.systemstack_switch()
    /usr/local/go/src/runtime/asm_amd64.s:363 
fp=0xc4204a06c0 sp=0xc4204a06b8 pc=0x450c00

runtime.goready(0xc420499380, 0x5)
    /usr/local/go/src/runtime/proc.go:301 +0x4b 
fp=0xc4204a06f0 sp=0xc4204a06c0 pc=0x42a74b

runtime.readyWithTime(0xc4201a4c00, 0x5)
    /usr/local/go/src/runtime/sema.go:83 +0x41 
fp=0xc4204a0710 sp=0xc4204a06f0 pc=0x43a071

runtime.semrelease1(0x8885e4, 0x0)
    /usr/local/go/src/runtime/sema.go:194 +0x12d 
fp=0xc4204a0768 sp=0xc4204a0710 pc=0x43a54d

sync.runtime_Semrelease(0x8885e4, 0xc4204a0700)
    /usr/local/go/src/runtime/sema.go:66 +0x34 
fp=0xc4204a0788 sp=0xc4204a0768 pc=0x439f84

sync.(*Mutex).Unlock(0x8885e0)
    /usr/local/go/src/sync/mutex.go:201 +0x75 
fp=0xc4204a07b0 sp=0xc4204a0788 pc=0x4674d5

sync.(*RWMutex).Unlock(0x8885e0)
    /usr/local/go/src/sync/rwmutex.go:132 +0x7e 
fp=0xc4204a07e0 sp=0xc4204a07b0 pc=0x46824e
syscall.forkExec(0xc4202f0440, 0x3d, 0xc4202aa1e0, 0x2, 0x2, 
0xc4204a09d8, 0x20, 0x0, 0xc4200aa5a0)
    /usr/local/go/src/syscall/exec_unix.go:199 +0x3e1 
fp=0xc4204a0900 sp=0xc4204a07e0 pc=0x46c031
syscall.StartProcess(0xc4202f0440, 0x3d, 0xc4202aa1e0, 0x2, 
0x2, 0xc4204a09d8, 0x2, 0x4, 0x0, 0x0)
    /usr/local/go/src/syscall/exec_unix.go:241 +0x64 
fp=0xc4204a0958 sp=0xc4204a0900 pc=0x46c484
os.startProcess(0xc4202f0440, 0x3d, 0xc4202aa1e0, 0x2, 0x2, 
0xc4204a0b80

Re: lang/go failes to build with poudriere, since 2018-04-05

2018-04-25 Thread Steven Hartland 

Builds fine on 11.1-RELEASE-p6 here:

[00:04:02] Committing packages to repository
[00:04:02] Removing old packages
[00:04:02] Built ports: lang/go
[ports11-1-multiplay] [2018-04-25_11h37m16s] [committing:] Queued: 1  
Built: 1  Failed: 0  Skipped: 0  Ignored: 0  Tobuild: 0   Time: 00:04:01
[00:04:02] Logs: 
/usr/local/poudriere/data/logs/bulk/ports11-1-multiplay/2018-04-25_11h37m16s

[00:04:02] Cleaning up

svn info
Path: .
Working Copy Root Path: /usr/local/poudriere/ports/multiplay
URL: https://svn.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 468275
Node Kind: directory
Schedule: normal
Last Changed Author: tobik
Last Changed Rev: 468275
Last Changed Date: 2018-04-25 11:08:41 + (Wed, 25 Apr 2018)


    Regards
    Steve

On 25/04/2018 12:07, Bjarne wrote:
I got a job to rebuild all packages every night, but since 2018-04-05 
building  /usr/ports/lang/go is failing.


Apparently 2018-04-05  some major changed was introduced, since 331 
pakackes was rebuilt. Not sure what it was, I saw nothing in UPATING.


Top of logfile:


Building lang/go

build started at Thu Apr  5 03:04:07 UTC 2018
port directory: /usr/ports/lang/go
package name: go-1.10.1,1
building for: FreeBSD freebsd_11-1-HEAD-job-03 11.1-RELEASE-p9 FreeBSD 
11.1-RELEASE-p9 amd64

maintained by: jlaff...@freebsd.org
Makefile ident:  $FreeBSD: head/lang/go/Makefile 466249 2018-04-02 
18:58:11Z jlaffaye $

Poudriere version: 3.2.6
Host OSVERSION: 1101001
Jail OSVERSION: 1101001

actually  build fails both on freebsd 10.3 and 11.1

Running poudriere testport -j freebsd_11-1 -p HEAD -i -o lang/go :


===
=== 


=>> Recording filesystem state for prebuild... done
===
===>   go-1.10.1,1 depends on package: go14>=1.4 - found
===>  Configuring for go-1.10.1,1
=== 


===
===>  Building for go-1.10.1,1
cd /wrkdirs/usr/ports/lang/go/work/go/src && 
GOROOT=/wrkdirs/usr/ports/lang/go/work/go GOROOT_FINAL=/usr/local/go  
GOROOT_BOOTSTRAP=/usr/local/go14 GOBIN= GOARCH=amd64 GOOS=freebsd  
GO386=  /bin/sh make.bash

-ap: not found
go: not found
Building Go cmd/dist using /usr/local/go14.
Building Go toolchain1 using /usr/local/go14.
Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
Building Go toolchain2 using go_bootstrap and Go toolchain1.
runtime: gp: gp=0xc420499380, goid=38, gp->atomicstatus=2
runtime:  g:  g=0xc42c00, goid=0,  g->atomicstatus=0
fatal error: bad g->status in ready

runtime stack:
runtime.throw(0x6f776b, 0x16)
    /usr/local/go/src/runtime/panic.go:616 +0x81
runtime.ready(0xc420499380, 0x5, 0xc420499201)
    /usr/local/go/src/runtime/proc.go:601 +0x27b
runtime.goready.func1()
    /usr/local/go/src/runtime/proc.go:302 +0x38
runtime.systemstack(0x0)
    /usr/local/go/src/runtime/asm_amd64.s:409 +0x79
runtime.mstart()
    /usr/local/go/src/runtime/proc.go:1175

goroutine 37 [running]:
runtime.systemstack_switch()
    /usr/local/go/src/runtime/asm_amd64.s:363 fp=0xc4204a06c0 
sp=0xc4204a06b8 pc=0x450c00

runtime.goready(0xc420499380, 0x5)
    /usr/local/go/src/runtime/proc.go:301 +0x4b fp=0xc4204a06f0 
sp=0xc4204a06c0 pc=0x42a74b

runtime.readyWithTime(0xc4201a4c00, 0x5)
    /usr/local/go/src/runtime/sema.go:83 +0x41 fp=0xc4204a0710 
sp=0xc4204a06f0 pc=0x43a071

runtime.semrelease1(0x8885e4, 0x0)
    /usr/local/go/src/runtime/sema.go:194 +0x12d fp=0xc4204a0768 
sp=0xc4204a0710 pc=0x43a54d

sync.runtime_Semrelease(0x8885e4, 0xc4204a0700)
    /usr/local/go/src/runtime/sema.go:66 +0x34 fp=0xc4204a0788 
sp=0xc4204a0768 pc=0x439f84

sync.(*Mutex).Unlock(0x8885e0)
    /usr/local/go/src/sync/mutex.go:201 +0x75 fp=0xc4204a07b0 
sp=0xc4204a0788 pc=0x4674d5

sync.(*RWMutex).Unlock(0x8885e0)
    /usr/local/go/src/sync/rwmutex.go:132 +0x7e fp=0xc4204a07e0 
sp=0xc4204a07b0 pc=0x46824e
syscall.forkExec(0xc4202f0440, 0x3d, 0xc4202aa1e0, 0x2, 0x2, 
0xc4204a09d8, 0x20, 0x0, 0xc4200aa5a0)
    /usr/local/go/src/syscall/exec_unix.go:199 +0x3e1 
fp=0xc4204a0900 sp=0xc4204a07e0 pc=0x46c031
syscall.StartProcess(0xc4202f0440, 0x3d, 0xc4202aa1e0, 0x2, 0x2, 
0xc4204a09d8, 0x2, 0x4, 0x0, 0x0)
    /usr/local/go/src/syscall/exec_unix.go:241 +0x64 
fp=0xc4204a0958 sp=0xc4204a0900 pc=0x46c484
os.startProcess(0xc4202f0440, 0x3d, 0xc4202aa1e0, 0x2, 0x2, 
0xc4204a0b80, 0xc420403400, 0x3e, 0x3e)
    /usr/local/go/src/os/exec_posix.go:46 +0x1f1 fp=0xc4204a0a30 
sp=0xc4204a0958 pc=0x48ce21
os.StartProcess(0xc4202f0440, 0x3d, 0xc4202aa1e0, 0x2, 0x2, 
0xc4204a0b80, 0x0, 0x0, 0x1)
    /usr/local/go/src/os/exec.go:102 +0x7c fp=0xc4204a0a88 
sp=0xc4204a0a30 pc=0x48c93c

os/exec.(*Cmd).Start(0xc4201809a0,