[Boost-testing] Re: More page not found errors... Was: Code Warrior Serialization test failures

From: Misha Bergal (mbergal_at_[hidden])
Date: 2005-03-07 18:00:50

Rene Rivera <grafik.list_at_[hidden]> writes:

> Rene Rivera wrote:
>> Rene Rivera wrote:
>> 
>>> ...or the processing of the logs is stalled.
>> The processing at metacomm is definitely stalled.

Was our fault.

>>  Just checked and
>> there are new uploaded test but nothing new is shown in the result
>> pages.
> The processing is back now :-) .. But now I see "Page not found!"
> errors everywhere.

Sorry, folks. 

Last night we have implemented several major improvements in our log
processing system, which should give as a turnaround times of about 30
minutes. The brief summary of changes:

* The results are uploaded to the target web server as one big zip
  file (reduced the upload time by factor of 30)

* Fixed problem with new version of xsltproc not being able to process
  files with spaces in them (runner id with spaces). 

* The previous regression results XSL stylesheet has been rewritten to
  use indexes (keys), reducing the processing time 

* Partially implemented incremental rebuild process, new results
  upload doesn't cause the full rebuild of everything.

Here is the list of known unresolved problems:

* Dirxion test still results still reference libs for which there are
  no test results (link goes to "page no found!"). I actually though
  that we've fixed that. Will look into it.

Please report all other problems to the boost-testing mailing list, we
will try to resolve them ASAP.

Thanks for understanding.

-- 
Misha Bergal
MetaCommunications Engineering