Hello,
We saw there was a problem with buildbot about the consultants listing for 
"infolearn”.
Is there anything we can do? Should we reapply/resend?


This is the infolearn XML file



 <?xml version="1.0" encoding="UTF-8"?>
 <consultants>


     <consultant>
         <name>infolearn - TEST4U.eu</name>
         <country>Global</country>
         <practice>Certification</practice>
         <practice>Training</practice>
         <practice>Development</practice>
        <description>
             Infolearn offers a complete range of Apache OpenOffice
             (Writer, Calc, Impress, Base) in-application tests through TEST4U.
             TEST4U is an automated test which cooperates with the actual
             applications instead of flash simulation and can be used to:  
             - prepare the students for certification examinations (e.g. 
ECDL/ICDL, DIPLOMA etc)
             - train and assess employees.
             TEST4U with its 700 000 users and 7 000 000 000 (yes 7 billion)
             served questions since 2003 is worldwide the only application 
             that works with all these applications in a real working 
environment.
         </description>
         <website>https://www.test4u.eu/en/e-tests/apache-openoffice</website>
         <email>i...@test4u.eu</email>
         <phone>+30 2310 888 771</phone>
     </consultant>



  </consultants>



Greeting from Greece
The TEST4U Team





-----Original Message-----
From: Kay Schenk [mailto:kay.sch...@gmail.com]
Sent: Sunday, July 26, 2015 8:01 PM
To: dev@openoffice.apache.org
Subject: Re: problem with web site staging build

On 07/26/2015 12:48 AM, Andrea Pescetti wrote:
> On 25/07/2015 Kay Schenk wrote:
>> I just committed the new consultants listing for "infolearn" to
>> /openoffice/ooo-site/trunk/content/bizdev/consultants.html
>> and much to my surprise, The buldbot has erred out.
>> See info at:
>> https://ci.apache.org/builders/ooo-site-site-staging/builds/6/steps/c
>> ompile/logs/stdio
>>
>
> Reading the logs, it seems this has nothing to do with your specific
> updated, but rather with two filenames that use non-ASCII characters.
>
> I've fixed the two reported ones (well this is not necessarily a bug
> in the file names; they always worked so far, so this may be an issue
> with the new buildbot setup) to check:
>
> http://svn.apache.org/r1692695
>
> http://svn.apache.org/r1692696
>
> Let's see if this gets rid of warnings. The affected files were unused
> (even if I took care of renaming where helpful) and had names like
> (hoping they get rendered correctly in mail clients): excepții.css 
> with a special t and ProjectMembersh…equestHelp.html with a literal "..."
> character, of course due to some mistake.
>
> Regards,
>   Andrea.

Thanks for looking deeper into this, Andrea. The most recent buildbot log 
indicates we still have issues. So, it does look like a new issue with the 
buildbot setup at this point.



--
--------------------------------------------
MzK

"Way down deep, we're all motivated by
 the  same urges.  Cats have the courage  to live by them."
                        -- Jim Davis


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org


---
Αυτό το e-mail ελέγχθηκε για ιούς από το πρόγραμμα Avast antivirus.
https://www.avast.com/antivirus


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to