There should be helpful log messages in the output from "maint/checkbuilds", but I don't see anything that matches what I expect to see. It looks like there's some sketchy perl code that doesn't make a lot of sense: ----8<---- 93 $OUTFD = OUTFD; ... 980 sub RunMPD { 981 # We need to background the mpd. 982 # If there is already an mpd running (for us), we want to stop it 983 my $mpdlocalsock = "/tmp/mpd2.console_". $ENV{"LOGNAME"}; 984 my $rc = 0; 985 if (-S $mpdlocalsock) { 986 system "$instdir/bin/mpdallexit"; 987 $rc = $? >> 8; 988 if ($rc != 0) { 989 print $OUTFD "Error running $instdir/bin/mpdallexit before starting MPD ($mpdlocalsock exists)\n"; 990 } 991 } 992 #system "$instdir/bin/mpd -d"; 993 # Try to background mpd 994 system "$instdir/bin/mpd &"; 995 $rc = $? >> 8; 996 if ($rc != 0) { 997 print $OUTFD "Error running $instdir/bin/mpd -d\n"; 998 } 999 else { 1000 print $OUTFD "Started mpd in demon mode\n"; 1001 } 1002 # Wait for the mpd to start 1003 sleep 1; 1004 return; 1005 } ----8<---- Is that bareword initialization on line 93 some sort of long-broken Perl4-ism? Or was it left that way so that "debug logging" could be enabled by a carefully placed "open(OUTFD,...)" call? I suppose a cheesier version is to change the OUTFD bareword to an STDOUT bareword, which will have the intended effect when not under "use strict", although in a totally gross way. Bill, because it's an older perl script, I'm guessing you wrote this. Is the output intentionally disabled because it causes a problem in normal use? Is there any reason that I shouldn't just replace line 93 with this? ----8<---- my $OUTFD = *STDOUT{IO}; ----8<---- -Dave On Apr 12, 2011, at 3:55 PM CDT, Dave Goodell wrote:
I dislike working on MPD as much as the next guy, but is MPD actually broken? Or is something just a bit off in the way the tests are being run or the way that our make/install steps have changed? I suspect this is a simpler issue, although I haven't done any investigation.
-Dave
On Apr 12, 2011, at 3:37 PM CDT, Pavan Balaji wrote:
Given that: (1) we no longer have any maintainers for mpd, and (2) it has been deprecated through the 1.3 series, I propose that we remove MPD in 1.4. Thoughts?
-- Pavan
On 04/12/2011 02:21 PM, Rajeev Thakur wrote:
Looks like they have enabled writes now. You are right. The MPD and SMPD tests are broken.
Rajeev
On Apr 12, 2011, at 2:19 PM, Rajeev Thakur wrote:
They have made the web site read only while they are investigating a security incident. Until they enable writes, we won't know whether the tests are broken or it is the web site problem.
Rajeev
On Apr 12, 2011, at 2:11 PM, Pavan Balaji wrote:
http://www.mcs.anl.gov/research/projects/mpich2/nightly/old
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
-- Pavan Balaji http://www.mcs.anl.gov/~balaji