-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This output looks a lot better: http://paste.drizzle.org/show/491/
I updated the port Makefile to compile with gcc 4.5, and I adjusted the ldconfig configuration. I also realized that the port did not call ./config/autorun.sh before the configuration step, so maybe that messed up the build and resulting executable. I am trying "gmake test-all" now, and I'll paste that output when it's ready. If things go well, I can post an updated FreeBSD port for you to try on your FreeBSD build machine. Regards, Greg On 4/29/11 10:47 AM, Patrick Crews wrote: > I'll have to dig into this, but something appears to be terribly borked > with tests related to the transaction log / innodb transaction log. > The tests are running, but we aren't seeing expected output : ( > You can always run this from the drizzle/tests dir: > ./dbqp --suite=transaction_log --debug --verbose > It is *quite* chatty, but it might give some insight. > > As for recreating the issues we saw on our FreeBSD machine, you can try > to create a drizzle branch somewhere with a ridiculously long path name > (something like 100 chars long) - that was the only case where I saw > things go awry (ie it was smooth as butter in my local repo) ; ) > > I'm stuck a conference now, so my bandwidth is limited...will see what I > can find out in a couple of days. > > Many, many thanks for helping out with this! > Patrick > > On Fri, Apr 29, 2011 at 7:36 AM, Greg Larkin <[email protected] > <mailto:[email protected]>> wrote: > > On 3/28/11 3:16 PM, Patrick Crews wrote: >> Hi. Here is a paste of what was happening. I suspect it has > something >> to do with path lengths as a clean branch / build / test worked > fine in >> my repo. We were also running into some issues with the socket path >> length being too long. > >> http://paste.drizzle.org/show/459/ > >> Here is what I saw going wrong in the hudson repo: >> 1) The server process seems to 'go rogue'. It holds ports and exists, >> but you can't connect to it >> 2) Nothing can connect to the server and it continues to live even >> after cleaning up >> 3) This *only* happens in the build-freebsd branch...works a-ok in my >> own repo!!! (wth?) >> 4) This happens with both test-run.pl <http://test-run.pl> > <http://test-run.pl/> *and* dbqp, >> so it isn't an issue with the either test-runner > >> 24 Mar 2011 12:04:29 VERBOSE: Reordering testcases to optimize test >> execution... >> 24 Mar 2011 12:04:29 INFO: Found 565 test(s) for execution >> 24 Mar 2011 12:04:29 INFO: Creating 1 bot(s) >> 24 Mar 2011 12:04:29 INFO: Taking clean db snapshot... >> 24 Mar 2011 12:04:29 INFO: bot0 server: >> 24 Mar 2011 12:04:29 INFO: NAME: s0 >> 24 Mar 2011 12:04:29 INFO: MASTER_PORT: 9306 >> 24 Mar 2011 12:04:29 INFO: DRIZZLE_TCP_PORT: 9307 >> 24 Mar 2011 12:04:29 INFO: MC_PORT: 9308 >> 24 Mar 2011 12:04:29 INFO: PBMS_PORT: 9309 >> 24 Mar 2011 12:04:29 INFO: RABBITMQ_NODE_PORT: 9310 >> 24 Mar 2011 12:04:29 INFO: VARDIR: /usr/home/hudson/hudson/ >> workspace/drizzle-build-freebsd-8.1/tests/workdir/bot0/s0/var >> 24 Mar 2011 12:04:29 INFO: STATUS: 1 >> ^C >> # I killed this here are it was dragging and I knew it would fail. > The >> server zombi-fies regardless of user input >> Detected <Ctrl>+c, shutting down and cleaning up... >> 24 Mar 2011 12:05:19 INFO: Stopping all running servers... > >> [hudson@orisndriz10 ~/hudson/workspace/drizzle-build-freebsd-8.1]$ > sockstat >> USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN >> ADDRESS >> hudson drizzled 60030 11 tcp4 127.0.0.1:9307 > <http://127.0.0.1:9307> >> <http://127.0.0.1:9307/> *:* >> hudson drizzled 60030 13 tcp4 127.0.0.1:9306 > <http://127.0.0.1:9306> >> <http://127.0.0.1:9306/> *:* >> hudson drizzled 60030 14 stream > > /usr/home/hudson/hudson/workspace/drizzle-build-freebsd-8.1/tests/workdir/bot0/s0/var/s0.sock >> <snip> > >> [hudson@orisndriz10 ~/hudson/workspace/drizzle-build-freebsd-8.1]$ >> client/drizzle -uroot -p9306 >> ERROR: >> drizzle_state_addrinfo:getaddrinfo:Invalid value for hints > > > > Hi all, > > I built the latest version of drizzle on an amd64 virtual machine > running FreeBSD 8.2 and ran "gmake test-dbqp" to see what would happen. > Here are the results of that run: > http://paste.drizzle.org/show/490/ > > It looks like I had more luck that the output posted by Patrick, but can > anyone scan it to see if there are any other problems? > > I don't have any ideas about the problems experienced in Patrick's test > run, but perhaps I can get a shell login on that machine so I can run > some diagnostic commands while the test is in progress. > > Thank you, > Greg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk27PS4ACgkQ0sRouByUApDMNQCfRUr1Xb76oNbyRijsP4wiiBI0 iP8An1SaNq3ejsgDmVs32RwvM2AIdVeh =FRSx -----END PGP SIGNATURE----- _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
