Date: Fri, 27 Apr 2018 09:32:32 +0100 From: Steven Hartland <killing@multiplay.co.uk> To: Bjarne <bjb@darco.dk>, "Derek (freebsd lists)" <482254ac@razorfever.net>, freebsd-ports@freebsd.org Subject: Re: lang/go failes to build with poudriere, since 2018-04-05 Message-ID: <3b301aee-1f76-34b2-c630-b8fb814007a0@multiplay.co.uk> In-Reply-To: <d141796c-b6af-3c74-a71f-649d2a325c80@darco.dk> References: <405cd11b-48c4-2b82-561e-ae9cada253bb@darco.dk> <8859afde-29a5-79d6-9b00-6b97df687b94@multiplay.co.uk> <874d92d2-55bc-6dc1-5f6e-f57dc5ab5381@razorfever.net> <348668e3-fff4-1f6a-47a2-9066f059cf21@multiplay.co.uk> <0b5e2eb2-8bfd-f60e-abd1-2c01021b2b47@darco.dk> <b70b5506-df49-5a25-5685-c6810e06eaf6@multiplay.co.uk> <d141796c-b6af-3c74-a71f-649d2a325c80@darco.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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 +0000 (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-unsubscribe@freebsd.org" >>>>>> >>>>> >>>> >>> >>> -- >>> mvh, >>> Bjarne >> > > -- > mvh, > Bjarne
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3b301aee-1f76-34b2-c630-b8fb814007a0>