Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@stdcxx.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <21282005.post@talk.nabble.com>
Date: Sun, 4 Jan 2009 14:11:18 -0800 (PST)
From: Martin Sebor <sebor@roguewave.com>
To: dev@stdcxx.apache.org
Subject: Re: Outdated nightly builds results on apache.org
In-Reply-To: <21269973.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: 
 <F355595021D34947A612599E91EAA27A16E3A3A1E6@EPBYMINSA0009.epam.com>
 <49428FCB.4030208@gmail.com> <21025075.post@talk.nabble.com>
 <4947D627.4080909@roguewave.com> <21269973.post@talk.nabble.com>


An update on the results: they are now current, but all testsuite builds
fail with errors in the Rogue Wave test driver file lockfile.cpp (see
below). I've just committed a fix for this error so once it's picked up
by the nightly test infrastructure we should start seeing some hopefully
more useful build results, probably sometime tomorrow.

$(TOPDIR)/tests/src/lockfile.cpp: In destructor 'virtual
RWQELockFile::~RWQELockFile()':
$(TOPDIR)/tests/src/lockfile.cpp:161: error: 'free' was not declared in this
scope
$(TOPDIR)/tests/src/lockfile.cpp: In member function 'void
RWQELockFile::copyName(const char*)':
$(TOPDIR)/tests/src/lockfile.cpp:218: error: 'malloc' was not declared in
this scope
gmake: *** [lockfile.o] Error 1

Martin Sebor wrote:
> 
> 
> Andrew Black-5 wrote:
>> 
>> Greetings Martin
>> 
>> I took a glance at the logs for the 4.2.x exports, and observe the
>> following error message:
>> 
>> /usr/bin/scp: Argument list too long
>> 
>> This particular message is generated when the exporter script attempts
>> to copy the generated files out to Apache.  The solution as I see it
>> will be to manually perform the export, splitting the export list into
>> pieces to avoid overloading scp.  You'll then need to manually update
>> the cache file as is done at the end of static_export.sh.
>> 
>> 
> 
> It turns out that cleaning out the $HOME/.stdcxx-cache/4.2.x directory
> and re-running the $HOME/bin/pubres.sh script fixed the problem. There
> were over 30,000 files in the directory, nearly half of them empty. All
> the empty ones were from sometime in September. There still are a bunch
> of them in $HOME/.stdcxx-cache/4.3.x although not nearly as many.
> 
> I'm in the process of running $HOME/bin/mkxviews on people.apache.org
> now. When it's done and when the Web server picks up the changes the
> 4.2.x results should be up to date. Let's keep an eye on the results
> page over the next few days to make sure the problem is gone:
> 
> http://stdcxx.apache.org/builds/4.2.x/
> 
> 
> 
>> 
>> --Andrew Black
>> 
>> Martin Sebor wrote:
>>> The page has been updated but it looks like all the builds are stale
>>> (33 days old). Let me see if I can find the time to figure out what's
>>> going on tomorrow. If not, I'm travelling starting Wednesday so it
>>> might need to wait until the 26th.
>>> 
>>> 
>>> Martin Sebor-2 wrote:
>>>> Farid Zaripov wrote:
>>>>>   The latest nightly builds report for 4.2.x branch generated
>>>>> Tue Nov 11 15:00:39 UTC 2008 - over a month ago.
>>>> Weird, the others are up to date.
>>>>
>>>> [...investigating...]
>>>>
>>>> I think I've got it. Seems that the SSL certificate had expired
>>>> and needed to be refreshed in order for svn to proceed with source
>>>> code update.
>>>>
>>>> The page is up to date now (it will take a bit for the web server
>>>> to pick it up).
>>>>
>>>> Martin
>>>>
>>>>> Farid.
>>>>>
>>>>
>>>>
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Outdated-nightly-builds-results-on-apache.org-tp20976643p21282005.html
Sent from the stdcxx-dev mailing list archive at Nabble.com.