Re: Buildbots

[Carl Marcum]

Hi Gavin,

On 11/16/21 7:15 AM, Gavin McDonald wrote:

Hi Matthias,

On Tue, Nov 16, 2021 at 12:32 PM Matthias Seidel 
wrote:


Hi Gavin,

Am 16.11.21 um 09:37 schrieb Gavin McDonald:

Hi All.

Ok so I am making progress.

The nightly x64 build is running fine. as are the rat builds.
I'll get the 41 branch added today - should we also do a 42 branch build?

Thanks!

It would be ideal to have all branches (trunk/AOO42X/AOO41X).


Yep no problem



As for the win10 builds I am working on those now.

I am at a stage in the win10 build where it wants dlls and exe files
(listed below) from an
'external' directory located on the machine but outside of the build
itself. These get copied in
during a build step.




No objection against copying these files from whatever location. They
haven't changed in the last years but it is always good when we can
access them.

If you take the files from the old buildbot everything should be the
correct version.

If you have questions about the Windows builds, feel free to contact me.


Perfect, new 'openoffice-externals' repository created, I'll put them in
there
and have the build(s) pull them in from there.




Regards,

Matthias


/

As can be seen at:


https://ci.apache.org/builders/openoffice-win7/builds/737/steps/externals/logs/stdio

On Sun, Nov 14, 2021 at 9:54 PM Carl Marcum  wrote:


Hi Gavin,

On 11/14/21 2:16 PM, Gavin McDonald wrote:

Hi All,

As the current Buildbots arent really working, nodes offline etc, I

thought

this would be the best time to migrate your builds over to our newer
replacement
buildbot 3.2 over at ci2.apache.org .

I'll do my best to get them all running as passing as best they can,

and

will update this thread with any questions or messages.

My first query is seeing as we have no more i386 or FreeBSD

agents/nodes,

I'll probably just go ahead and remove those from the new config file.

HTH


I just realized I had somehow missed your original email about migrating
andwas discussing getting with you.

Thanks for working on this.

Let us know if you have any questions.

Best regards,
Carl





Can you point me to info on the tech stack used for the linux64 
buildbots like OS platform and how it works.


I'd like to look at future changes that could be made and I'm not 
suggesting changing anything your doing now:


A couple questions:
Is it possible to use docker containers to build with?

We have a build verification test suite using JUnit but it requires a GUI.
Are there any options to add something like this to a workflow?

Thanks again for working on this!
Best regards,
Carl

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

Re: Buildbots

[Gavin McDonald]

Hi Matthias,

On Tue, Nov 16, 2021 at 12:32 PM Matthias Seidel 
wrote:

> Hi Gavin,
>
> Am 16.11.21 um 09:37 schrieb Gavin McDonald:
> > Hi All.
> >
> > Ok so I am making progress.
> >
> > The nightly x64 build is running fine. as are the rat builds.
> > I'll get the 41 branch added today - should we also do a 42 branch build?
>
> Thanks!
>
> It would be ideal to have all branches (trunk/AOO42X/AOO41X).
>

Yep no problem


> >
> > As for the win10 builds I am working on those now.
> >
> > I am at a stage in the win10 build where it wants dlls and exe files
> > (listed below) from an
> > 'external' directory located on the machine but outside of the build
> > itself. These get copied in
> > during a build step.
> >
> 
>
> No objection against copying these files from whatever location. They
> haven't changed in the last years but it is always good when we can
> access them.
>
> If you take the files from the old buildbot everything should be the
> correct version.
>
> If you have questions about the Windows builds, feel free to contact me.
>

Perfect, new 'openoffice-externals' repository created, I'll put them in
there
and have the build(s) pull them in from there.



> Regards,
>
>Matthias
>
> >
> > /
> >
> > As can be seen at:
> >
> https://ci.apache.org/builders/openoffice-win7/builds/737/steps/externals/logs/stdio
> >
> > On Sun, Nov 14, 2021 at 9:54 PM Carl Marcum  wrote:
> >
> >> Hi Gavin,
> >>
> >> On 11/14/21 2:16 PM, Gavin McDonald wrote:
> >>> Hi All,
> >>>
> >>> As the current Buildbots arent really working, nodes offline etc, I
> >> thought
> >>> this would be the best time to migrate your builds over to our newer
> >>> replacement
> >>> buildbot 3.2 over at ci2.apache.org .
> >>>
> >>> I'll do my best to get them all running as passing as best they can,
> and
> >>> will update this thread with any questions or messages.
> >>>
> >>> My first query is seeing as we have no more i386 or FreeBSD
> agents/nodes,
> >>> I'll probably just go ahead and remove those from the new config file.
> >>>
> >>> HTH
> >>>
> >> I just realized I had somehow missed your original email about migrating
> >> andwas discussing getting with you.
> >>
> >> Thanks for working on this.
> >>
> >> Let us know if you have any questions.
> >>
> >> Best regards,
> >> Carl
> >>
> >
>
>

-- 

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team

Re: Buildbots

[Matthias Seidel]

Hi Gavin,

Am 16.11.21 um 09:37 schrieb Gavin McDonald:
> Hi All.
>
> Ok so I am making progress.
>
> The nightly x64 build is running fine. as are the rat builds.
> I'll get the 41 branch added today - should we also do a 42 branch build?

Thanks!

It would be ideal to have all branches (trunk/AOO42X/AOO41X).

>
> As for the win10 builds I am working on those now.
>
> I am at a stage in the win10 build where it wants dlls and exe files
> (listed below) from an
> 'external' directory located on the machine but outside of the build
> itself. These get copied in
> during a build step.
>
> These files have been previously uploaded manually to the buildbot
> node/agent. I'd like to stop that
> practice; and change the build so that it pulls them in from a repository
> instead. We can create a new
> gitr repo called openoffice-externals and put them in there. This method
> has the added advantage that
> the project can then manage these externals themselves,
> adding/updating/deleting/whatever from the
> repo and the build will pull those in each time.
>
> Thoughts? My only query really was one of whether or not these libraries
> should not be available to the
> public, (I don't see why) in which case I would have to rethink this
> strategy. If I can get replies ASAP on
> this please so that I can continue to migrate the builds.
>
> Thanks
>
> /
>
> '/cygdrive/e/slave14/aoo-win7/external/gdiplus/gdiplus.dll'
> '/cygdrive/e/slave14/aoo-win7/external/dbghelp/dbghelp.dll'
> '/cygdrive/e/slave14/aoo-win7/external/msm90/Microsoft_VC90_CRT_x86.msm'
> '/cygdrive/e/slave14/aoo-win7/external/msm90/policy_9_0_Microsoft_VC90_CRT_x86.msm'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp100/msvcr100.dll'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp71'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp71/msvcp71.dll'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp71/msvcr71.dll'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp80'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp80/msvcp80.dll'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp80/msvcr80.dll'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp90/Microsoft.VC90.CRT.manifest'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp90/msvcm90.dll'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp90/msvcp90.dll'
> '/cygdrive/e/slave14/aoo-win7/external/msvcp90/msvcr90.dll'
> '/cygdrive/e/slave14/aoo-win7/external/vcredist/vcredist_x64.exe'
> '/cygdrive/e/slave14/aoo-win7/external/vcredist/vcredist_x86.exe'
> '/cygdrive/e/slave14/aoo-win7/external/vcredist/old'
> '/cygdrive/e/slave14/aoo-win7/external/vcredist/old/vcredist_x64.exe'
> '/cygdrive/e/slave14/aoo-win7/external/vcredist/old/vcredist_x86.exe'

No objection against copying these files from whatever location. They
haven't changed in the last years but it is always good when we can
access them.

If you take the files from the old buildbot everything should be the
correct version.

If you have questions about the Windows builds, feel free to contact me.

Regards,

   Matthias

>
> /
>
> As can be seen at:
> https://ci.apache.org/builders/openoffice-win7/builds/737/steps/externals/logs/stdio
>
> On Sun, Nov 14, 2021 at 9:54 PM Carl Marcum  wrote:
>
>> Hi Gavin,
>>
>> On 11/14/21 2:16 PM, Gavin McDonald wrote:
>>> Hi All,
>>>
>>> As the current Buildbots arent really working, nodes offline etc, I
>> thought
>>> this would be the best time to migrate your builds over to our newer
>>> replacement
>>> buildbot 3.2 over at ci2.apache.org .
>>>
>>> I'll do my best to get them all running as passing as best they can, and
>>> will update this thread with any questions or messages.
>>>
>>> My first query is seeing as we have no more i386 or FreeBSD agents/nodes,
>>> I'll probably just go ahead and remove those from the new config file.
>>>
>>> HTH
>>>
>> I just realized I had somehow missed your original email about migrating
>> andwas discussing getting with you.
>>
>> Thanks for working on this.
>>
>> Let us know if you have any questions.
>>
>> Best regards,
>> Carl
>>
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Buildbots

[Gavin McDonald]

Hi All.

Ok so I am making progress.

The nightly x64 build is running fine. as are the rat builds.
I'll get the 41 branch added today - should we also do a 42 branch build?

As for the win10 builds I am working on those now.

I am at a stage in the win10 build where it wants dlls and exe files
(listed below) from an
'external' directory located on the machine but outside of the build
itself. These get copied in
during a build step.

These files have been previously uploaded manually to the buildbot
node/agent. I'd like to stop that
practice; and change the build so that it pulls them in from a repository
instead. We can create a new
gitr repo called openoffice-externals and put them in there. This method
has the added advantage that
the project can then manage these externals themselves,
adding/updating/deleting/whatever from the
repo and the build will pull those in each time.

Thoughts? My only query really was one of whether or not these libraries
should not be available to the
public, (I don't see why) in which case I would have to rethink this
strategy. If I can get replies ASAP on
this please so that I can continue to migrate the builds.

Thanks

/

'/cygdrive/e/slave14/aoo-win7/external/gdiplus/gdiplus.dll'
'/cygdrive/e/slave14/aoo-win7/external/dbghelp/dbghelp.dll'
'/cygdrive/e/slave14/aoo-win7/external/msm90/Microsoft_VC90_CRT_x86.msm'
'/cygdrive/e/slave14/aoo-win7/external/msm90/policy_9_0_Microsoft_VC90_CRT_x86.msm'
'/cygdrive/e/slave14/aoo-win7/external/msvcp100/msvcr100.dll'
'/cygdrive/e/slave14/aoo-win7/external/msvcp71'
'/cygdrive/e/slave14/aoo-win7/external/msvcp71/msvcp71.dll'
'/cygdrive/e/slave14/aoo-win7/external/msvcp71/msvcr71.dll'
'/cygdrive/e/slave14/aoo-win7/external/msvcp80'
'/cygdrive/e/slave14/aoo-win7/external/msvcp80/msvcp80.dll'
'/cygdrive/e/slave14/aoo-win7/external/msvcp80/msvcr80.dll'
'/cygdrive/e/slave14/aoo-win7/external/msvcp90/Microsoft.VC90.CRT.manifest'
'/cygdrive/e/slave14/aoo-win7/external/msvcp90/msvcm90.dll'
'/cygdrive/e/slave14/aoo-win7/external/msvcp90/msvcp90.dll'
'/cygdrive/e/slave14/aoo-win7/external/msvcp90/msvcr90.dll'
'/cygdrive/e/slave14/aoo-win7/external/vcredist/vcredist_x64.exe'
'/cygdrive/e/slave14/aoo-win7/external/vcredist/vcredist_x86.exe'
'/cygdrive/e/slave14/aoo-win7/external/vcredist/old'
'/cygdrive/e/slave14/aoo-win7/external/vcredist/old/vcredist_x64.exe'
'/cygdrive/e/slave14/aoo-win7/external/vcredist/old/vcredist_x86.exe'

/

As can be seen at:
https://ci.apache.org/builders/openoffice-win7/builds/737/steps/externals/logs/stdio

On Sun, Nov 14, 2021 at 9:54 PM Carl Marcum  wrote:

> Hi Gavin,
>
> On 11/14/21 2:16 PM, Gavin McDonald wrote:
> > Hi All,
> >
> > As the current Buildbots arent really working, nodes offline etc, I
> thought
> > this would be the best time to migrate your builds over to our newer
> > replacement
> > buildbot 3.2 over at ci2.apache.org .
> >
> > I'll do my best to get them all running as passing as best they can, and
> > will update this thread with any questions or messages.
> >
> > My first query is seeing as we have no more i386 or FreeBSD agents/nodes,
> > I'll probably just go ahead and remove those from the new config file.
> >
> > HTH
> >
> I just realized I had somehow missed your original email about migrating
> andwas discussing getting with you.
>
> Thanks for working on this.
>
> Let us know if you have any questions.
>
> Best regards,
> Carl
>


-- 

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team

Re: Buildbots

[Carl Marcum]

Hi Gavin,

On 11/14/21 2:16 PM, Gavin McDonald wrote:

Hi All,

As the current Buildbots arent really working, nodes offline etc, I thought
this would be the best time to migrate your builds over to our newer
replacement
buildbot 3.2 over at ci2.apache.org .

I'll do my best to get them all running as passing as best they can, and
will update this thread with any questions or messages.

My first query is seeing as we have no more i386 or FreeBSD agents/nodes,
I'll probably just go ahead and remove those from the new config file.

HTH

I just realized I had somehow missed your original email about migrating 
andwas discussing getting with you.


Thanks for working on this.

Let us know if you have any questions.

Best regards,
Carl

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

Buildbots

[Gavin McDonald]

Hi All,

As the current Buildbots arent really working, nodes offline etc, I thought
this would be the best time to migrate your builds over to our newer
replacement
buildbot 3.2 over at ci2.apache.org .

I'll do my best to get them all running as passing as best they can, and
will update this thread with any questions or messages.

My first query is seeing as we have no more i386 or FreeBSD agents/nodes,
I'll probably just go ahead and remove those from the new config file.

HTH

-- 

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team

Re: Windows Buildbots

[Matthias Seidel]

Hi Arrigo,

Am 21.03.21 um 15:13 schrieb Arrigo Marchiori:
> Hello Matthias, all,
>
> replying to a somewhat old thread:
>
> On Sat, Mar 06, 2021 at 12:15:55AM +0100, Matthias Seidel wrote:
>
> [...]
>> P.S.: Did I mention, that we need someone to maintain the buildbots? ;-)
> What kind of maintenance do they require?
Every kind! ;-)
>
> And also: do we have any documentation about how those buildbots were
> installed and configured?

The only thing I know of is our configuration file:

https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/openofficeorg.conf

I kept the Windows buildbots running somehow...

> The Windows building guide leaves some choices to the reader, and it
> may be useful to know which ones were followed for them.

I kept them as close to a release build as possible.

Regards,

   Matthias

>
> Thank you in advance and best regards,



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Windows Buildbots

[Arrigo Marchiori]

Hello Matthias, all,

replying to a somewhat old thread:

On Sat, Mar 06, 2021 at 12:15:55AM +0100, Matthias Seidel wrote:

[...]
> P.S.: Did I mention, that we need someone to maintain the buildbots? ;-)

What kind of maintenance do they require?

And also: do we have any documentation about how those buildbots were
installed and configured?

The Windows building guide leaves some choices to the reader, and it
may be useful to know which ones were followed for them.

Thank you in advance and best regards,
-- 
Arrigo

http://rigo.altervista.org

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

Re: Windows Buildbots

[Matthias Seidel]

Hi Arrigo,

Am 05.03.21 um 23:06 schrieb Arrigo Marchiori:
> Hello Matthias,
>
> On Fri, Mar 05, 2021 at 04:58:59PM +0100, Matthias Seidel wrote:
>
>> Hi Arrigo,
>>
>> Am 05.03.21 um 16:54 schrieb Arrigo Marchiori:
>>> Hello Matthias, all,
>>>
>>> On Fri, Mar 05, 2021 at 04:11:44PM +0100, Matthias Seidel wrote:
>>>
>>>> Hi all,
>>>>
>>>> FYI, the Windows buildbots should be functional again.
>>>>
>>>> Thanks Chris (Infra)!
>>> Thank you as well, Matthias!
>>>
>>> It looks like that the latest build failed. Can we get any detailed
>>> output of the failing module's compilation?
>> If you think of:
>>
>> https://ci.apache.org/builders/openoffice-win7-41x/builds/132
>>
>> That is a buildbot issue, happens from time to time. 
> Yes, I meant that one.
>
>> Trunk did build OK.
> But apparently trunk failed as well...
> https://ci.apache.org/projects/openoffice/buildlogs/win/log/wntmsci12.pro.build.html

The build before that was successful (same revision).
Normally the next build should be OK again...

>
>>> From the buildbot's page I can only see the output of build.pl
>>> enumerating modules as it compiles them, but not the invocation of the
>>> compiler, warning messages etc.
>> Logs can be found here:
>>
>> https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info
> Aha, thank you!
>
> And... yuck,,, file mtime mismatch?!
> Do you ever see this problem when you build AOO yourself?

No. This happens sometimes when the buildbots were stuck.

Regards,

   Matthias

P.S.: Did I mention, that we need someone to maintain the buildbots? ;-)

>
> Best regards,



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Windows Buildbots

[Arrigo Marchiori]

Hello Matthias,

On Fri, Mar 05, 2021 at 04:58:59PM +0100, Matthias Seidel wrote:

> Hi Arrigo,
> 
> Am 05.03.21 um 16:54 schrieb Arrigo Marchiori:
> > Hello Matthias, all,
> >
> > On Fri, Mar 05, 2021 at 04:11:44PM +0100, Matthias Seidel wrote:
> >
> >> Hi all,
> >>
> >> FYI, the Windows buildbots should be functional again.
> >>
> >> Thanks Chris (Infra)!
> > Thank you as well, Matthias!
> >
> > It looks like that the latest build failed. Can we get any detailed
> > output of the failing module's compilation?
> 
> If you think of:
> 
> https://ci.apache.org/builders/openoffice-win7-41x/builds/132
> 
> That is a buildbot issue, happens from time to time. 

Yes, I meant that one.

> Trunk did build OK.

But apparently trunk failed as well...
https://ci.apache.org/projects/openoffice/buildlogs/win/log/wntmsci12.pro.build.html

> > From the buildbot's page I can only see the output of build.pl
> > enumerating modules as it compiles them, but not the invocation of the
> > compiler, warning messages etc.
> 
> Logs can be found here:
> 
> https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info

Aha, thank you!

And... yuck,,, file mtime mismatch?!
Do you ever see this problem when you build AOO yourself?

Best regards,
-- 
Arrigo

http://rigo.altervista.org

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

Re: Windows Buildbots

[Matthias Seidel]

Hi Arrigo,

Am 05.03.21 um 16:54 schrieb Arrigo Marchiori:
> Hello Matthias, all,
>
> On Fri, Mar 05, 2021 at 04:11:44PM +0100, Matthias Seidel wrote:
>
>> Hi all,
>>
>> FYI, the Windows buildbots should be functional again.
>>
>> Thanks Chris (Infra)!
> Thank you as well, Matthias!
>
> It looks like that the latest build failed. Can we get any detailed
> output of the failing module's compilation?

If you think of:

https://ci.apache.org/builders/openoffice-win7-41x/builds/132

That is a buildbot issue, happens from time to time. Trunk did build OK.

>
> From the buildbot's page I can only see the output of build.pl
> enumerating modules as it compiles them, but not the invocation of the
> compiler, warning messages etc.

Logs can be found here:

https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info

Regards,

   Matthias

>
> Thank you in advance and best regards,



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Windows Buildbots

[Arrigo Marchiori]

Hello Matthias, all,

On Fri, Mar 05, 2021 at 04:11:44PM +0100, Matthias Seidel wrote:

> Hi all,
> 
> FYI, the Windows buildbots should be functional again.
> 
> Thanks Chris (Infra)!

Thank you as well, Matthias!

It looks like that the latest build failed. Can we get any detailed
output of the failing module's compilation?

>From the buildbot's page I can only see the output of build.pl
enumerating modules as it compiles them, but not the invocation of the
compiler, warning messages etc.

Thank you in advance and best regards,
-- 
Arrigo

http://rigo.altervista.org

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

Re: Windows Buildbots

[Matthias Seidel]

Hi all,

FYI, the Windows buildbots should be functional again.

Thanks Chris (Infra)!

Regards,

   Matthias

Am 25.02.21 um 17:55 schrieb Matthias Seidel:
> Hi Pedro,
>
> Am 25.02.21 um 17:47 schrieb Pedro Lino:
>> Hi Matthias
>>
>>> On 02/25/2021 12:56 PM Matthias Seidel  wrote:
>>> The Windows Buildbots are offline for more than two weeks.
>>> Apparently nobody noticed it...
>> Personally I only use Windows builds from Sourceforge or from
>> https://home.apache.org/~mseidel/AOO-builds/
> I take the buildbot builds to see if a commit breaks something and to
> test certain issues.
> One should never "use" them for daily work.
>
> And I don't have the time for daily builds, so it comes down to a
> monthly period.
>
>> Unfortunately there doesn't seem to be any correlation between the number of 
>> downloads and the number of testers...
> It never has been... :-)
>
> Regards,
>
>    Matthias
>
>> Regards,
>> Pedro
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Windows Buildbots

[Matthias Seidel]

Hi Pedro,

Am 25.02.21 um 17:47 schrieb Pedro Lino:
> Hi Matthias
>
>> On 02/25/2021 12:56 PM Matthias Seidel  wrote:
>> The Windows Buildbots are offline for more than two weeks.
>> Apparently nobody noticed it...
> Personally I only use Windows builds from Sourceforge or from
> https://home.apache.org/~mseidel/AOO-builds/
I take the buildbot builds to see if a commit breaks something and to
test certain issues.
One should never "use" them for daily work.

And I don't have the time for daily builds, so it comes down to a
monthly period.

>
> Unfortunately there doesn't seem to be any correlation between the number of 
> downloads and the number of testers...

It never has been... :-)

Regards,

   Matthias

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



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Windows Buildbots

[Pedro Lino]

Hi Matthias

> On 02/25/2021 12:56 PM Matthias Seidel  wrote:

> The Windows Buildbots are offline for more than two weeks.
> Apparently nobody noticed it...

Personally I only use Windows builds from Sourceforge or from
https://home.apache.org/~mseidel/AOO-builds/

Unfortunately there doesn't seem to be any correlation between the number of 
downloads and the number of testers...

Regards,
Pedro

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

Windows Buildbots

[Matthias Seidel]

Hi all,

Just FYI:

The Windows Buildbots are offline for more than two weeks.
Apparently nobody noticed it...

I created a ticket for Infra:

https://issues.apache.org/jira/browse/INFRA-21462

Regards,

   Matthias




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Buildbots

[Marcus]

Am 09.11.19 um 09:28 schrieb Matthias Seidel:

Just FYI, the Windows bots are building again...

https://www.openoffice.org/download/devbuilds.html

We are now working on the Linux machines...


that's great news. Thanks for that. :-)

Marcus


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

Re: Buildbots

[Peter Kovacs]

Great!

Am 9. November 2019 09:28:40 MEZ schrieb Matthias Seidel 
:
>Hi all,
>
>Just FYI, the Windows bots are building again...
>
>https://www.openoffice.org/download/devbuilds.html
>
>We are now working on the Linux machines...
>
>Regards,
>
>   Matthias

Buildbots

[Matthias Seidel]

Hi all,

Just FYI, the Windows bots are building again...

https://www.openoffice.org/download/devbuilds.html

We are now working on the Linux machines...

Regards,

   Matthias




smime.p7s
Description: S/MIME Cryptographic Signature

Re: 32-bit buildbots

[Matthias Seidel]

Hi Jim,

Could you do me a favor and send a screenshot of the macOS version from
a full screen Writer window?

Regards,

   Matthias

Am 24.07.19 um 18:16 schrieb Jim Jagielski:
> Uploading to:
>
>   http://home.apache.org/~jim/AOO-builds/ 
> 
>
> as we speak... Cheers!



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 32-bit buildbots

[Matthias Seidel]

Thanks a lot!

Am 24.07.19 um 18:16 schrieb Jim Jagielski:
> Uploading to:
>
>   http://home.apache.org/~jim/AOO-builds/ 
> 
>
> as we speak... Cheers!



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 32-bit buildbots

[Jim Jagielski]

Uploading to:

  http://home.apache.org/~jim/AOO-builds/ 


as we speak... Cheers!

Re: 32-bit buildbots

[Matthias Seidel]

Am 23.07.19 um 20:01 schrieb Jim Jagielski:
> building the Linux build as we speak

Thanks!

>
>> On Jul 23, 2019, at 1:58 PM, Matthias Seidel  
>> wrote:
>>
>> Yes... ;-)
>>
>> This should be r1863580. en-US and de if possible.
>>
>> Thanks!
>>
>> Am 23.07.19 um 19:26 schrieb Jim Jagielski:
>>> You got it... I will be using my normal CentOS7 build server.
>>>
>>> I assume HEAD of the 
>>> http://svn.apache.org/viewvc/openoffice/branches/AOO42X/ branch.
>>>
>>>> On Jul 23, 2019, at 1:03 PM, Matthias Seidel  
>>>> wrote:
>>>>
>>>> Hi Jim,
>>>>
>>>> 4.2.0, please. 64 bit would be preferred. ;-)
>>>>
>>>> Meanwhile we are trying to get the buildbots working again:
>>>> https://issues.apache.org/jira/browse/INFRA-17822
>>>>
>>>> Regards,
>>>>
>>>>   Matthias
>>>>
>>>> Am 23.07.19 um 18:47 schrieb Jim Jagielski:
>>>>> You got it... for 4.1.7 or 4.2.0-dev?
>>>>>
>>>>>> On Jul 22, 2019, at 6:56 AM, Matthias Seidel 
>>>>>>  wrote:
>>>>>>
>>>>>> Hi Jim,
>>>>>>
>>>>>> If your time permits, can you provide new builds for Linux (and macOS)?
>>>>>>
>>>>>> I made some changes that l would like to check.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>>  Matthias
>>>>>>
>>>>>>
>>>>>> Am 01.07.19 um 17:47 schrieb Jim Jagielski:
>>>>>>> I can, and will, provide 32bit Linux builds on CentOS5, CentOS7 and 
>>>>>>> Ubuntu 14.04
>>>>>>>
>>>>>>>> On Jun 25, 2019, at 9:31 AM, Matthias Seidel 
>>>>>>>>  wrote:
>>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> Infra does not provide 32-bit slaves anymore, so we will not have new
>>>>>>>> builds for Linux32 here:
>>>>>>>>
>>>>>>>> https://www.openoffice.org/download/devbuilds.html
>>>>>>>>
>>>>>>>> I will update the page but leave the links to the most recent builds 
>>>>>>>> for
>>>>>>>> a while.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Matthias
>>>>>>>>
>>>>>>>>
>>>>>>> -
>>>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>>>>>
>>>>>>>
>>>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 32-bit buildbots

[Jim Jagielski]

building the Linux build as we speak

> On Jul 23, 2019, at 1:58 PM, Matthias Seidel  
> wrote:
> 
> Yes... ;-)
> 
> This should be r1863580. en-US and de if possible.
> 
> Thanks!
> 
> Am 23.07.19 um 19:26 schrieb Jim Jagielski:
>> You got it... I will be using my normal CentOS7 build server.
>> 
>> I assume HEAD of the 
>> http://svn.apache.org/viewvc/openoffice/branches/AOO42X/ branch.
>> 
>>> On Jul 23, 2019, at 1:03 PM, Matthias Seidel  
>>> wrote:
>>> 
>>> Hi Jim,
>>> 
>>> 4.2.0, please. 64 bit would be preferred. ;-)
>>> 
>>> Meanwhile we are trying to get the buildbots working again:
>>> https://issues.apache.org/jira/browse/INFRA-17822
>>> 
>>> Regards,
>>> 
>>>   Matthias
>>> 
>>> Am 23.07.19 um 18:47 schrieb Jim Jagielski:
>>>> You got it... for 4.1.7 or 4.2.0-dev?
>>>> 
>>>>> On Jul 22, 2019, at 6:56 AM, Matthias Seidel  
>>>>> wrote:
>>>>> 
>>>>> Hi Jim,
>>>>> 
>>>>> If your time permits, can you provide new builds for Linux (and macOS)?
>>>>> 
>>>>> I made some changes that l would like to check.
>>>>> 
>>>>> Regards,
>>>>> 
>>>>>  Matthias
>>>>> 
>>>>> 
>>>>> Am 01.07.19 um 17:47 schrieb Jim Jagielski:
>>>>>> I can, and will, provide 32bit Linux builds on CentOS5, CentOS7 and 
>>>>>> Ubuntu 14.04
>>>>>> 
>>>>>>> On Jun 25, 2019, at 9:31 AM, Matthias Seidel 
>>>>>>>  wrote:
>>>>>>> 
>>>>>>> Hi all,
>>>>>>> 
>>>>>>> Infra does not provide 32-bit slaves anymore, so we will not have new
>>>>>>> builds for Linux32 here:
>>>>>>> 
>>>>>>> https://www.openoffice.org/download/devbuilds.html
>>>>>>> 
>>>>>>> I will update the page but leave the links to the most recent builds for
>>>>>>> a while.
>>>>>>> 
>>>>>>> Regards,
>>>>>>> 
>>>>>>> Matthias
>>>>>>> 
>>>>>>> 
>>>>>> -
>>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>>>> 
>>>>>> 
>>>> -
>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
> 


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

Re: 32-bit buildbots

[Matthias Seidel]

Yes... ;-)

This should be r1863580. en-US and de if possible.

Thanks!

Am 23.07.19 um 19:26 schrieb Jim Jagielski:
> You got it... I will be using my normal CentOS7 build server.
>
> I assume HEAD of the http://svn.apache.org/viewvc/openoffice/branches/AOO42X/ 
> branch.
>
>> On Jul 23, 2019, at 1:03 PM, Matthias Seidel  
>> wrote:
>>
>> Hi Jim,
>>
>> 4.2.0, please. 64 bit would be preferred. ;-)
>>
>> Meanwhile we are trying to get the buildbots working again:
>> https://issues.apache.org/jira/browse/INFRA-17822
>>
>> Regards,
>>
>>Matthias
>>
>> Am 23.07.19 um 18:47 schrieb Jim Jagielski:
>>> You got it... for 4.1.7 or 4.2.0-dev?
>>>
>>>> On Jul 22, 2019, at 6:56 AM, Matthias Seidel  
>>>> wrote:
>>>>
>>>> Hi Jim,
>>>>
>>>> If your time permits, can you provide new builds for Linux (and macOS)?
>>>>
>>>> I made some changes that l would like to check.
>>>>
>>>> Regards,
>>>>
>>>>   Matthias
>>>>
>>>>
>>>> Am 01.07.19 um 17:47 schrieb Jim Jagielski:
>>>>> I can, and will, provide 32bit Linux builds on CentOS5, CentOS7 and 
>>>>> Ubuntu 14.04
>>>>>
>>>>>> On Jun 25, 2019, at 9:31 AM, Matthias Seidel 
>>>>>>  wrote:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Infra does not provide 32-bit slaves anymore, so we will not have new
>>>>>> builds for Linux32 here:
>>>>>>
>>>>>> https://www.openoffice.org/download/devbuilds.html
>>>>>>
>>>>>> I will update the page but leave the links to the most recent builds for
>>>>>> a while.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>>  Matthias
>>>>>>
>>>>>>
>>>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>>>
>>>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 32-bit buildbots

[Jim Jagielski]

You got it... I will be using my normal CentOS7 build server.

I assume HEAD of the http://svn.apache.org/viewvc/openoffice/branches/AOO42X/ 
branch.

> On Jul 23, 2019, at 1:03 PM, Matthias Seidel  
> wrote:
> 
> Hi Jim,
> 
> 4.2.0, please. 64 bit would be preferred. ;-)
> 
> Meanwhile we are trying to get the buildbots working again:
> https://issues.apache.org/jira/browse/INFRA-17822
> 
> Regards,
> 
>Matthias
> 
> Am 23.07.19 um 18:47 schrieb Jim Jagielski:
>> You got it... for 4.1.7 or 4.2.0-dev?
>> 
>>> On Jul 22, 2019, at 6:56 AM, Matthias Seidel  
>>> wrote:
>>> 
>>> Hi Jim,
>>> 
>>> If your time permits, can you provide new builds for Linux (and macOS)?
>>> 
>>> I made some changes that l would like to check.
>>> 
>>> Regards,
>>> 
>>>   Matthias
>>> 
>>> 
>>> Am 01.07.19 um 17:47 schrieb Jim Jagielski:
>>>> I can, and will, provide 32bit Linux builds on CentOS5, CentOS7 and Ubuntu 
>>>> 14.04
>>>> 
>>>>> On Jun 25, 2019, at 9:31 AM, Matthias Seidel  
>>>>> wrote:
>>>>> 
>>>>> Hi all,
>>>>> 
>>>>> Infra does not provide 32-bit slaves anymore, so we will not have new
>>>>> builds for Linux32 here:
>>>>> 
>>>>> https://www.openoffice.org/download/devbuilds.html
>>>>> 
>>>>> I will update the page but leave the links to the most recent builds for
>>>>> a while.
>>>>> 
>>>>> Regards,
>>>>> 
>>>>>  Matthias
>>>>> 
>>>>> 
>>>> -
>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>> 
>>>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
> 


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

Re: 32-bit buildbots

[Matthias Seidel]

Hi Jim,

4.2.0, please. 64 bit would be preferred. ;-)

Meanwhile we are trying to get the buildbots working again:
https://issues.apache.org/jira/browse/INFRA-17822

Regards,

   Matthias

Am 23.07.19 um 18:47 schrieb Jim Jagielski:
> You got it... for 4.1.7 or 4.2.0-dev?
>
>> On Jul 22, 2019, at 6:56 AM, Matthias Seidel  
>> wrote:
>>
>> Hi Jim,
>>
>> If your time permits, can you provide new builds for Linux (and macOS)?
>>
>> I made some changes that l would like to check.
>>
>> Regards,
>>
>>Matthias
>>
>>
>> Am 01.07.19 um 17:47 schrieb Jim Jagielski:
>>> I can, and will, provide 32bit Linux builds on CentOS5, CentOS7 and Ubuntu 
>>> 14.04
>>>
>>>> On Jun 25, 2019, at 9:31 AM, Matthias Seidel  
>>>> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> Infra does not provide 32-bit slaves anymore, so we will not have new
>>>> builds for Linux32 here:
>>>>
>>>> https://www.openoffice.org/download/devbuilds.html
>>>>
>>>> I will update the page but leave the links to the most recent builds for
>>>> a while.
>>>>
>>>> Regards,
>>>>
>>>>   Matthias
>>>>
>>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 32-bit buildbots

[Jim Jagielski]

You got it... for 4.1.7 or 4.2.0-dev?

> On Jul 22, 2019, at 6:56 AM, Matthias Seidel  
> wrote:
> 
> Hi Jim,
> 
> If your time permits, can you provide new builds for Linux (and macOS)?
> 
> I made some changes that l would like to check.
> 
> Regards,
> 
>Matthias
> 
> 
> Am 01.07.19 um 17:47 schrieb Jim Jagielski:
>> I can, and will, provide 32bit Linux builds on CentOS5, CentOS7 and Ubuntu 
>> 14.04
>> 
>>> On Jun 25, 2019, at 9:31 AM, Matthias Seidel  
>>> wrote:
>>> 
>>> Hi all,
>>> 
>>> Infra does not provide 32-bit slaves anymore, so we will not have new
>>> builds for Linux32 here:
>>> 
>>> https://www.openoffice.org/download/devbuilds.html
>>> 
>>> I will update the page but leave the links to the most recent builds for
>>> a while.
>>> 
>>> Regards,
>>> 
>>>   Matthias
>>> 
>>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
>> 
> 


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

Re: 32-bit buildbots

[Matthias Seidel]

Hi Jim,

If your time permits, can you provide new builds for Linux (and macOS)?

I made some changes that l would like to check.

Regards,

   Matthias


Am 01.07.19 um 17:47 schrieb Jim Jagielski:
> I can, and will, provide 32bit Linux builds on CentOS5, CentOS7 and Ubuntu 
> 14.04
>
>> On Jun 25, 2019, at 9:31 AM, Matthias Seidel  
>> wrote:
>>
>> Hi all,
>>
>> Infra does not provide 32-bit slaves anymore, so we will not have new
>> builds for Linux32 here:
>>
>> https://www.openoffice.org/download/devbuilds.html
>>
>> I will update the page but leave the links to the most recent builds for
>> a while.
>>
>> Regards,
>>
>>Matthias
>>
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 32-bit buildbots

[Matthias Seidel]

Hi Jim,

Am 01.07.19 um 17:47 schrieb Jim Jagielski:
> I can, and will, provide 32bit Linux builds on CentOS5, CentOS7 and Ubuntu 
> 14.04

That's great!

But you are not a bot... ;-)

Regards,

   Matthias

>
>> On Jun 25, 2019, at 9:31 AM, Matthias Seidel  
>> wrote:
>>
>> Hi all,
>>
>> Infra does not provide 32-bit slaves anymore, so we will not have new
>> builds for Linux32 here:
>>
>> https://www.openoffice.org/download/devbuilds.html
>>
>> I will update the page but leave the links to the most recent builds for
>> a while.
>>
>> Regards,
>>
>>Matthias
>>
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 32-bit buildbots

[Jim Jagielski]

I can, and will, provide 32bit Linux builds on CentOS5, CentOS7 and Ubuntu 14.04

> On Jun 25, 2019, at 9:31 AM, Matthias Seidel  
> wrote:
> 
> Hi all,
> 
> Infra does not provide 32-bit slaves anymore, so we will not have new
> builds for Linux32 here:
> 
> https://www.openoffice.org/download/devbuilds.html
> 
> I will update the page but leave the links to the most recent builds for
> a while.
> 
> Regards,
> 
>Matthias
> 
> 


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

Re: 32-bit buildbots

[Matthias Seidel]

Hi Peter,

Am 29.06.19 um 15:55 schrieb Peter Kovacs:
> Hmm, okay. I understood that build bot expects python 2.7 but got python 3.
> I think you mean build bot needs python 3 but runs with python 2.7, right? 
At least for the buildbot-master...
>
> Okay still I think infra needs to sort this.
> We could give them pointers. Shall I write another Comment? Or do you want to?

They should be aware of it because every buildbot on that machine has a
similar error:

https://ci.apache.org/buildslaves/bb_slave8_ubuntu

Regards,

   Matthias

>
> :) 
>
> Am 29. Juni 2019 13:17:10 MESZ schrieb Matthias Seidel 
> :
>> Am 29.06.19 um 13:11 schrieb Peter Kovacs:
>>> If it is a standard 18.04 Ubuntu
>> I think it is...
>>> |/usr/bin/python still points to 2.7 if version 3 should be use it
>> needs
>>> to run |
>>> |/usr/bin/python3 So I think thats not the problem. I updated the
>> ticket
>>> with the issue we experience and asked for an update. Lets see what
>>> happens. |||
>> See also: https://github.com/buildbot/buildbot/issues/4439
>>
>> Regards,
>>
>>    Matthias
>>
>>> On 29.06.19 11:06, Matthias Seidel wrote:
>>>> Hi Peter,
>>>>
>>>> This is the corresponding ticket:
>>>>
>>>>
>> https://issues.apache.org/jira/browse/INFRA-17822?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=16852361#comment-16852361
>>>> I think the main problem now is that bb-slave8 runs a newer version
>> of
>>>> buildbot and doesn't support Python 2.7 anymore:
>>>>
>>>>
>> https://ci.apache.org/builders/openoffice-linux64-nightly/builds/571/steps/delete%20old%20build/logs/err.text
>>>> Regards,
>>>>
>>>>    Matthias
>>>>
>>>> Am 29.06.19 um 10:58 schrieb Peter Kovacs:
>>>>> +1, since I am in full support of the build bots, I would like to
>>>>> support this, too.
>>>>>
>>>>> I do not have any rights I think. Will check as soon as I can
>> confirm
>>>>> that my connection works now on the Laptop.
>>>>>
>>>>> The more maintainers are available the better the situation is.
>>>>>
>>>>> On 29.06.19 10:39, Matthias Seidel wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> Am 27.06.19 um 12:16 schrieb Josef Latt:
>>>>>>> Hi,
>>>>>>>
>>>>>>> what's about the 64 bit builds?
>>>>>>> They are outdated > 1 month.
>>>>>> Josef has a point here.
>>>>>>
>>>>>> We should concentrate on getting the existing buildbots up before
>> we
>>>>>> dream about new VMs and macOS...
>>>>>>
>>>>>> Volunteers? ;-)
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>>    Matthias
>>>>>>
>>>>>>> Regards
>>>>>>> Josef
>>>>>>>
>>>>>>> Am 25.06.19 um 15:31 schrieb Matthias Seidel:
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> Infra does not provide 32-bit slaves anymore, so we will not
>> have new
>>>>>>>> builds for Linux32 here:
>>>>>>>>
>>>>>>>> https://www.openoffice.org/download/devbuilds.html
>>>>>>>>
>>>>>>>> I will update the page but leave the links to the most recent
>> builds for
>>>>>>>> a while.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>>    Matthias
>>>>>>>>
>>>>>>>>
>> -
>>>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>>>>>
>>>>>>>
>> -
>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>>>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 32-bit buildbots

[Peter Kovacs]

Hmm, okay. I understood that build bot expects python 2.7 but got python 3.
I think you mean build bot needs python 3 but runs with python 2.7, right? 

Okay still I think infra needs to sort this.
We could give them pointers. Shall I write another Comment? Or do you want to?

:) 

Am 29. Juni 2019 13:17:10 MESZ schrieb Matthias Seidel 
:
>Am 29.06.19 um 13:11 schrieb Peter Kovacs:
>> If it is a standard 18.04 Ubuntu
>I think it is...
>>
>> |/usr/bin/python still points to 2.7 if version 3 should be use it
>needs
>> to run |
>> |/usr/bin/python3 So I think thats not the problem. I updated the
>ticket
>> with the issue we experience and asked for an update. Lets see what
>> happens. |||
>
>See also: https://github.com/buildbot/buildbot/issues/4439
>
>Regards,
>
>   Matthias
>
>>
>> On 29.06.19 11:06, Matthias Seidel wrote:
>>> Hi Peter,
>>>
>>> This is the corresponding ticket:
>>>
>>>
>https://issues.apache.org/jira/browse/INFRA-17822?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=16852361#comment-16852361
>>>
>>> I think the main problem now is that bb-slave8 runs a newer version
>of
>>> buildbot and doesn't support Python 2.7 anymore:
>>>
>>>
>https://ci.apache.org/builders/openoffice-linux64-nightly/builds/571/steps/delete%20old%20build/logs/err.text
>>>
>>> Regards,
>>>
>>>    Matthias
>>>
>>> Am 29.06.19 um 10:58 schrieb Peter Kovacs:
>>>> +1, since I am in full support of the build bots, I would like to
>>>> support this, too.
>>>>
>>>> I do not have any rights I think. Will check as soon as I can
>confirm
>>>> that my connection works now on the Laptop.
>>>>
>>>> The more maintainers are available the better the situation is.
>>>>
>>>> On 29.06.19 10:39, Matthias Seidel wrote:
>>>>> Hi all,
>>>>>
>>>>> Am 27.06.19 um 12:16 schrieb Josef Latt:
>>>>>> Hi,
>>>>>>
>>>>>> what's about the 64 bit builds?
>>>>>> They are outdated > 1 month.
>>>>> Josef has a point here.
>>>>>
>>>>> We should concentrate on getting the existing buildbots up before
>we
>>>>> dream about new VMs and macOS...
>>>>>
>>>>> Volunteers? ;-)
>>>>>
>>>>> Regards,
>>>>>
>>>>>    Matthias
>>>>>
>>>>>> Regards
>>>>>> Josef
>>>>>>
>>>>>> Am 25.06.19 um 15:31 schrieb Matthias Seidel:
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Infra does not provide 32-bit slaves anymore, so we will not
>have new
>>>>>>> builds for Linux32 here:
>>>>>>>
>>>>>>> https://www.openoffice.org/download/devbuilds.html
>>>>>>>
>>>>>>> I will update the page but leave the links to the most recent
>builds for
>>>>>>> a while.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>>    Matthias
>>>>>>>
>>>>>>>
>>>>>>
>-
>>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>>>>
>>>>>>
>>>>
>-
>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>>

Re: 32-bit buildbots

[Matthias Seidel]

Am 29.06.19 um 13:11 schrieb Peter Kovacs:
> If it is a standard 18.04 Ubuntu
I think it is...
>
> |/usr/bin/python still points to 2.7 if version 3 should be use it needs
> to run |
> |/usr/bin/python3 So I think thats not the problem. I updated the ticket
> with the issue we experience and asked for an update. Lets see what
> happens. |||

See also: https://github.com/buildbot/buildbot/issues/4439

Regards,

   Matthias

>
> On 29.06.19 11:06, Matthias Seidel wrote:
>> Hi Peter,
>>
>> This is the corresponding ticket:
>>
>> https://issues.apache.org/jira/browse/INFRA-17822?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=16852361#comment-16852361
>>
>> I think the main problem now is that bb-slave8 runs a newer version of
>> buildbot and doesn't support Python 2.7 anymore:
>>
>> https://ci.apache.org/builders/openoffice-linux64-nightly/builds/571/steps/delete%20old%20build/logs/err.text
>>
>> Regards,
>>
>>    Matthias
>>
>> Am 29.06.19 um 10:58 schrieb Peter Kovacs:
>>> +1, since I am in full support of the build bots, I would like to
>>> support this, too.
>>>
>>> I do not have any rights I think. Will check as soon as I can confirm
>>> that my connection works now on the Laptop.
>>>
>>> The more maintainers are available the better the situation is.
>>>
>>> On 29.06.19 10:39, Matthias Seidel wrote:
>>>> Hi all,
>>>>
>>>> Am 27.06.19 um 12:16 schrieb Josef Latt:
>>>>> Hi,
>>>>>
>>>>> what's about the 64 bit builds?
>>>>> They are outdated > 1 month.
>>>> Josef has a point here.
>>>>
>>>> We should concentrate on getting the existing buildbots up before we
>>>> dream about new VMs and macOS...
>>>>
>>>> Volunteers? ;-)
>>>>
>>>> Regards,
>>>>
>>>>    Matthias
>>>>
>>>>> Regards
>>>>> Josef
>>>>>
>>>>> Am 25.06.19 um 15:31 schrieb Matthias Seidel:
>>>>>> Hi all,
>>>>>>
>>>>>> Infra does not provide 32-bit slaves anymore, so we will not have new
>>>>>> builds for Linux32 here:
>>>>>>
>>>>>> https://www.openoffice.org/download/devbuilds.html
>>>>>>
>>>>>> I will update the page but leave the links to the most recent builds for
>>>>>> a while.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>>    Matthias
>>>>>>
>>>>>>
>>>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>>>
>>>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 32-bit buildbots

[Peter Kovacs]

If it is a standard 18.04 Ubuntu

|/usr/bin/python still points to 2.7 if version 3 should be use it needs
to run |
|/usr/bin/python3 So I think thats not the problem. I updated the ticket
with the issue we experience and asked for an update. Lets see what
happens. |||

On 29.06.19 11:06, Matthias Seidel wrote:
> Hi Peter,
>
> This is the corresponding ticket:
>
> https://issues.apache.org/jira/browse/INFRA-17822?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=16852361#comment-16852361
>
> I think the main problem now is that bb-slave8 runs a newer version of
> buildbot and doesn't support Python 2.7 anymore:
>
> https://ci.apache.org/builders/openoffice-linux64-nightly/builds/571/steps/delete%20old%20build/logs/err.text
>
> Regards,
>
>    Matthias
>
> Am 29.06.19 um 10:58 schrieb Peter Kovacs:
>> +1, since I am in full support of the build bots, I would like to
>> support this, too.
>>
>> I do not have any rights I think. Will check as soon as I can confirm
>> that my connection works now on the Laptop.
>>
>> The more maintainers are available the better the situation is.
>>
>> On 29.06.19 10:39, Matthias Seidel wrote:
>>> Hi all,
>>>
>>> Am 27.06.19 um 12:16 schrieb Josef Latt:
>>>> Hi,
>>>>
>>>> what's about the 64 bit builds?
>>>> They are outdated > 1 month.
>>> Josef has a point here.
>>>
>>> We should concentrate on getting the existing buildbots up before we
>>> dream about new VMs and macOS...
>>>
>>> Volunteers? ;-)
>>>
>>> Regards,
>>>
>>>    Matthias
>>>
>>>> Regards
>>>> Josef
>>>>
>>>> Am 25.06.19 um 15:31 schrieb Matthias Seidel:
>>>>> Hi all,
>>>>>
>>>>> Infra does not provide 32-bit slaves anymore, so we will not have new
>>>>> builds for Linux32 here:
>>>>>
>>>>> https://www.openoffice.org/download/devbuilds.html
>>>>>
>>>>> I will update the page but leave the links to the most recent builds for
>>>>> a while.
>>>>>
>>>>> Regards,
>>>>>
>>>>>    Matthias
>>>>>
>>>>>
>>>> -
>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>>
>>>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>

Re: 32-bit buildbots

[Matthias Seidel]

Hi Peter,

This is the corresponding ticket:

https://issues.apache.org/jira/browse/INFRA-17822?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=16852361#comment-16852361

I think the main problem now is that bb-slave8 runs a newer version of
buildbot and doesn't support Python 2.7 anymore:

https://ci.apache.org/builders/openoffice-linux64-nightly/builds/571/steps/delete%20old%20build/logs/err.text

Regards,

   Matthias

Am 29.06.19 um 10:58 schrieb Peter Kovacs:
> +1, since I am in full support of the build bots, I would like to
> support this, too.
>
> I do not have any rights I think. Will check as soon as I can confirm
> that my connection works now on the Laptop.
>
> The more maintainers are available the better the situation is.
>
> On 29.06.19 10:39, Matthias Seidel wrote:
>> Hi all,
>>
>> Am 27.06.19 um 12:16 schrieb Josef Latt:
>>> Hi,
>>>
>>> what's about the 64 bit builds?
>>> They are outdated > 1 month.
>> Josef has a point here.
>>
>> We should concentrate on getting the existing buildbots up before we
>> dream about new VMs and macOS...
>>
>> Volunteers? ;-)
>>
>> Regards,
>>
>>    Matthias
>>
>>> Regards
>>> Josef
>>>
>>> Am 25.06.19 um 15:31 schrieb Matthias Seidel:
>>>> Hi all,
>>>>
>>>> Infra does not provide 32-bit slaves anymore, so we will not have new
>>>> builds for Linux32 here:
>>>>
>>>> https://www.openoffice.org/download/devbuilds.html
>>>>
>>>> I will update the page but leave the links to the most recent builds for
>>>> a while.
>>>>
>>>> Regards,
>>>>
>>>>    Matthias
>>>>
>>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
>>>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 32-bit buildbots

[Peter Kovacs]

+1, since I am in full support of the build bots, I would like to
support this, too.

I do not have any rights I think. Will check as soon as I can confirm
that my connection works now on the Laptop.

The more maintainers are available the better the situation is.

On 29.06.19 10:39, Matthias Seidel wrote:
> Hi all,
>
> Am 27.06.19 um 12:16 schrieb Josef Latt:
>> Hi,
>>
>> what's about the 64 bit builds?
>> They are outdated > 1 month.
> Josef has a point here.
>
> We should concentrate on getting the existing buildbots up before we
> dream about new VMs and macOS...
>
> Volunteers? ;-)
>
> Regards,
>
>    Matthias
>
>> Regards
>> Josef
>>
>> Am 25.06.19 um 15:31 schrieb Matthias Seidel:
>>> Hi all,
>>>
>>> Infra does not provide 32-bit slaves anymore, so we will not have new
>>> builds for Linux32 here:
>>>
>>> https://www.openoffice.org/download/devbuilds.html
>>>
>>> I will update the page but leave the links to the most recent builds for
>>> a while.
>>>
>>> Regards,
>>>
>>>    Matthias
>>>
>>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>

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

Re: 32-bit buildbots

[Matthias Seidel]

Hi all,

Am 27.06.19 um 12:16 schrieb Josef Latt:
> Hi,
>
> what's about the 64 bit builds?
> They are outdated > 1 month.

Josef has a point here.

We should concentrate on getting the existing buildbots up before we
dream about new VMs and macOS...

Volunteers? ;-)

Regards,

   Matthias

>
> Regards
> Josef
>
> Am 25.06.19 um 15:31 schrieb Matthias Seidel:
>> Hi all,
>>
>> Infra does not provide 32-bit slaves anymore, so we will not have new
>> builds for Linux32 here:
>>
>> https://www.openoffice.org/download/devbuilds.html
>>
>> I will update the page but leave the links to the most recent builds for
>> a while.
>>
>> Regards,
>>
>>    Matthias
>>
>>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 32-bit buildbots

[Matthias Seidel]

Am 27.06.19 um 12:16 schrieb Josef Latt:
> Hi,
>
> what's about the 64 bit builds?
> They are outdated > 1 month.

Oh, at least someone recognized it. ;-)

Buildslaves are being moved and updated by Infra. This is a work in
progress...

But I would be happy if people would *really* test those builds when
available.
Apparently that didn't happen over the last years...

Regards,

   Matthias

>
> Regards
> Josef
>
> Am 25.06.19 um 15:31 schrieb Matthias Seidel:
>> Hi all,
>>
>> Infra does not provide 32-bit slaves anymore, so we will not have new
>> builds for Linux32 here:
>>
>> https://www.openoffice.org/download/devbuilds.html
>>
>> I will update the page but leave the links to the most recent builds for
>> a while.
>>
>> Regards,
>>
>>    Matthias
>>
>>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 32-bit buildbots

[Josef Latt]

Hi,

what's about the 64 bit builds?
They are outdated > 1 month.

Regards
Josef

Am 25.06.19 um 15:31 schrieb Matthias Seidel:
> Hi all,
>
> Infra does not provide 32-bit slaves anymore, so we will not have new
> builds for Linux32 here:
>
> https://www.openoffice.org/download/devbuilds.html
>
> I will update the page but leave the links to the most recent builds for
> a while.
>
> Regards,
>
>    Matthias
>
>

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

Re: 32-bit buildbots

[Peter]

Do we have a capable VM? I think our vms are all 64 bit. So we would need to 
recycle one VM to be capable on doing this.

I tried to check if the azure pipeline service can fill the gap. It is a build 
service like Jenkins I think. 
However my internet connection is to slow at the moment ( I am on vacation, and 
I thought the mogile 4g link would be quicker :() for their web side. 

BTW. Azure offers a pipeline for macs. 
I started to experiment if we could use the service for building Mac versions. 

The service is free for open source projects.
So yea volunteers are always welcome. :D


Am 26. Juni 2019 17:26:23 MESZ schrieb Matthias Seidel 
:
>Hi Mechtilde,
>
>Am 26.06.19 um 06:03 schrieb Mechtilde:
>> Hello Matthias,
>>
>> IMO as long as we provide 32bit Linux build we also run it a a
>buildbot.
>As Gavin said, if we provide a VM (CentOS?) with buildbot-worker
>running
>he can connect it.
>>
>> So we can see whether the build breaks and so on.
>
>D'accord! But that needs volunteers.
>
>Someone?! ;-)
>
>Regards,
>
>   Matthias
>
>>
>> Regards
>>
>> Mechtilde
>>
>> Am 25.06.19 um 19:34 schrieb Matthias Seidel:
>>> Hi Mechtilde,
>>>
>>> Am 25.06.19 um 19:06 schrieb Mechtilde:
>>>> Hello
>>>>
>>>> Am 25.06.19 um 16:00 schrieb Matthias Seidel:
>>>>> Hi Gavin,
>>>>>
>>>>> Am 25.06.19 um 15:42 schrieb Gavin McDonald:
>>>>>> Thanks Matthias, you beat me to it!
>>>>>>
>>>>>> If openoffice were to have someone with a 32 bit VM running a
>>>>>> buildbot-worker, we would of course connect it
>>>>>> to our master, and your builds would continue to be provided.
>>>> we should provide 32 bit builds for Linux. I know several people
>using
>>>> EEEPC and such older Laptops which are 32 bit.
>>> And those people don't use official releases but builds from
>buildbots?
>>>
>>> For 32-bit builds in general, see my comment below...
>>>
>>> Regards,
>>>
>>>    Matthias
>>>
>>>> Kind regards
>>>>
>>>> Mechtilde
>>>>> Maybe Jim could set one up?
>>>>>
>>>>> But I am not sure if we really need a buildbot for 32-bit or
>better
>>>>> provide test builds from time to time...
>>>>>
>>>>>> Have you any idea how many 32 bit openoffice users are left?
>>>>> Not really, but we plan to provide 32-bit builds at least for the
>next
>>>>> minor release (4.2.x)
>>>>>
>>>>> Regards,
>>>>>
>>>>>    Matthias
>>>>>
>>>>>
>>>>> P.S.: What is bb_slave8_ubuntu running? 18.04?
>>>>>
>>>>>> Gav...
>>>>>>
>>>>>>
>>>>>> On Tue, Jun 25, 2019 at 3:31 PM Matthias Seidel
>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Infra does not provide 32-bit slaves anymore, so we will not
>have new
>>>>>>> builds for Linux32 here:
>>>>>>>
>>>>>>> https://www.openoffice.org/download/devbuilds.html
>>>>>>>
>>>>>>> I will update the page but leave the links to the most recent
>builds for
>>>>>>> a while.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>>Matthias
>>>>>>>
>>>>>>>
>>>>>>>

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Re: 32-bit buildbots

[Matthias Seidel]

Hi Mechtilde,

Am 26.06.19 um 06:03 schrieb Mechtilde:
> Hello Matthias,
>
> IMO as long as we provide 32bit Linux build we also run it a a buildbot.
As Gavin said, if we provide a VM (CentOS?) with buildbot-worker running
he can connect it.
>
> So we can see whether the build breaks and so on.

D'accord! But that needs volunteers.

Someone?! ;-)

Regards,

   Matthias

>
> Regards
>
> Mechtilde
>
> Am 25.06.19 um 19:34 schrieb Matthias Seidel:
>> Hi Mechtilde,
>>
>> Am 25.06.19 um 19:06 schrieb Mechtilde:
>>> Hello
>>>
>>> Am 25.06.19 um 16:00 schrieb Matthias Seidel:
>>>> Hi Gavin,
>>>>
>>>> Am 25.06.19 um 15:42 schrieb Gavin McDonald:
>>>>> Thanks Matthias, you beat me to it!
>>>>>
>>>>> If openoffice were to have someone with a 32 bit VM running a
>>>>> buildbot-worker, we would of course connect it
>>>>> to our master, and your builds would continue to be provided.
>>> we should provide 32 bit builds for Linux. I know several people using
>>> EEEPC and such older Laptops which are 32 bit.
>> And those people don't use official releases but builds from buildbots?
>>
>> For 32-bit builds in general, see my comment below...
>>
>> Regards,
>>
>>    Matthias
>>
>>> Kind regards
>>>
>>> Mechtilde
>>>> Maybe Jim could set one up?
>>>>
>>>> But I am not sure if we really need a buildbot for 32-bit or better
>>>> provide test builds from time to time...
>>>>
>>>>> Have you any idea how many 32 bit openoffice users are left?
>>>> Not really, but we plan to provide 32-bit builds at least for the next
>>>> minor release (4.2.x)
>>>>
>>>> Regards,
>>>>
>>>>    Matthias
>>>>
>>>>
>>>> P.S.: What is bb_slave8_ubuntu running? 18.04?
>>>>
>>>>> Gav...
>>>>>
>>>>>
>>>>> On Tue, Jun 25, 2019 at 3:31 PM Matthias Seidel 
>>>>> 
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Infra does not provide 32-bit slaves anymore, so we will not have new
>>>>>> builds for Linux32 here:
>>>>>>
>>>>>> https://www.openoffice.org/download/devbuilds.html
>>>>>>
>>>>>> I will update the page but leave the links to the most recent builds for
>>>>>> a while.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>>Matthias
>>>>>>
>>>>>>
>>>>>>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 32-bit buildbots

[Mechtilde]

Hello Matthias,

IMO as long as we provide 32bit Linux build we also run it a a buildbot.

So we can see whether the build breaks and so on.

Regards

Mechtilde

Am 25.06.19 um 19:34 schrieb Matthias Seidel:
> Hi Mechtilde,
> 
> Am 25.06.19 um 19:06 schrieb Mechtilde:
>> Hello
>>
>> Am 25.06.19 um 16:00 schrieb Matthias Seidel:
>>> Hi Gavin,
>>>
>>> Am 25.06.19 um 15:42 schrieb Gavin McDonald:
>>>> Thanks Matthias, you beat me to it!
>>>>
>>>> If openoffice were to have someone with a 32 bit VM running a
>>>> buildbot-worker, we would of course connect it
>>>> to our master, and your builds would continue to be provided.
>> we should provide 32 bit builds for Linux. I know several people using
>> EEEPC and such older Laptops which are 32 bit.
> 
> And those people don't use official releases but builds from buildbots?
> 
> For 32-bit builds in general, see my comment below...
> 
> Regards,
> 
>    Matthias
> 
>>
>> Kind regards
>>
>> Mechtilde
>>> Maybe Jim could set one up?
>>>
>>> But I am not sure if we really need a buildbot for 32-bit or better
>>> provide test builds from time to time...
>>>
>>>> Have you any idea how many 32 bit openoffice users are left?
>>> Not really, but we plan to provide 32-bit builds at least for the next
>>> minor release (4.2.x)
>>>
>>> Regards,
>>>
>>>    Matthias
>>>
>>>
>>> P.S.: What is bb_slave8_ubuntu running? 18.04?
>>>
>>>> Gav...
>>>>
>>>>
>>>> On Tue, Jun 25, 2019 at 3:31 PM Matthias Seidel 
>>>> 
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> Infra does not provide 32-bit slaves anymore, so we will not have new
>>>>> builds for Linux32 here:
>>>>>
>>>>> https://www.openoffice.org/download/devbuilds.html
>>>>>
>>>>> I will update the page but leave the links to the most recent builds for
>>>>> a while.
>>>>>
>>>>> Regards,
>>>>>
>>>>>Matthias
>>>>>
>>>>>
>>>>>
> 

-- 
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F



signature.asc
Description: OpenPGP digital signature

Re: 32-bit buildbots

[Matthias Seidel]

Hi Mechtilde,

Am 25.06.19 um 19:06 schrieb Mechtilde:
> Hello
>
> Am 25.06.19 um 16:00 schrieb Matthias Seidel:
>> Hi Gavin,
>>
>> Am 25.06.19 um 15:42 schrieb Gavin McDonald:
>>> Thanks Matthias, you beat me to it!
>>>
>>> If openoffice were to have someone with a 32 bit VM running a
>>> buildbot-worker, we would of course connect it
>>> to our master, and your builds would continue to be provided.
> we should provide 32 bit builds for Linux. I know several people using
> EEEPC and such older Laptops which are 32 bit.

And those people don't use official releases but builds from buildbots?

For 32-bit builds in general, see my comment below...

Regards,

   Matthias

>
> Kind regards
>
> Mechtilde
>> Maybe Jim could set one up?
>>
>> But I am not sure if we really need a buildbot for 32-bit or better
>> provide test builds from time to time...
>>
>>> Have you any idea how many 32 bit openoffice users are left?
>> Not really, but we plan to provide 32-bit builds at least for the next
>> minor release (4.2.x)
>>
>> Regards,
>>
>>    Matthias
>>
>>
>> P.S.: What is bb_slave8_ubuntu running? 18.04?
>>
>>> Gav...
>>>
>>>
>>> On Tue, Jun 25, 2019 at 3:31 PM Matthias Seidel 
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> Infra does not provide 32-bit slaves anymore, so we will not have new
>>>> builds for Linux32 here:
>>>>
>>>> https://www.openoffice.org/download/devbuilds.html
>>>>
>>>> I will update the page but leave the links to the most recent builds for
>>>> a while.
>>>>
>>>> Regards,
>>>>
>>>>Matthias
>>>>
>>>>
>>>>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 32-bit buildbots

[Mechtilde]

Hello

Am 25.06.19 um 16:00 schrieb Matthias Seidel:
> Hi Gavin,
> 
> Am 25.06.19 um 15:42 schrieb Gavin McDonald:
>> Thanks Matthias, you beat me to it!
>>
>> If openoffice were to have someone with a 32 bit VM running a
>> buildbot-worker, we would of course connect it
>> to our master, and your builds would continue to be provided.

we should provide 32 bit builds for Linux. I know several people using
EEEPC and such older Laptops which are 32 bit.

Kind regards

Mechtilde
> 
> Maybe Jim could set one up?
> 
> But I am not sure if we really need a buildbot for 32-bit or better
> provide test builds from time to time...
> 
>>
>> Have you any idea how many 32 bit openoffice users are left?
> 
> Not really, but we plan to provide 32-bit builds at least for the next
> minor release (4.2.x)
> 
> Regards,
> 
>    Matthias
> 
> 
> P.S.: What is bb_slave8_ubuntu running? 18.04?
> 
>>
>> Gav...
>>
>>
>> On Tue, Jun 25, 2019 at 3:31 PM Matthias Seidel 
>> wrote:
>>
>>> Hi all,
>>>
>>> Infra does not provide 32-bit slaves anymore, so we will not have new
>>> builds for Linux32 here:
>>>
>>> https://www.openoffice.org/download/devbuilds.html
>>>
>>> I will update the page but leave the links to the most recent builds for
>>> a while.
>>>
>>> Regards,
>>>
>>>Matthias
>>>
>>>
>>>
> 

-- 
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F



signature.asc
Description: OpenPGP digital signature

Re: 32-bit buildbots

[Gavin McDonald]

On Tue, Jun 25, 2019 at 4:00 PM Matthias Seidel 
wrote:

> Hi Gavin,
>
> P.S.: What is bb_slave8_ubuntu running? 18.04?
>

Is is yep!

Gav...


>
> >
> > Gav...
> >
> >
> > On Tue, Jun 25, 2019 at 3:31 PM Matthias Seidel <
> matthias.sei...@hamburg.de>
> > wrote:
> >
> >> Hi all,
> >>
> >> Infra does not provide 32-bit slaves anymore, so we will not have new
> >> builds for Linux32 here:
> >>
> >> https://www.openoffice.org/download/devbuilds.html
> >>
> >> I will update the page but leave the links to the most recent builds for
> >> a while.
> >>
> >> Regards,
> >>
> >>Matthias
> >>
> >>
> >>
>
>

-- 
Gav...

Re: 32-bit buildbots

[Matthias Seidel]

Hi Gavin,

Am 25.06.19 um 15:42 schrieb Gavin McDonald:
> Thanks Matthias, you beat me to it!
>
> If openoffice were to have someone with a 32 bit VM running a
> buildbot-worker, we would of course connect it
> to our master, and your builds would continue to be provided.

Maybe Jim could set one up?

But I am not sure if we really need a buildbot for 32-bit or better
provide test builds from time to time...

>
> Have you any idea how many 32 bit openoffice users are left?

Not really, but we plan to provide 32-bit builds at least for the next
minor release (4.2.x)

Regards,

   Matthias


P.S.: What is bb_slave8_ubuntu running? 18.04?

>
> Gav...
>
>
> On Tue, Jun 25, 2019 at 3:31 PM Matthias Seidel 
> wrote:
>
>> Hi all,
>>
>> Infra does not provide 32-bit slaves anymore, so we will not have new
>> builds for Linux32 here:
>>
>> https://www.openoffice.org/download/devbuilds.html
>>
>> I will update the page but leave the links to the most recent builds for
>> a while.
>>
>> Regards,
>>
>>Matthias
>>
>>
>>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 32-bit buildbots

[Gavin McDonald]

Thanks Matthias, you beat me to it!

If openoffice were to have someone with a 32 bit VM running a
buildbot-worker, we would of course connect it
to our master, and your builds would continue to be provided.

Have you any idea how many 32 bit openoffice users are left?

Gav...


On Tue, Jun 25, 2019 at 3:31 PM Matthias Seidel 
wrote:

> Hi all,
>
> Infra does not provide 32-bit slaves anymore, so we will not have new
> builds for Linux32 here:
>
> https://www.openoffice.org/download/devbuilds.html
>
> I will update the page but leave the links to the most recent builds for
> a while.
>
> Regards,
>
>Matthias
>
>
>

-- 
Gav...

32-bit buildbots

[Matthias Seidel]

Hi all,

Infra does not provide 32-bit slaves anymore, so we will not have new
builds for Linux32 here:

https://www.openoffice.org/download/devbuilds.html

I will update the page but leave the links to the most recent builds for
a while.

Regards,

   Matthias




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Linux32 buildbots time out (fixed)

[Damjan Jovanovic]

That's great news :)

On Tue, Sep 12, 2017 at 10:54 PM, Matthias Seidel <
matthias.sei...@hamburg.de> wrote:

> The problem is fixed!
> RPMbuild had issues and therefore the bots timed out...
>
> We now have a full set of new Linux32 builds uploaded:
>
> https://www.openoffice.org/download/devbuilds.html
>
> Regards, Matthias
>
>
> Am 09.09.2017 um 13:40 schrieb Matthias Seidel:
> > Hello all,
> >
> > Our buildbots for Linux32 time out since mid August.
> >
> > I already opened a ticket with Infra, but we do not seem to find the
> > real cause:
> > https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-14954
> > (The issue with Java 8 is fixed and all other bots are working fine)
> >
> > Maybe someone more knowledgeable than me can have a look at the logs?
> >
> > Kind regards, Matthias
> >
> >
>
>
>

Re: Linux32 buildbots time out (fixed)

[Matthias Seidel]

The problem is fixed!
RPMbuild had issues and therefore the bots timed out...

We now have a full set of new Linux32 builds uploaded:

https://www.openoffice.org/download/devbuilds.html

Regards, Matthias


Am 09.09.2017 um 13:40 schrieb Matthias Seidel:
> Hello all,
>
> Our buildbots for Linux32 time out since mid August.
>
> I already opened a ticket with Infra, but we do not seem to find the
> real cause:
> https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-14954
> (The issue with Java 8 is fixed and all other bots are working fine)
>
> Maybe someone more knowledgeable than me can have a look at the logs?
>
> Kind regards, Matthias
>
>




smime.p7s
Description: S/MIME Cryptographic Signature

Linux32 buildbots time out

[Matthias Seidel]

Hello all,

Our buildbots for Linux32 time out since mid August.

I already opened a ticket with Infra, but we do not seem to find the
real cause:
https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-14954
(The issue with Java 8 is fixed and all other bots are working fine)

Maybe someone more knowledgeable than me can have a look at the logs?

Kind regards, Matthias




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Windows Buildbots

[Matthias Seidel]

Am 18.08.2017 um 21:13 schrieb Marcus:
> Am 18.08.2017 um 17:46 schrieb Matthias Seidel:
>> As of today, we have working Windows Buildbots for the 4.1.4 branch as
>> well as for trunk (aka 4.2.0).
>>
>> Thanks to Gavin who brought them back to life and Don for his latest
>> patches in trunk! ;-)
>
> thats great. Thanks to all for your steady efforts. This will bring us
> forward for new releases.

I also changed the configuration to be as close as possible to what we
use in releases (for Windows).

Unfortunately now the Linux32 bots are stuck... :-(

Matthias

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




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Windows Buildbots

[Jim Jagielski]

W00t! I just wish I could get my Windows build system working! :)

> On Aug 18, 2017, at 11:46 AM, Matthias Seidel <matthias.sei...@hamburg.de> 
> wrote:
> 
> As of today, we have working Windows Buildbots for the 4.1.4 branch as
> well as for trunk (aka 4.2.0).
> 
> Thanks to Gavin who brought them back to life and Don for his latest
> patches in trunk! ;-)
> 
> Kind regards, Matthias
> 


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

Re: Windows Buildbots

[Marcus]

Am 18.08.2017 um 17:46 schrieb Matthias Seidel:

As of today, we have working Windows Buildbots for the 4.1.4 branch as
well as for trunk (aka 4.2.0).

Thanks to Gavin who brought them back to life and Don for his latest
patches in trunk! ;-)


thats great. Thanks to all for your steady efforts. This will bring us 
forward for new releases.


Marcus


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

Windows Buildbots

[Matthias Seidel]

As of today, we have working Windows Buildbots for the 4.1.4 branch as
well as for trunk (aka 4.2.0).

Thanks to Gavin who brought them back to life and Don for his latest
patches in trunk! ;-)

Kind regards, Matthias



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Buildbots page

[Andrea Pescetti]

Jim Jagielski wrote:

How can I upload my macOS build there??


I've answered you here:

https://lists.apache.org/thread.html/05d175d207b2bdc1ed83c8c4884630e91663a953daf12fe8612e98c5@%3Cdev.openoffice.apache.org%3E

and here:

https://lists.apache.org/thread.html/96b7085351f7ab7975ac56c5bc7c42852b8a888da53e0a67864d3396@%3Cdev.openoffice.apache.org%3E

See also

https://lists.apache.org/thread.html/fb2aa00aac961e6f04cb987721f820502ec68675f57f1ca6671b27cf@%3Cdev.openoffice.apache.org%3E

for the current Linux-64 builds.

Regards,
  Andrea.

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

Re: Buildbots page

[Matthias Seidel]

Hi Jim,

This page links only to the output area of our buildbots.
I doubt that we can upload there...

As Andrea stated in another mail:

"So we've traditionally hosted the normal dev builds (before RC) on
people.apache.org; but Infra decided to replace it with  home.apache.org
and to make it SFTP-only (no rsync); still, it is possible, while still
painful, to upload an OpenOffice development snapshot there; see
https://home.apache.org/~pescetti/openoffice-4.1.3-dev-r1761989/binaries/
as an example."

So home.apache.org would be the place to upload your mac builds.

Kind regards, Matthias


Am 03.04.2017 um 16:07 schrieb Jim Jagielski:
> How can I upload my macOS build there??
>
>> On Apr 1, 2017, at 4:52 PM, Matthias Seidel <matthias.sei...@hamburg.de> 
>> wrote:
>>
>> If no one has objections I would make :
>>
>> https://www.openoffice.org/download/devbuilds-test.html
>>
>> live tomorrow and ask Infra to remove the script, page and artefacts of:
>>
>> https://ci.apache.org/projects/openoffice/index.html
>>
>> Regards, Matthias
>>
>> FYI: I changed the schedule of the snapshot builds (414 branch) to a
>> weekly base.
>>
>>
>> Am 28.03.2017 um 21:15 schrieb Matthias Seidel:
>>> Am 28.03.2017 um 01:55 schrieb Damjan Jovanovic:
>>>> It might have changed...
>>> Indeed (from:
>>> https://svn.apache.org/repos//infra/infrastructure/buildbot/aegis/buildmaster/master1/public_html/README_SCRIPTS.txt):
>>>
>>> Index generation scripts
>>> 
>>>
>>> Note:
>>> The shell scripts which generate the nightly and snapshot indexes have been 
>>> moved to puppet.
>>>
>>> See the directory:
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;a=tree;f=modules/buildbot_asf/files/projects;hb=HEAD
>>>
>>> The cron jobs are defined in
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;a=blob_plain;f=modules/buildbot_asf/manifests/init.pp;hb=HEAD
>>>
>>>
>>> Unfortunately only the script has been moved, but not the header, footer
>>> and css. Therefore the page can not be updated properly.
>>> The script itself generates links to AOO 4.1.2 snapshots and needs also
>>> to be changed.
>>>
>>> Instead of trying to fix the generated page I would suggest to link
>>> directly to nightlys/snapshots from our devbuilds homepage:
>>> https://www.openoffice.org/download/devbuilds.html
>>>
>>> I created a test page as example:
>>> https://www.openoffice.org/download/devbuilds-test.html
>>>
>>> Opinions?
>>>
>>> Kind regards, Matthias
>>>
>>>> On Mon, Mar 27, 2017 at 10:33 PM, Matthias Seidel <
>>>> matthias.sei...@hamburg.de> wrote:
>>>>
>>>>> Hi Damjan,
>>>>>
>>>>> Thanks you for the link, but in:
>>>>>
>>>>> https://svn.apache.org/repos/infra/infrastructure/buildbot/
>>>>> aegis/buildmaster/master1/public_html/projects/openoffice/
>>>>>
>>>>> I can only find header, footer and CSS but no script?
>>>>>
>>>>> Regards, Matthias
>>>>>
>>>>>
>>>>> Am 27.03.2017 um 18:25 schrieb Damjan Jovanovic:
>>>>>> It's generated from:
>>>>>> https://svn.apache.org/repos/infra/infrastructure/buildbot/
>>>>> aegis/buildmaster/master1/public_html/projects/openoffice/create-ooo-
>>>>> snapshots-index.sh
>>>>>> Regards
>>>>>> Damjan
>>>>>>
>>>>>> On Mon, Mar 27, 2017 at 5:58 PM, Matthias Seidel <
>>>>> matthias.sei...@hamburg.de
>>>>>>> wrote:
>>>>>>> Hello all!
>>>>>>>
>>>>>>> Is there a way to maintain our Buildbots page?
>>>>>>>
>>>>>>> https://ci.apache.org/projects/openoffice/index.html
>>>>>>>
>>>>>>> Regards, Matthias
>>>>>>>
>>>>>>>
>>>>>>>
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Buildbots page

[Jim Jagielski]

How can I upload my macOS build there??

> On Apr 1, 2017, at 4:52 PM, Matthias Seidel <matthias.sei...@hamburg.de> 
> wrote:
> 
> If no one has objections I would make :
> 
> https://www.openoffice.org/download/devbuilds-test.html
> 
> live tomorrow and ask Infra to remove the script, page and artefacts of:
> 
> https://ci.apache.org/projects/openoffice/index.html
> 
> Regards, Matthias
> 
> FYI: I changed the schedule of the snapshot builds (414 branch) to a
> weekly base.
> 
> 
> Am 28.03.2017 um 21:15 schrieb Matthias Seidel:
>> Am 28.03.2017 um 01:55 schrieb Damjan Jovanovic:
>>> It might have changed...
>> Indeed (from:
>> https://svn.apache.org/repos//infra/infrastructure/buildbot/aegis/buildmaster/master1/public_html/README_SCRIPTS.txt):
>> 
>> Index generation scripts
>> 
>> 
>> Note:
>> The shell scripts which generate the nightly and snapshot indexes have been 
>> moved to puppet.
>> 
>> See the directory:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;a=tree;f=modules/buildbot_asf/files/projects;hb=HEAD
>> 
>> The cron jobs are defined in
>> 
>> https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;a=blob_plain;f=modules/buildbot_asf/manifests/init.pp;hb=HEAD
>> 
>> 
>> Unfortunately only the script has been moved, but not the header, footer
>> and css. Therefore the page can not be updated properly.
>> The script itself generates links to AOO 4.1.2 snapshots and needs also
>> to be changed.
>> 
>> Instead of trying to fix the generated page I would suggest to link
>> directly to nightlys/snapshots from our devbuilds homepage:
>> https://www.openoffice.org/download/devbuilds.html
>> 
>> I created a test page as example:
>> https://www.openoffice.org/download/devbuilds-test.html
>> 
>> Opinions?
>> 
>> Kind regards, Matthias
>> 
>>> On Mon, Mar 27, 2017 at 10:33 PM, Matthias Seidel <
>>> matthias.sei...@hamburg.de> wrote:
>>> 
>>>> Hi Damjan,
>>>> 
>>>> Thanks you for the link, but in:
>>>> 
>>>> https://svn.apache.org/repos/infra/infrastructure/buildbot/
>>>> aegis/buildmaster/master1/public_html/projects/openoffice/
>>>> 
>>>> I can only find header, footer and CSS but no script?
>>>> 
>>>> Regards, Matthias
>>>> 
>>>> 
>>>> Am 27.03.2017 um 18:25 schrieb Damjan Jovanovic:
>>>>> It's generated from:
>>>>> https://svn.apache.org/repos/infra/infrastructure/buildbot/
>>>> aegis/buildmaster/master1/public_html/projects/openoffice/create-ooo-
>>>> snapshots-index.sh
>>>>> Regards
>>>>> Damjan
>>>>> 
>>>>> On Mon, Mar 27, 2017 at 5:58 PM, Matthias Seidel <
>>>> matthias.sei...@hamburg.de
>>>>>> wrote:
>>>>>> Hello all!
>>>>>> 
>>>>>> Is there a way to maintain our Buildbots page?
>>>>>> 
>>>>>> https://ci.apache.org/projects/openoffice/index.html
>>>>>> 
>>>>>> Regards, Matthias
>>>>>> 
>>>>>> 
>>>>>> 
>>>> 
>> 
> 
> 


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

Re: Buildbots page

[Matthias Seidel]

Hi,

"All this work" took me about 30 minutes... ;-)

But the script has not been updated for years and the page is totally
outdated.
Feel free to maintain it.

Regards, Matthias


Am 02.04.2017 um 02:58 schrieb Gavin McDonald:
> I have no idea why you have been doing all this work, the old scripts have 
> been working fine 
> and can be updated in svn for the template parts and git for the sh script.
>
> Gav…
>
>> On 2 Apr 2017, at 6:52 am, Matthias Seidel <matthias.sei...@hamburg.de> 
>> wrote:
>>
>> If no one has objections I would make :
>>
>> https://www.openoffice.org/download/devbuilds-test.html
>>
>> live tomorrow and ask Infra to remove the script, page and artefacts of:
>>
>> https://ci.apache.org/projects/openoffice/index.html
>>
>> Regards, Matthias
>>
>> FYI: I changed the schedule of the snapshot builds (414 branch) to a
>> weekly base.
>>
>>
>> Am 28.03.2017 um 21:15 schrieb Matthias Seidel:
>>> Am 28.03.2017 um 01:55 schrieb Damjan Jovanovic:
>>>> It might have changed...
>>> Indeed (from:
>>> https://svn.apache.org/repos//infra/infrastructure/buildbot/aegis/buildmaster/master1/public_html/README_SCRIPTS.txt):
>>>
>>> Index generation scripts
>>> 
>>>
>>> Note:
>>> The shell scripts which generate the nightly and snapshot indexes have been 
>>> moved to puppet.
>>>
>>> See the directory:
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;a=tree;f=modules/buildbot_asf/files/projects;hb=HEAD
>>>
>>> The cron jobs are defined in
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;a=blob_plain;f=modules/buildbot_asf/manifests/init.pp;hb=HEAD
>>>
>>>
>>> Unfortunately only the script has been moved, but not the header, footer
>>> and css. Therefore the page can not be updated properly.
>>> The script itself generates links to AOO 4.1.2 snapshots and needs also
>>> to be changed.
>>>
>>> Instead of trying to fix the generated page I would suggest to link
>>> directly to nightlys/snapshots from our devbuilds homepage:
>>> https://www.openoffice.org/download/devbuilds.html
>>>
>>> I created a test page as example:
>>> https://www.openoffice.org/download/devbuilds-test.html
>>>
>>> Opinions?
>>>
>>> Kind regards, Matthias
>>>
>>>> On Mon, Mar 27, 2017 at 10:33 PM, Matthias Seidel <
>>>> matthias.sei...@hamburg.de> wrote:
>>>>
>>>>> Hi Damjan,
>>>>>
>>>>> Thanks you for the link, but in:
>>>>>
>>>>> https://svn.apache.org/repos/infra/infrastructure/buildbot/
>>>>> aegis/buildmaster/master1/public_html/projects/openoffice/
>>>>>
>>>>> I can only find header, footer and CSS but no script?
>>>>>
>>>>> Regards, Matthias
>>>>>
>>>>>
>>>>> Am 27.03.2017 um 18:25 schrieb Damjan Jovanovic:
>>>>>> It's generated from:
>>>>>> https://svn.apache.org/repos/infra/infrastructure/buildbot/
>>>>> aegis/buildmaster/master1/public_html/projects/openoffice/create-ooo-
>>>>> snapshots-index.sh
>>>>>> Regards
>>>>>> Damjan
>>>>>>
>>>>>> On Mon, Mar 27, 2017 at 5:58 PM, Matthias Seidel <
>>>>> matthias.sei...@hamburg.de
>>>>>>> wrote:
>>>>>>> Hello all!
>>>>>>>
>>>>>>> Is there a way to maintain our Buildbots page?
>>>>>>>
>>>>>>> https://ci.apache.org/projects/openoffice/index.html
>>>>>>>
>>>>>>> Regards, Matthias
>>>>>>>
>>>>>>>
>>>>>>>
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Buildbots page

[Gavin McDonald]

I have no idea why you have been doing all this work, the old scripts have been 
working fine 
and can be updated in svn for the template parts and git for the sh script.

Gav…

> On 2 Apr 2017, at 6:52 am, Matthias Seidel <matthias.sei...@hamburg.de> wrote:
> 
> If no one has objections I would make :
> 
> https://www.openoffice.org/download/devbuilds-test.html
> 
> live tomorrow and ask Infra to remove the script, page and artefacts of:
> 
> https://ci.apache.org/projects/openoffice/index.html
> 
> Regards, Matthias
> 
> FYI: I changed the schedule of the snapshot builds (414 branch) to a
> weekly base.
> 
> 
> Am 28.03.2017 um 21:15 schrieb Matthias Seidel:
>> Am 28.03.2017 um 01:55 schrieb Damjan Jovanovic:
>>> It might have changed...
>> Indeed (from:
>> https://svn.apache.org/repos//infra/infrastructure/buildbot/aegis/buildmaster/master1/public_html/README_SCRIPTS.txt):
>> 
>> Index generation scripts
>> 
>> 
>> Note:
>> The shell scripts which generate the nightly and snapshot indexes have been 
>> moved to puppet.
>> 
>> See the directory:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;a=tree;f=modules/buildbot_asf/files/projects;hb=HEAD
>> 
>> The cron jobs are defined in
>> 
>> https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;a=blob_plain;f=modules/buildbot_asf/manifests/init.pp;hb=HEAD
>> 
>> 
>> Unfortunately only the script has been moved, but not the header, footer
>> and css. Therefore the page can not be updated properly.
>> The script itself generates links to AOO 4.1.2 snapshots and needs also
>> to be changed.
>> 
>> Instead of trying to fix the generated page I would suggest to link
>> directly to nightlys/snapshots from our devbuilds homepage:
>> https://www.openoffice.org/download/devbuilds.html
>> 
>> I created a test page as example:
>> https://www.openoffice.org/download/devbuilds-test.html
>> 
>> Opinions?
>> 
>> Kind regards, Matthias
>> 
>>> On Mon, Mar 27, 2017 at 10:33 PM, Matthias Seidel <
>>> matthias.sei...@hamburg.de> wrote:
>>> 
>>>> Hi Damjan,
>>>> 
>>>> Thanks you for the link, but in:
>>>> 
>>>> https://svn.apache.org/repos/infra/infrastructure/buildbot/
>>>> aegis/buildmaster/master1/public_html/projects/openoffice/
>>>> 
>>>> I can only find header, footer and CSS but no script?
>>>> 
>>>> Regards, Matthias
>>>> 
>>>> 
>>>> Am 27.03.2017 um 18:25 schrieb Damjan Jovanovic:
>>>>> It's generated from:
>>>>> https://svn.apache.org/repos/infra/infrastructure/buildbot/
>>>> aegis/buildmaster/master1/public_html/projects/openoffice/create-ooo-
>>>> snapshots-index.sh
>>>>> Regards
>>>>> Damjan
>>>>> 
>>>>> On Mon, Mar 27, 2017 at 5:58 PM, Matthias Seidel <
>>>> matthias.sei...@hamburg.de
>>>>>> wrote:
>>>>>> Hello all!
>>>>>> 
>>>>>> Is there a way to maintain our Buildbots page?
>>>>>> 
>>>>>> https://ci.apache.org/projects/openoffice/index.html
>>>>>> 
>>>>>> Regards, Matthias
>>>>>> 
>>>>>> 
>>>>>> 
>>>> 
>> 
> 
> 


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

Re: Buildbots page

[Matthias Seidel]

If no one has objections I would make :

https://www.openoffice.org/download/devbuilds-test.html

live tomorrow and ask Infra to remove the script, page and artefacts of:

https://ci.apache.org/projects/openoffice/index.html

Regards, Matthias

FYI: I changed the schedule of the snapshot builds (414 branch) to a
weekly base.


Am 28.03.2017 um 21:15 schrieb Matthias Seidel:
> Am 28.03.2017 um 01:55 schrieb Damjan Jovanovic:
>> It might have changed...
> Indeed (from:
> https://svn.apache.org/repos//infra/infrastructure/buildbot/aegis/buildmaster/master1/public_html/README_SCRIPTS.txt):
>
> Index generation scripts
> 
>
> Note:
> The shell scripts which generate the nightly and snapshot indexes have been 
> moved to puppet.
>
> See the directory:
>
> https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;a=tree;f=modules/buildbot_asf/files/projects;hb=HEAD
>
> The cron jobs are defined in
>
> https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;a=blob_plain;f=modules/buildbot_asf/manifests/init.pp;hb=HEAD
>
>
> Unfortunately only the script has been moved, but not the header, footer
> and css. Therefore the page can not be updated properly.
> The script itself generates links to AOO 4.1.2 snapshots and needs also
> to be changed.
>
> Instead of trying to fix the generated page I would suggest to link
> directly to nightlys/snapshots from our devbuilds homepage:
> https://www.openoffice.org/download/devbuilds.html
>
> I created a test page as example:
> https://www.openoffice.org/download/devbuilds-test.html
>
> Opinions?
>
> Kind regards, Matthias
>
>> On Mon, Mar 27, 2017 at 10:33 PM, Matthias Seidel <
>> matthias.sei...@hamburg.de> wrote:
>>
>>> Hi Damjan,
>>>
>>> Thanks you for the link, but in:
>>>
>>> https://svn.apache.org/repos/infra/infrastructure/buildbot/
>>> aegis/buildmaster/master1/public_html/projects/openoffice/
>>>
>>> I can only find header, footer and CSS but no script?
>>>
>>> Regards, Matthias
>>>
>>>
>>> Am 27.03.2017 um 18:25 schrieb Damjan Jovanovic:
>>>> It's generated from:
>>>> https://svn.apache.org/repos/infra/infrastructure/buildbot/
>>> aegis/buildmaster/master1/public_html/projects/openoffice/create-ooo-
>>> snapshots-index.sh
>>>> Regards
>>>> Damjan
>>>>
>>>> On Mon, Mar 27, 2017 at 5:58 PM, Matthias Seidel <
>>> matthias.sei...@hamburg.de
>>>>> wrote:
>>>>> Hello all!
>>>>>
>>>>> Is there a way to maintain our Buildbots page?
>>>>>
>>>>> https://ci.apache.org/projects/openoffice/index.html
>>>>>
>>>>> Regards, Matthias
>>>>>
>>>>>
>>>>>
>>>
>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Buildbots page

[Matthias Seidel]

Am 28.03.2017 um 01:55 schrieb Damjan Jovanovic:
> It might have changed...

Indeed (from:
https://svn.apache.org/repos//infra/infrastructure/buildbot/aegis/buildmaster/master1/public_html/README_SCRIPTS.txt):

Index generation scripts


Note:
The shell scripts which generate the nightly and snapshot indexes have been 
moved to puppet.

See the directory:

https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;a=tree;f=modules/buildbot_asf/files/projects;hb=HEAD

The cron jobs are defined in

https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;a=blob_plain;f=modules/buildbot_asf/manifests/init.pp;hb=HEAD


Unfortunately only the script has been moved, but not the header, footer
and css. Therefore the page can not be updated properly.
The script itself generates links to AOO 4.1.2 snapshots and needs also
to be changed.

Instead of trying to fix the generated page I would suggest to link
directly to nightlys/snapshots from our devbuilds homepage:
https://www.openoffice.org/download/devbuilds.html

I created a test page as example:
https://www.openoffice.org/download/devbuilds-test.html

Opinions?

Kind regards, Matthias

>
> On Mon, Mar 27, 2017 at 10:33 PM, Matthias Seidel <
> matthias.sei...@hamburg.de> wrote:
>
>> Hi Damjan,
>>
>> Thanks you for the link, but in:
>>
>> https://svn.apache.org/repos/infra/infrastructure/buildbot/
>> aegis/buildmaster/master1/public_html/projects/openoffice/
>>
>> I can only find header, footer and CSS but no script?
>>
>> Regards, Matthias
>>
>>
>> Am 27.03.2017 um 18:25 schrieb Damjan Jovanovic:
>>> It's generated from:
>>> https://svn.apache.org/repos/infra/infrastructure/buildbot/
>> aegis/buildmaster/master1/public_html/projects/openoffice/create-ooo-
>> snapshots-index.sh
>>> Regards
>>> Damjan
>>>
>>> On Mon, Mar 27, 2017 at 5:58 PM, Matthias Seidel <
>> matthias.sei...@hamburg.de
>>>> wrote:
>>>> Hello all!
>>>>
>>>> Is there a way to maintain our Buildbots page?
>>>>
>>>> https://ci.apache.org/projects/openoffice/index.html
>>>>
>>>> Regards, Matthias
>>>>
>>>>
>>>>
>>
>>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Buildbots page

[Damjan Jovanovic]

It might have changed...

On Mon, Mar 27, 2017 at 10:33 PM, Matthias Seidel <
matthias.sei...@hamburg.de> wrote:

> Hi Damjan,
>
> Thanks you for the link, but in:
>
> https://svn.apache.org/repos/infra/infrastructure/buildbot/
> aegis/buildmaster/master1/public_html/projects/openoffice/
>
> I can only find header, footer and CSS but no script?
>
> Regards, Matthias
>
>
> Am 27.03.2017 um 18:25 schrieb Damjan Jovanovic:
> > It's generated from:
> > https://svn.apache.org/repos/infra/infrastructure/buildbot/
> aegis/buildmaster/master1/public_html/projects/openoffice/create-ooo-
> snapshots-index.sh
> >
> > Regards
> > Damjan
> >
> > On Mon, Mar 27, 2017 at 5:58 PM, Matthias Seidel <
> matthias.sei...@hamburg.de
> >> wrote:
> >> Hello all!
> >>
> >> Is there a way to maintain our Buildbots page?
> >>
> >> https://ci.apache.org/projects/openoffice/index.html
> >>
> >> Regards, Matthias
> >>
> >>
> >>
>
>
>

Re: Buildbots page

[Matthias Seidel]

Hi Damjan,

Thanks you for the link, but in:

https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/public_html/projects/openoffice/

I can only find header, footer and CSS but no script?

Regards, Matthias


Am 27.03.2017 um 18:25 schrieb Damjan Jovanovic:
> It's generated from:
> https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/public_html/projects/openoffice/create-ooo-snapshots-index.sh
>
> Regards
> Damjan
>
> On Mon, Mar 27, 2017 at 5:58 PM, Matthias Seidel <matthias.sei...@hamburg.de
>> wrote:
>> Hello all!
>>
>> Is there a way to maintain our Buildbots page?
>>
>> https://ci.apache.org/projects/openoffice/index.html
>>
>> Regards, Matthias
>>
>>
>>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Buildbots page

[Damjan Jovanovic]

It's generated from:
https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/public_html/projects/openoffice/create-ooo-snapshots-index.sh

Regards
Damjan

On Mon, Mar 27, 2017 at 5:58 PM, Matthias Seidel <matthias.sei...@hamburg.de
> wrote:

> Hello all!
>
> Is there a way to maintain our Buildbots page?
>
> https://ci.apache.org/projects/openoffice/index.html
>
> Regards, Matthias
>
>
>

Buildbots page

[Matthias Seidel]

Hello all!

Is there a way to maintain our Buildbots page?

https://ci.apache.org/projects/openoffice/index.html

Regards, Matthias




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Buildbots are working again

[Damjan Jovanovic]

Hi Peter

If trunk is stable and I develop in branches, then buildbots will either be
equally broken as they will break on the branches, or they will build trunk
and be stable but useless to me.

I think your biggest problem is building on Arch Linux, and I am
downloading it now to try it myself. Which bitness are you using?

Damjan

On Wed, Jan 4, 2017 at 3:00 PM, Peter Kovacs <legi...@gmail.com> wrote:

> Hi all,
>
> I am a bit unhappy with this approach. It basicly blocks all other efforts
> on the code.
>
> Ok. I am still struggeling with the build, but since I started to change
> code itself I actually making progress. I currently do not know where to
> commit those changes, so I can check on different machines (And see if my
> changes are still compatible with all other machines).
>
> I personally like to open up a branch.
>
> I also would like to see that trunc is the most stable branch we have,
> since this is the one we advertise people to start with. It is pretty hard
> to get familiar with the code if you work on something unstable.
>
> I do not mean to offend Damjan, who is doing a fine Job! - It is just I
> have the feeling our current organization is only working for a view, and
> not for all activities we are on.
>
>
> All the best
>
> Peter
>
>
> On 04.01.2017 13:27, Damjan Jovanovic wrote:
>
>> Yes, the last problem was that main/curl needed adding to
>> RepositoryExternal.mk. I've committed a fix and am testing it on the
>> FreeBSD bot now.
>>
>> The bots will be quite unstable going forward, as I am actively porting
>> modules to gbuild. They help me a lot to test different platforms quickly,
>> with different build settings - my PC mostly uses system libraries, the
>> bots internal ones. If you don't see commits to SVN for a while, and the
>> bots are still broken, then there's a problem ;-).
>>
>> Damjan
>>
>>
>>
>> On Wed, Jan 4, 2017 at 2:16 PM, Matthias Seidel <
>> matthias.sei...@hamburg.de>
>> wrote:
>>
>> Hi Damjan,
>>>
>>> Last night the linux64-41x buildbot (and maybe others)  failed. Last
>>> successful build was 31.12.2016.
>>>
>>> Do you have any idea?
>>>
>>> Regards, Matthias
>>>
>>>
>>> Am 26.12.2016 um 19:45 schrieb Damjan Jovanovic:
>>>
>>>> Hi
>>>>
>>>> All the buildbots are successfully building now.
>>>>
>>>> The FreeBSD bot was fixed by changing the buildbot script to use Clang
>>>> instead of GCC. From what I've seen, on FreeBSD, loading a mixture of
>>>> C++
>>>> libraries built with GCC and C++ libraries built with Clang into the
>>>> same
>>>> process, and using more advanced C++ features like exception handling,
>>>> causes memory corruption and crashes due to incompatible C++ ABIs;
>>>> either
>>>> every library has to be built with GCC or every library has to be built
>>>> with Clang. In practice, the former requires a rebuild of the entire
>>>> base
>>>> system and building all ports from source, which is why the latter is
>>>> better.
>>>>
>>>> The Linux bots were much harder to fix. The build was breaking because
>>>>
>>> libc
>>>
>>>> isn't linked to in some gbuild modules, something that was fixed by
>>>> explicitly always linking to libc on Linux, and because Google Test
>>>>
>>> wasn't
>>>
>>>> linking to libpthread, somehow resulting in missing symbols in at least
>>>> main/binaryurp when built without --enable-dbgutil, which was fixed by
>>>> explicitly linking it to libpthread. I don't like these linker
>>>> mysteries,
>>>> which never happen on FreeBSD, and some of which can be worked around
>>>>
>>> with
>>>
>>>> the "gold" linker...
>>>>
>>>> Damjan
>>>>
>>>>
>>>
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: Buildbots are working again

[Peter Kovacs]

Hi all,

I am a bit unhappy with this approach. It basicly blocks all other 
efforts on the code.


Ok. I am still struggeling with the build, but since I started to change 
code itself I actually making progress. I currently do not know where to 
commit those changes, so I can check on different machines (And see if 
my changes are still compatible with all other machines).


I personally like to open up a branch.

I also would like to see that trunc is the most stable branch we have, 
since this is the one we advertise people to start with. It is pretty 
hard to get familiar with the code if you work on something unstable.


I do not mean to offend Damjan, who is doing a fine Job! - It is just I 
have the feeling our current organization is only working for a view, 
and not for all activities we are on.



All the best

Peter

On 04.01.2017 13:27, Damjan Jovanovic wrote:

Yes, the last problem was that main/curl needed adding to
RepositoryExternal.mk. I've committed a fix and am testing it on the
FreeBSD bot now.

The bots will be quite unstable going forward, as I am actively porting
modules to gbuild. They help me a lot to test different platforms quickly,
with different build settings - my PC mostly uses system libraries, the
bots internal ones. If you don't see commits to SVN for a while, and the
bots are still broken, then there's a problem ;-).

Damjan



On Wed, Jan 4, 2017 at 2:16 PM, Matthias Seidel <matthias.sei...@hamburg.de>
wrote:


Hi Damjan,

Last night the linux64-41x buildbot (and maybe others)  failed. Last
successful build was 31.12.2016.

Do you have any idea?

Regards, Matthias


Am 26.12.2016 um 19:45 schrieb Damjan Jovanovic:

Hi

All the buildbots are successfully building now.

The FreeBSD bot was fixed by changing the buildbot script to use Clang
instead of GCC. From what I've seen, on FreeBSD, loading a mixture of C++
libraries built with GCC and C++ libraries built with Clang into the same
process, and using more advanced C++ features like exception handling,
causes memory corruption and crashes due to incompatible C++ ABIs; either
every library has to be built with GCC or every library has to be built
with Clang. In practice, the former requires a rebuild of the entire base
system and building all ports from source, which is why the latter is
better.

The Linux bots were much harder to fix. The build was breaking because

libc

isn't linked to in some gbuild modules, something that was fixed by
explicitly always linking to libc on Linux, and because Google Test

wasn't

linking to libpthread, somehow resulting in missing symbols in at least
main/binaryurp when built without --enable-dbgutil, which was fixed by
explicitly linking it to libpthread. I don't like these linker mysteries,
which never happen on FreeBSD, and some of which can be worked around

with

the "gold" linker...

Damjan







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

Re: Buildbots are working again

[Damjan Jovanovic]

Yes, the last problem was that main/curl needed adding to
RepositoryExternal.mk. I've committed a fix and am testing it on the
FreeBSD bot now.

The bots will be quite unstable going forward, as I am actively porting
modules to gbuild. They help me a lot to test different platforms quickly,
with different build settings - my PC mostly uses system libraries, the
bots internal ones. If you don't see commits to SVN for a while, and the
bots are still broken, then there's a problem ;-).

Damjan



On Wed, Jan 4, 2017 at 2:16 PM, Matthias Seidel <matthias.sei...@hamburg.de>
wrote:

> Hi Damjan,
>
> Last night the linux64-41x buildbot (and maybe others)  failed. Last
> successful build was 31.12.2016.
>
> Do you have any idea?
>
> Regards, Matthias
>
>
> Am 26.12.2016 um 19:45 schrieb Damjan Jovanovic:
> > Hi
> >
> > All the buildbots are successfully building now.
> >
> > The FreeBSD bot was fixed by changing the buildbot script to use Clang
> > instead of GCC. From what I've seen, on FreeBSD, loading a mixture of C++
> > libraries built with GCC and C++ libraries built with Clang into the same
> > process, and using more advanced C++ features like exception handling,
> > causes memory corruption and crashes due to incompatible C++ ABIs; either
> > every library has to be built with GCC or every library has to be built
> > with Clang. In practice, the former requires a rebuild of the entire base
> > system and building all ports from source, which is why the latter is
> > better.
> >
> > The Linux bots were much harder to fix. The build was breaking because
> libc
> > isn't linked to in some gbuild modules, something that was fixed by
> > explicitly always linking to libc on Linux, and because Google Test
> wasn't
> > linking to libpthread, somehow resulting in missing symbols in at least
> > main/binaryurp when built without --enable-dbgutil, which was fixed by
> > explicitly linking it to libpthread. I don't like these linker mysteries,
> > which never happen on FreeBSD, and some of which can be worked around
> with
> > the "gold" linker...
> >
> > Damjan
> >
>
>
>

Re: Buildbots are working again

[Matthias Seidel]

Hi Damjan,

Last night the linux64-41x buildbot (and maybe others)  failed. Last
successful build was 31.12.2016.

Do you have any idea?

Regards, Matthias


Am 26.12.2016 um 19:45 schrieb Damjan Jovanovic:
> Hi
>
> All the buildbots are successfully building now.
>
> The FreeBSD bot was fixed by changing the buildbot script to use Clang
> instead of GCC. From what I've seen, on FreeBSD, loading a mixture of C++
> libraries built with GCC and C++ libraries built with Clang into the same
> process, and using more advanced C++ features like exception handling,
> causes memory corruption and crashes due to incompatible C++ ABIs; either
> every library has to be built with GCC or every library has to be built
> with Clang. In practice, the former requires a rebuild of the entire base
> system and building all ports from source, which is why the latter is
> better.
>
> The Linux bots were much harder to fix. The build was breaking because libc
> isn't linked to in some gbuild modules, something that was fixed by
> explicitly always linking to libc on Linux, and because Google Test wasn't
> linking to libpthread, somehow resulting in missing symbols in at least
> main/binaryurp when built without --enable-dbgutil, which was fixed by
> explicitly linking it to libpthread. I don't like these linker mysteries,
> which never happen on FreeBSD, and some of which can be worked around with
> the "gold" linker...
>
> Damjan
>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Buildbots are working again

[Peter Kovacs]

Thanks a lot Damjan.
Sounds really great. I will update my repository and try to build open
office again. Maybe it works for me.
:)

All the best
Peter

Damjan Jovanovic <dam...@apache.org> schrieb am Mo., 26. Dez. 2016, 19:46:

> Hi
>
> All the buildbots are successfully building now.
>
> The FreeBSD bot was fixed by changing the buildbot script to use Clang
> instead of GCC. From what I've seen, on FreeBSD, loading a mixture of C++
> libraries built with GCC and C++ libraries built with Clang into the same
> process, and using more advanced C++ features like exception handling,
> causes memory corruption and crashes due to incompatible C++ ABIs; either
> every library has to be built with GCC or every library has to be built
> with Clang. In practice, the former requires a rebuild of the entire base
> system and building all ports from source, which is why the latter is
> better.
>
> The Linux bots were much harder to fix. The build was breaking because libc
> isn't linked to in some gbuild modules, something that was fixed by
> explicitly always linking to libc on Linux, and because Google Test wasn't
> linking to libpthread, somehow resulting in missing symbols in at least
> main/binaryurp when built without --enable-dbgutil, which was fixed by
> explicitly linking it to libpthread. I don't like these linker mysteries,
> which never happen on FreeBSD, and some of which can be worked around with
> the "gold" linker...
>
> Damjan
>
-- 

Disclaimer: Diese Nachricht stammt aus einem Google Account. Ihre Antwort
wird in der Google Cloud Gespeichert und durch Google Algorythmen zwecks
werbeanaöysen gescannt. Es ist derzeit nicht auszuschließen das ihre
Nachricht auch durch einen NSA Mitarbeiter geprüft wird. Durch
kommunikation mit diesen Account stimmen Sie zu das ihre Mail, ihre
Kontaktdaten und die Termine die Sie mit mir vereinbaren online zu Google
konditionen in der Googlecloud gespeichert wird. Sollten sie dies nicht
wünschen kontaktieren sie mich bitte Umgehend um z.B. alternativen zu
verhandeln.

Buildbots are working again

[Damjan Jovanovic]

Hi

All the buildbots are successfully building now.

The FreeBSD bot was fixed by changing the buildbot script to use Clang
instead of GCC. From what I've seen, on FreeBSD, loading a mixture of C++
libraries built with GCC and C++ libraries built with Clang into the same
process, and using more advanced C++ features like exception handling,
causes memory corruption and crashes due to incompatible C++ ABIs; either
every library has to be built with GCC or every library has to be built
with Clang. In practice, the former requires a rebuild of the entire base
system and building all ports from source, which is why the latter is
better.

The Linux bots were much harder to fix. The build was breaking because libc
isn't linked to in some gbuild modules, something that was fixed by
explicitly always linking to libc on Linux, and because Google Test wasn't
linking to libpthread, somehow resulting in missing symbols in at least
main/binaryurp when built without --enable-dbgutil, which was fixed by
explicitly linking it to libpthread. I don't like these linker mysteries,
which never happen on FreeBSD, and some of which can be worked around with
the "gold" linker...

Damjan

Re: Status of ASF Ubuntu Buildbots

[Andrea Pescetti]

Gavin McDonald wrote:

What we do have is two (imho) useless ‘snapshot’ builds (based on 
openoffice/tags/SNAPSHOT
- Which hasn’t had a commit in 10 months and never will have because its a 
‘tag’.


...which would be true if we were using SVN the textbook way, but for 
historical reasons we aren't.


The SNAPSHOT tag is meant to be moved (deleted and recreated with svn 
copy) by the release manager to mark a milestone towards the next release.



So I’ll remove those builds and replace them with 413 branch builds.
Unless someone objects.


This would make sense and align us to more "normal" practices. The 
convenience of the SNAPSHOT tag was that people providing binary 
releases had a simple reference for the build (i.e., just SNAPSHOT 
instead of a revision number). With more stable builbots we can probably 
use the latest commit at build time, i.e., simply track AOO413 HEAD as 
you suggest.


Regards,
  Andrea.

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

Re: Status of ASF Ubuntu Buildbots

[Mechtilde]

Hello Gavin

+1

Am 13.09.2016 um 03:38 schrieb Gavin McDonald:
> 
>> On 12 Sep 2016, at 8:25 AM, Marcus <marcus.m...@wtnet.de> wrote:
>>
>> Am 09/10/2016 03:51 PM, schrieb Andrea Pescetti:
>>> Gavin McDonald wrote:
>>>> I’ve been working on creating replacement VMs for the deprecated Tethys
>>>
>>> Thanks a lot. This is really much appreciated.
>>
>> yes, thanks so much for helping us with the buildbots.
>>
>>>> I reduced the frequency of some builds - I mean why spend 9 hours
>>>> building and uploading language packs every single day, there is
>>>> no need - especially from the aoo410 branch thats seen like 2 commits
>>>> in 9 months!
>>>
>>> Well, this is correct SO FAR... but now we will definitely need to build
>>> AOO410 often for 4.1.3, so a daily run would make sense as of now.
>>
>> Or AOO413 as it will be now. With more commits than in the past a higher 
>> build frequency makes sense now.
> 
> I have replaced the 410 RAT build with a 413 build.
> 
> output at: https://ci.apache.org/projects/openoffice/AOO413/rat-output.html 
> <https://ci.apache.org/projects/openoffice/AOO413/rat-output.html> tl;dr no 
> license header errors so far.
> 
> Now currently we have no 413 builds other than the RAT report.
> 
> What we do have is two (imho) useless ‘snapshot’ builds (based on 
> openoffice/tags/SNAPSHOT
> - Which hasn’t had a commit in 10 months and never will have because its a 
> ‘tag’.
> 
> So I’ll remove those builds and replace them with 413 branch builds.
> Unless someone objects.
> 
> Gav…
> 
> 
> 
>> Marcus
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
> 
> 

-- 
Mechtilde Stehmann
--
## Apache OpenOffice.org
## Freie Office Suite für Linux, MacOSX, Windows
## Debian
## Loook, calender-exchange-provider, libreoffice-canzeley-client
## PGP encryption welcome
## Key-ID 0x141AAD7F



signature.asc
Description: OpenPGP digital signature

Re: Status of ASF Ubuntu Buildbots

[Gavin McDonald]

> On 12 Sep 2016, at 8:25 AM, Marcus <marcus.m...@wtnet.de> wrote:
> 
> Am 09/10/2016 03:51 PM, schrieb Andrea Pescetti:
>> Gavin McDonald wrote:
>>> I’ve been working on creating replacement VMs for the deprecated Tethys
>> 
>> Thanks a lot. This is really much appreciated.
> 
> yes, thanks so much for helping us with the buildbots.
> 
>>> I reduced the frequency of some builds - I mean why spend 9 hours
>>> building and uploading language packs every single day, there is
>>> no need - especially from the aoo410 branch thats seen like 2 commits
>>> in 9 months!
>> 
>> Well, this is correct SO FAR... but now we will definitely need to build
>> AOO410 often for 4.1.3, so a daily run would make sense as of now.
> 
> Or AOO413 as it will be now. With more commits than in the past a higher 
> build frequency makes sense now.

I have replaced the 410 RAT build with a 413 build.

output at: https://ci.apache.org/projects/openoffice/AOO413/rat-output.html 
<https://ci.apache.org/projects/openoffice/AOO413/rat-output.html> tl;dr no 
license header errors so far.

Now currently we have no 413 builds other than the RAT report.

What we do have is two (imho) useless ‘snapshot’ builds (based on 
openoffice/tags/SNAPSHOT
- Which hasn’t had a commit in 10 months and never will have because its a 
‘tag’.

So I’ll remove those builds and replace them with 413 branch builds.
Unless someone objects.

Gav…



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

Re: Status of ASF Ubuntu Buildbots

[Marcus]

Am 09/10/2016 03:51 PM, schrieb Andrea Pescetti:

Gavin McDonald wrote:

I’ve been working on creating replacement VMs for the deprecated Tethys


Thanks a lot. This is really much appreciated.


yes, thanks so much for helping us with the buildbots.


I reduced the frequency of some builds - I mean why spend 9 hours
building and uploading language packs every single day, there is
no need - especially from the aoo410 branch thats seen like 2 commits
in 9 months!


Well, this is correct SO FAR... but now we will definitely need to build
AOO410 often for 4.1.3, so a daily run would make sense as of now.


Or AOO413 as it will be now. With more commits than in the past a higher 
build frequency makes sense now.


Marcus


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

Re: Status of ASF Ubuntu Buildbots

[Mechtilde]

Hello

+1 in general

I think one build per week or two weeks is enough.

It should be possible to start it manually if there are some bigger
commits..

The person who commit code to the main branch should be able to start
the buildbots.

Kind regards

Mechtilde

Am 10.09.2016 um 02:24 schrieb Gavin McDonald:
> Hi All,
> 
> I’ve been working on creating replacement VMs for the deprecated Tethys 
> (10.04 64bit) , bb-vm2 (12.04 32bit) and bb-vm3 (12.04 32bit).
> This work is now complete. 3 VMs replaced with 2 x 14.04 LTS VMs. (As an 
> aside there is a 16.04 LTS buildbot available if you want to
> do tests on it)
> 
> 3 builds were moved from Tethys to bb_slave4_ubuntu - the linux64 nightly 
> build and the two RAT builds (trunk and aoo410 testing)
> All 3 builds are successful currently.
> 
> The linux32-nightly and linux32-snapshot builds have been moved from bb-vm2 
> and bb-vm3 to bb_slave5_ubuntu - initial builds are
> still being performed.
> 
> I reduced the frequency of some builds - I mean why spend 9 hours building 
> and uploading language packs every single day, there is 
> no need - especially from the aoo410 branch thats seen like 2 commits in 9 
> months!
> 
> the openoffice.conf file has been updated. Feel free to start tweaking the 
> linux32 builds after the initial builds have completed in a day or so.
> 
> Any questions, I’m here on list.
> 
> Gav…
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 

-- 
Mechtilde Stehmann
--
## Apache OpenOffice.org
## Freie Office Suite für Linux, MacOSX, Windows
## Debian
## Loook, calender-exchange-provider, libreoffice-canzeley-client
## PGP encryption welcome
## Key-ID 0x141AAD7F



signature.asc
Description: OpenPGP digital signature

Status of ASF Ubuntu Buildbots

[Gavin McDonald]

Hi All,

I’ve been working on creating replacement VMs for the deprecated Tethys (10.04 
64bit) , bb-vm2 (12.04 32bit) and bb-vm3 (12.04 32bit).
This work is now complete. 3 VMs replaced with 2 x 14.04 LTS VMs. (As an aside 
there is a 16.04 LTS buildbot available if you want to
do tests on it)

3 builds were moved from Tethys to bb_slave4_ubuntu - the linux64 nightly build 
and the two RAT builds (trunk and aoo410 testing)
All 3 builds are successful currently.

The linux32-nightly and linux32-snapshot builds have been moved from bb-vm2 and 
bb-vm3 to bb_slave5_ubuntu - initial builds are
still being performed.

I reduced the frequency of some builds - I mean why spend 9 hours building and 
uploading language packs every single day, there is 
no need - especially from the aoo410 branch thats seen like 2 commits in 9 
months!

the openoffice.conf file has been updated. Feel free to start tweaking the 
linux32 builds after the initial builds have completed in a day or so.

Any questions, I’m here on list.

Gav…


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

Re: Buildbots update

[Don Lewis]

On 24 Jul, Andrea Pescetti wrote:
> On 22/07/2016 Don Lewis wrote:
>> On 22 Jul, Damjan Jovanovic wrote:
>>> I've progressed much further
> 
> Thanks Damjan for the (as usual) great progress.
> 
>>> Buildbots
>>> should immediately fail the build if ./bootstrap fails
>> Yes, there is no sense in continuing if bootstrap fails
> 
> Yes, sure.
> 
>>> 5 hours is pure waste. Alternatively we should find a more reliable
>>> ooo-extras hosting solution than SourceForge. We could also cache
>>> dependencies offline between builds, but I am guessing that has licensing
>>> issues?
> 
> No, dependencies we temporarily download on a build machine are not 
> affected by licensing issues.
> 
> Maybe an extra parameter --cache-dir=$DIR to bootstrap would work? This 
> way we could setup a dedicated cache directory on the buildbots (even if 
> we are doing a "clean build", there is really no point in re-downloading 
> a file if the checksum matches).

That's a good idea, though we should probably have another bot that
periodically checks for working downloads.  There's no need for each
buildbot to do it though, which ends up happend now multiple times per
day.


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

Re: Buildbots update

[Don Lewis]

On 24 Jul, Damjan Jovanovic wrote:
> On Fri, Jul 22, 2016 at 9:39 PM, Don Lewis <truck...@apache.org> wrote:
> 
>> On 22 Jul, Damjan Jovanovic wrote:
>> > I've progressed much further, and openoffice-fbsd-nightly,
>> > openoffice-linux32-nightly, openoffice-linux64-nightly, and
>> > openoffice-linux64-rat are now building, while
>> openoffice-linux32-snapshot
>> > is only temporarily breaking due to SourceForge issues. I've also made
>> some
>> > interesting discoveries about the Windows buildbots.
>>
>> FreeBSD still needs LWP::Protocol::https.  It's only working because of
>> the non-https fallback to a specific SourceForge mirror.
>>
>>
> No, it's only working because of --with-system-

The FreeBSD buildbot uses more --with-system stuff that the other
buildbots, but not as much as the FreeBSD port.  It was still getting
LWP::Protocol::https failures, but they weren't fatal because of the
fallback to a specific http SourceForge mirror.  Most recently it was
only succeeding while the Linux buildbots were failing to download
openssl because thate version wasn't present on the SourceForge mirror
and the FreeBSD buildbot used --with-system-openssl.

BTW, the FreeBSD port doesn't rely on bootstrap to download anything.
Bootstrap is run during the build stage, and when building FreeBSD
packages, there is no network connectivity during the build stage.
Instead, everything is downloaded and stashed in ext_sources before
configure is run.

> Also LWP::Protocol::https is dead now, please see my upcoming email.

Ding, dong, the witch is dead ...

>> > That buildbot is currently running out of disk space, and it doesn't help
>> > that we "svn co" and then "svn export" a second copy. Originally the
>> > buildbot script used other tricks, like "svn switch", or keeping an SVN
>> > checkout across builds that was just updated and then exported from for
>> > each build, but some time ago I switched to a full "svn co" because it
>> was
>> > too unreliable (eg. files can get locked and need "svn cleanup"). With a
>> > full checkout there is no need to export, as we get a fresh copy each
>> time.
>> > I'll overhaul that buildbot script and try make it simpler and cleaner.
>>
>> Doing an update followed by an export of that would be less resource
>> intensive, though it adds 50% (since .svn isn't copied) to the space
>> consumed by the source.  The write-locked file problem should only occur
>> if the update is interrupted, and since there is so little activity in
>> the repo, the updates should be pretty fast have a low probability of
>> failing.  A full checkout would be much more likely to fail in the
>> middle.  You could always run "svn cleanup" before "svn update".
>>
>> A checked out source tree for 4.1.2 is about 725 MB.  A second exported
>> copy would bring the total up to about 1090 MB, which is still fairly
>> small compared to the overall build size.  If space is an issue and load
>> on the svn server is not, then doing a fresh export (vs a checkout) from
>> the server each time would be the best.
>>
>>
> Space was an issue because I was using the small C: drive instead of E:.
> 
> As the buildbots run automatically and we usually don't initiate builds and
> wait for results, little is lost by doing SVN update the slowest way, and
> much is gained through the increased reliability and simplicity.

Doing svn export direct from the repo would be just as reliable as svn
co.  It would be quicker and more spece efficient because it wouldn't
create a second copy of the source under .svn that we don't use since we
aren't doing incremental updates and we are just going to delete at the
start of the next build.

Thanks for spending the time on this!  It'll be awesome having working
buildbots again.

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

Re: Buildbots update

[Andrea Pescetti]

On 22/07/2016 Don Lewis wrote:

On 22 Jul, Damjan Jovanovic wrote:

I've progressed much further


Thanks Damjan for the (as usual) great progress.


Buildbots
should immediately fail the build if ./bootstrap fails

Yes, there is no sense in continuing if bootstrap fails


Yes, sure.


5 hours is pure waste. Alternatively we should find a more reliable
ooo-extras hosting solution than SourceForge. We could also cache
dependencies offline between builds, but I am guessing that has licensing
issues?


No, dependencies we temporarily download on a build machine are not 
affected by licensing issues.


Maybe an extra parameter --cache-dir=$DIR to bootstrap would work? This 
way we could setup a dedicated cache directory on the buildbots (even if 
we are doing a "clean build", there is really no point in re-downloading 
a file if the checksum matches).



showed 4 nmake processes, 2 from March 30, 2 from April 4, part of
orphaned trees also containing perl, sh, and dmake.


At least we could have the VM restarted to make sure we don't carry 
stale processes around for months. Infra can for sure do it with minimal 
effort. And access to the dedicated IRC channel for giving instructions 
to buildbots might be useful too (I guess you know what I am talking 
about; if not, just ask and I can look it up).


Regards,
  Andrea.

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

Re: Buildbots update

[Damjan Jovanovic]

On Fri, Jul 22, 2016 at 9:39 PM, Don Lewis <truck...@apache.org> wrote:

> On 22 Jul, Damjan Jovanovic wrote:
> > I've progressed much further, and openoffice-fbsd-nightly,
> > openoffice-linux32-nightly, openoffice-linux64-nightly, and
> > openoffice-linux64-rat are now building, while
> openoffice-linux32-snapshot
> > is only temporarily breaking due to SourceForge issues. I've also made
> some
> > interesting discoveries about the Windows buildbots.
>
> FreeBSD still needs LWP::Protocol::https.  It's only working because of
> the non-https fallback to a specific SourceForge mirror.
>
>
No, it's only working because of --with-system-

Also LWP::Protocol::https is dead now, please see my upcoming email.


> > I had to revert r1736692 (in r1753709), setting main/extensions.lst back
> to
> > generic https:// SourceForge URLs, as the mirror-specific http:// URLs
> are
> > now broken, which was causing all buildbots that use
> > --enable-bundled-dictionaries to fail. Enough buildbots support https now
> > to make this a net benefit.
>
> The iweb mirror is out of service, but switching the main SourceForge
> URL to pilotfiber (in r1752780) fixed that.
>
> > Also had to upload openssl-0.9.8zg to ooo-extras for the
> > openoffice-linux32-snapshot, but the most recent build failed because it
> > couldn't download some dictionaries/languages from SourceForge, which I
> am
> > generally finding to be too flaky.
> >
> > I think we should either run ./bootstrap multiple times on the buildbots,
> > or list SourceForge URLs several times in external_deps.lst and
> > extensions.lst, to compensate for SourceForge's unreliability. Buildbots
> > should immediately fail the build if ./bootstrap fails, as there is no
> > hope: ./bootstrap only downloads dependencies needed for the build, and
> if
> > any are missing, the build will definitely fail, and burning CPU for up
> to
> > 5 hours is pure waste. Alternatively we should find a more reliable
> > ooo-extras hosting solution than SourceForge. We could also cache
> > dependencies offline between builds, but I am guessing that has licensing
> > issues?
>
> Yes, there is no sense in continuing if bootstrap fails.
>
> > That leaves the Windows bots.
> > aoo-w7snap is still missing LWP::Protocol::https.
> > aoo-win7 was failing to delete the old build files (rm: cannot remove
> > `build/ext_libraries/apr/wntmsci12.pro/misc/build/apr-1.4.5/Makefile.win
> ':
> > Device or resource busy).
> > Something seems to be keeping that file open even after the previous
> builds
> > are over.
> > According to ext_libraries/apr/makefile.mk, the BUILD_ACTION on Windows
> is:
> > INCLUDE="$(INCLUDE);./include"  nmake -f Makefile.win buildall
> > so I suspected nmake hangs.
> >
> > I patched the build script to run "ps -W" (results at
> > https://ci.apache.org/builders/aoo-win7/builds/348/steps/ps/logs/stdio)
> > which showed 4 nmake processes, 2 from March 30, 2 from April 4, part of
> > orphaned trees also containing perl, sh, and dmake.
> > Killing nmake (through hacks to the buildbot script, as I still don't
> have
> > remote access) had no effect - deleting apr-1.4.5/Makefile.win was still
> > giving the same error.
> > Even killing dmake, sh and perl (which had to be done in creative ways on
> > that dodgy OS - some through taskkill, some through Cygwin's kill) still
> > had no effect.
> > After all Cygwin processes were dead, that error was still coming up!
> >
> > So I started looking at non-Cygwin processes. DEVENV.EXE and DEVENV.COM
> had
> > the same March 30 / April 4 start times as the hung process trees, and
> > killing them *finally* allowed apr-1.4.5/Makefile.win to be deleted.
> >
> > I'll experiment a lot more over the weekend, but right now I think the
> > problem could be that the buildbot runs VSVARS.BAT to set up the Visual
> > Studio environment, which (presumably) contains the evil DEVENV that
> break
> > the build and locks files while hung. On my own Windows VM I don't run
> > VSVARS.BAT, and I can't reproduce the problem. Do the rest of you that
> > build on Windows use it?
>
> Since VSVARS.BAT was not listed in the step by step guide, I haven't
> been running it.  It sounds a lot like it just sets some environment
> variables to find where the various bits of VS are installed, so I would
> think it would be generally harmless.  I've been running builds from the
> desktop.  VSVARS.BAT might be needed when running headless ...
>
> I did some searches and saw some mention that DEVENV.* hangs m

Re: Buildbots update

[Kay Schenk]

On Fri, Jul 22, 2016 at 12:09 AM, Damjan Jovanovic <dam...@apache.org>
wrote:

> I've progressed much further, and openoffice-fbsd-nightly,
> openoffice-linux32-nightly, openoffice-linux64-nightly, and
> openoffice-linux64-rat are now building, while openoffice-linux32-snapshot
> is only temporarily breaking due to SourceForge issues. I've also made some
> interesting discoveries about the Windows buildbots.
>

​Lookin' pretty good so far! A BIG thank you again for all your work on
this!
Dealing with the buildbot configurations is quite a challenge!
​


>
> I had to revert r1736692 (in r1753709), setting main/extensions.lst back to
> generic https:// SourceForge URLs, as the mirror-specific http:// URLs are
> now broken, which was causing all buildbots that use
> --enable-bundled-dictionaries to fail. Enough buildbots support https now
> to make this a net benefit.
>
> Also had to upload openssl-0.9.8zg to ooo-extras for the
> openoffice-linux32-snapshot, but the most recent build failed because it
> couldn't download some dictionaries/languages from SourceForge, which I am
> generally finding to be too flaky.
>
> I think we should either run ./bootstrap multiple times on the buildbots,
> or list SourceForge URLs several times in external_deps.lst and
> extensions.lst, to compensate for SourceForge's unreliability. Buildbots
> should immediately fail the build if ./bootstrap fails, as there is no
> hope: ./bootstrap only downloads dependencies needed for the build, and if
> any are missing, the build will definitely fail, and burning CPU for up to
> 5 hours is pure waste. Alternatively we should find a more reliable
> ooo-extras hosting solution than SourceForge. We could also cache
> dependencies offline between builds, but I am guessing that has licensing
> issues?
>
> That leaves the Windows bots.
> aoo-w7snap is still missing LWP::Protocol::https.
> aoo-win7 was failing to delete the old build files (rm: cannot remove
> `build/ext_libraries/apr/wntmsci12.pro/misc/build/apr-1.4.5/Makefile.win':
> Device or resource busy).
> Something seems to be keeping that file open even after the previous builds
> are over.
> According to ext_libraries/apr/makefile.mk, the BUILD_ACTION on Windows
> is:
> INCLUDE="$(INCLUDE);./include"  nmake -f Makefile.win buildall
> so I suspected nmake hangs.
>
> I patched the build script to run "ps -W" (results at
> https://ci.apache.org/builders/aoo-win7/builds/348/steps/ps/logs/stdio)
> which showed 4 nmake processes, 2 from March 30, 2 from April 4, part of
> orphaned trees also containing perl, sh, and dmake.
> Killing nmake (through hacks to the buildbot script, as I still don't have
> remote access) had no effect - deleting apr-1.4.5/Makefile.win was still
> giving the same error.
> Even killing dmake, sh and perl (which had to be done in creative ways on
> that dodgy OS - some through taskkill, some through Cygwin's kill) still
> had no effect.
> After all Cygwin processes were dead, that error was still coming up!
>
> So I started looking at non-Cygwin processes. DEVENV.EXE and DEVENV.COM
> had
> the same March 30 / April 4 start times as the hung process trees, and
> killing them *finally* allowed apr-1.4.5/Makefile.win to be deleted.
>
> I'll experiment a lot more over the weekend, but right now I think the
> problem could be that the buildbot runs VSVARS.BAT to set up the Visual
> Studio environment, which (presumably) contains the evil DEVENV that break
> the build and locks files while hung. On my own Windows VM I don't run
> VSVARS.BAT, and I can't reproduce the problem. Do the rest of you that
> build on Windows use it?
>
> That buildbot is currently running out of disk space, and it doesn't help
> that we "svn co" and then "svn export" a second copy. Originally the
> buildbot script used other tricks, like "svn switch", or keeping an SVN
> checkout across builds that was just updated and then exported from for
> each build, but some time ago I switched to a full "svn co" because it was
> too unreliable (eg. files can get locked and need "svn cleanup"). With a
> full checkout there is no need to export, as we get a fresh copy each time.
> I'll overhaul that buildbot script and try make it simpler and cleaner.
>
> On Tue, Jul 19, 2016 at 8:17 PM, Damjan Jovanovic <dam...@apache.org>
> wrote:
>
> > Hi
> >
> > I contacted Infra on HipChat and asked them to fix the buildbots I could
> > find with the Perl LWP::Protocol::https problem (aoo-w7snap,
> > openoffice-fbsd-nightly, and openoffice-linux32-nightly) or give me
> access
> > to do it myself, and @pono fixed at least the op

Re: Buildbots update

[Don Lewis]

On 22 Jul, Damjan Jovanovic wrote:
> I've progressed much further, and openoffice-fbsd-nightly,
> openoffice-linux32-nightly, openoffice-linux64-nightly, and
> openoffice-linux64-rat are now building, while openoffice-linux32-snapshot
> is only temporarily breaking due to SourceForge issues. I've also made some
> interesting discoveries about the Windows buildbots.

FreeBSD still needs LWP::Protocol::https.  It's only working because of
the non-https fallback to a specific SourceForge mirror.

> I had to revert r1736692 (in r1753709), setting main/extensions.lst back to
> generic https:// SourceForge URLs, as the mirror-specific http:// URLs are
> now broken, which was causing all buildbots that use
> --enable-bundled-dictionaries to fail. Enough buildbots support https now
> to make this a net benefit.

The iweb mirror is out of service, but switching the main SourceForge
URL to pilotfiber (in r1752780) fixed that.

> Also had to upload openssl-0.9.8zg to ooo-extras for the
> openoffice-linux32-snapshot, but the most recent build failed because it
> couldn't download some dictionaries/languages from SourceForge, which I am
> generally finding to be too flaky.
> 
> I think we should either run ./bootstrap multiple times on the buildbots,
> or list SourceForge URLs several times in external_deps.lst and
> extensions.lst, to compensate for SourceForge's unreliability. Buildbots
> should immediately fail the build if ./bootstrap fails, as there is no
> hope: ./bootstrap only downloads dependencies needed for the build, and if
> any are missing, the build will definitely fail, and burning CPU for up to
> 5 hours is pure waste. Alternatively we should find a more reliable
> ooo-extras hosting solution than SourceForge. We could also cache
> dependencies offline between builds, but I am guessing that has licensing
> issues?

Yes, there is no sense in continuing if bootstrap fails.

> That leaves the Windows bots.
> aoo-w7snap is still missing LWP::Protocol::https.
> aoo-win7 was failing to delete the old build files (rm: cannot remove
> `build/ext_libraries/apr/wntmsci12.pro/misc/build/apr-1.4.5/Makefile.win':
> Device or resource busy).
> Something seems to be keeping that file open even after the previous builds
> are over.
> According to ext_libraries/apr/makefile.mk, the BUILD_ACTION on Windows is:
> INCLUDE="$(INCLUDE);./include"  nmake -f Makefile.win buildall
> so I suspected nmake hangs.
> 
> I patched the build script to run "ps -W" (results at
> https://ci.apache.org/builders/aoo-win7/builds/348/steps/ps/logs/stdio)
> which showed 4 nmake processes, 2 from March 30, 2 from April 4, part of
> orphaned trees also containing perl, sh, and dmake.
> Killing nmake (through hacks to the buildbot script, as I still don't have
> remote access) had no effect - deleting apr-1.4.5/Makefile.win was still
> giving the same error.
> Even killing dmake, sh and perl (which had to be done in creative ways on
> that dodgy OS - some through taskkill, some through Cygwin's kill) still
> had no effect.
> After all Cygwin processes were dead, that error was still coming up!
> 
> So I started looking at non-Cygwin processes. DEVENV.EXE and DEVENV.COM had
> the same March 30 / April 4 start times as the hung process trees, and
> killing them *finally* allowed apr-1.4.5/Makefile.win to be deleted.
> 
> I'll experiment a lot more over the weekend, but right now I think the
> problem could be that the buildbot runs VSVARS.BAT to set up the Visual
> Studio environment, which (presumably) contains the evil DEVENV that break
> the build and locks files while hung. On my own Windows VM I don't run
> VSVARS.BAT, and I can't reproduce the problem. Do the rest of you that
> build on Windows use it?

Since VSVARS.BAT was not listed in the step by step guide, I haven't
been running it.  It sounds a lot like it just sets some environment
variables to find where the various bits of VS are installed, so I would
think it would be generally harmless.  I've been running builds from the
desktop.  VSVARS.BAT might be needed when running headless ...

I did some searches and saw some mention that DEVENV.* hangs might be
caused by anti-virus software.  Is that running on the windows buildbot?
 
> That buildbot is currently running out of disk space, and it doesn't help
> that we "svn co" and then "svn export" a second copy. Originally the
> buildbot script used other tricks, like "svn switch", or keeping an SVN
> checkout across builds that was just updated and then exported from for
> each build, but some time ago I switched to a full "svn co" because it was
> too unreliable (eg. files can get locked and need "svn cleanup"). With a
> full checkout there is no need to export, as w

Re: Buildbots update

[Marcus]

Am 07/22/2016 09:09 AM, schrieb Damjan Jovanovic:

I've progressed much further, and openoffice-fbsd-nightly,
openoffice-linux32-nightly, openoffice-linux64-nightly, and
openoffice-linux64-rat are now building, while openoffice-linux32-snapshot
is only temporarily breaking due to SourceForge issues. I've also made some
interesting discoveries about the Windows buildbots.

[...]


that's great news and very valueable. Thanks a lot for not letting go 
this important stuff. :-)


Marcus


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

Re: Buildbots update

[Patricia Shanahan]

On 7/22/2016 12:09 AM, Damjan Jovanovic wrote:
...

I'll experiment a lot more over the weekend, but right now I think the
problem could be that the buildbot runs VSVARS.BAT to set up the Visual
Studio environment, which (presumably) contains the evil DEVENV that break
the build and locks files while hung. On my own Windows VM I don't run
VSVARS.BAT, and I can't reproduce the problem. Do the rest of you that
build on Windows use it?

...

I don't explicitly run it, and cannot find it in any of the scripts such 
as configure that I do run. I copy pieces of Visual Studio into 
main/external/ directories, as described in 
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7.2C_Windows_8.1


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

Re: Buildbots update

[Damjan Jovanovic]

I've progressed much further, and openoffice-fbsd-nightly,
openoffice-linux32-nightly, openoffice-linux64-nightly, and
openoffice-linux64-rat are now building, while openoffice-linux32-snapshot
is only temporarily breaking due to SourceForge issues. I've also made some
interesting discoveries about the Windows buildbots.

I had to revert r1736692 (in r1753709), setting main/extensions.lst back to
generic https:// SourceForge URLs, as the mirror-specific http:// URLs are
now broken, which was causing all buildbots that use
--enable-bundled-dictionaries to fail. Enough buildbots support https now
to make this a net benefit.

Also had to upload openssl-0.9.8zg to ooo-extras for the
openoffice-linux32-snapshot, but the most recent build failed because it
couldn't download some dictionaries/languages from SourceForge, which I am
generally finding to be too flaky.

I think we should either run ./bootstrap multiple times on the buildbots,
or list SourceForge URLs several times in external_deps.lst and
extensions.lst, to compensate for SourceForge's unreliability. Buildbots
should immediately fail the build if ./bootstrap fails, as there is no
hope: ./bootstrap only downloads dependencies needed for the build, and if
any are missing, the build will definitely fail, and burning CPU for up to
5 hours is pure waste. Alternatively we should find a more reliable
ooo-extras hosting solution than SourceForge. We could also cache
dependencies offline between builds, but I am guessing that has licensing
issues?

That leaves the Windows bots.
aoo-w7snap is still missing LWP::Protocol::https.
aoo-win7 was failing to delete the old build files (rm: cannot remove
`build/ext_libraries/apr/wntmsci12.pro/misc/build/apr-1.4.5/Makefile.win':
Device or resource busy).
Something seems to be keeping that file open even after the previous builds
are over.
According to ext_libraries/apr/makefile.mk, the BUILD_ACTION on Windows is:
INCLUDE="$(INCLUDE);./include"  nmake -f Makefile.win buildall
so I suspected nmake hangs.

I patched the build script to run "ps -W" (results at
https://ci.apache.org/builders/aoo-win7/builds/348/steps/ps/logs/stdio)
which showed 4 nmake processes, 2 from March 30, 2 from April 4, part of
orphaned trees also containing perl, sh, and dmake.
Killing nmake (through hacks to the buildbot script, as I still don't have
remote access) had no effect - deleting apr-1.4.5/Makefile.win was still
giving the same error.
Even killing dmake, sh and perl (which had to be done in creative ways on
that dodgy OS - some through taskkill, some through Cygwin's kill) still
had no effect.
After all Cygwin processes were dead, that error was still coming up!

So I started looking at non-Cygwin processes. DEVENV.EXE and DEVENV.COM had
the same March 30 / April 4 start times as the hung process trees, and
killing them *finally* allowed apr-1.4.5/Makefile.win to be deleted.

I'll experiment a lot more over the weekend, but right now I think the
problem could be that the buildbot runs VSVARS.BAT to set up the Visual
Studio environment, which (presumably) contains the evil DEVENV that break
the build and locks files while hung. On my own Windows VM I don't run
VSVARS.BAT, and I can't reproduce the problem. Do the rest of you that
build on Windows use it?

That buildbot is currently running out of disk space, and it doesn't help
that we "svn co" and then "svn export" a second copy. Originally the
buildbot script used other tricks, like "svn switch", or keeping an SVN
checkout across builds that was just updated and then exported from for
each build, but some time ago I switched to a full "svn co" because it was
too unreliable (eg. files can get locked and need "svn cleanup"). With a
full checkout there is no need to export, as we get a fresh copy each time.
I'll overhaul that buildbot script and try make it simpler and cleaner.

On Tue, Jul 19, 2016 at 8:17 PM, Damjan Jovanovic <dam...@apache.org> wrote:

> Hi
>
> I contacted Infra on HipChat and asked them to fix the buildbots I could
> find with the Perl LWP::Protocol::https problem (aoo-w7snap,
> openoffice-fbsd-nightly, and openoffice-linux32-nightly) or give me access
> to do it myself, and @pono fixed at least the openoffice-linux32-nightly
> bot.
>
> The other buildbots are either failing earlier or failing for other
> reasons. For example openoffice-linux64-nightly was failing to download
> openssl ("500 Can't connect to www.openssl.org:443"), but I've uploaded
> it to ooo-extras and it's gotten further in the build I am forcing now.
>
> Damjan
>
>

Re: Buildbots update

[kaysch...@apache.org]

On 07/19/2016 11:17 AM, Damjan Jovanovic wrote:
> Hi
> 
> I contacted Infra on HipChat and asked them to fix the buildbots I could
> find with the Perl LWP::Protocol::https problem (aoo-w7snap,
> openoffice-fbsd-nightly, and openoffice-linux32-nightly) or give me access
> to do it myself, and @pono fixed at least the openoffice-linux32-nightly
> bot.
> 
> The other buildbots are either failing earlier or failing for other
> reasons. For example openoffice-linux64-nightly was failing to download
> openssl ("500 Can't connect to www.openssl.org:443"), but I've uploaded it
> to ooo-extras and it's gotten further in the build I am forcing now.
> 
> Damjan
> 

Thanks for looking into this, Damjan!

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

Buildbots update

[Damjan Jovanovic]

Hi

I contacted Infra on HipChat and asked them to fix the buildbots I could
find with the Perl LWP::Protocol::https problem (aoo-w7snap,
openoffice-fbsd-nightly, and openoffice-linux32-nightly) or give me access
to do it myself, and @pono fixed at least the openoffice-linux32-nightly
bot.

The other buildbots are either failing earlier or failing for other
reasons. For example openoffice-linux64-nightly was failing to download
openssl ("500 Can't connect to www.openssl.org:443"), but I've uploaded it
to ooo-extras and it's gotten further in the build I am forcing now.

Damjan

Re: Getting buildbots operational again

[Kay Schenk]

On Sun, Mar 27, 2016 at 12:51 AM, Andrea Pescetti <pesce...@apache.org>
wrote:

> On 26/03/2016 Andrea Pescetti wrote:
>
>> https://bz.apache.org/ooo/show_bug.cgi?id=126892
>> This will hopefully mean that buildbots get past the "./bootstrap"
>> phase. It is a temporary fix
>>
>
> All buildbots are indeed now past the "./bootstrap" phase (the one that
> had been failing in the last month) and they are now building, which will
> take several hours.
>
> You can see the nightly ones here:
> https://ci.apache.org/builders/aoo-win7
> https://ci.apache.org/builders/openoffice-fbsd-nightly
> https://ci.apache.org/builders/openoffice-linux32-nightly
> https://ci.apache.org/builders/openoffice-linux64-nightly
>
> (the last one was already OK since it is on the system that Infra had
> already updated to support HTTPS).
>
>
> Regards,
>   Andrea.
>

​Thank you SO much for this fix.
​




-- 
--
MzK

"Time spent with cats is never wasted."
-- Sigmund Freud

Re: Getting buildbots operational again

[Marcus]

Am 03/26/2016 12:20 PM, schrieb Andrea Pescetti:

If someone is interested in the story, all buildbots broke because we
download dependencies from the (SourceForge-hosted) ooo-extras
repository before building. SF decided to switch from HTTP to HTTPS but
our buildbots were caught unprepared (we use a Perl script that needs an
additional Perl module to use HTTPS). So the reason buildbots fail is
that one small installation must be done on each machine, and this is a
task for Infra.


ah, thats the problem. Now I got the complete picture. Thanks.


This will hopefully mean that buildbots get past the "./bootstrap"
phase. It is a temporary fix that will be reverted when all buildbots
support HTTPS download.


I cross my fingers. :-)

Marcus


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

Getting buildbots operational again

[Andrea Pescetti]

Issue https://issues.apache.org/jira/browse/INFRA-11296 has been open 
for more than one month. It prevents buildbots from operating correctly. 
Infra did fix one buildbot, but 5 are still waiting.


If someone is interested in the story, all buildbots broke because we 
download dependencies from the (SourceForge-hosted) ooo-extras 
repository before building. SF decided to switch from HTTP to HTTPS but 
our buildbots were caught unprepared (we use a Perl script that needs an 
additional Perl module to use HTTPS). So the reason buildbots fail is 
that one small installation must be done on each machine, and this is a 
task for Infra.


But due to this we can't have nightly builds and we can't test the 
changes Damjan did months ago in an attempt to fix the Windows buildbots.


Fortunately it seems there's a workaround: SourceForge uses HTTPS for 
the mirror selection, but then the file gets downloaded through HTTP 
from the selected mirror. So I've gone ahead and I've changed the 
generic SourceForge URLs to a pre-selected SourceForge mirror (the one I 
was getting in my tests). See 
https://bz.apache.org/ooo/show_bug.cgi?id=126892


This will hopefully mean that buildbots get past the "./bootstrap" 
phase. It is a temporary fix that will be reverted when all buildbots 
support HTTPS download.


Regards,
  Andrea.

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

Re: Buildbots are back

[Pedro Giffuni]

Nice!

Thanks to everyone involved. The FreeBSD buildbot appears to need the 
same treatment BTW.


Pedro.

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

Re: Buildbots are back

[Kay Schenk]

On Tue, Mar 1, 2016 at 12:00 AM, Andrea Pescetti <pesce...@apache.org>
wrote:

> As you may have noticed, our buildbots are back. We now have development
> builds available.
>
> A missing package needed to be installed by Infra on the buildbots and
> they started installing it on the various VMs.
>
> The Linux buildbots already picked up the change:
> https://ci.apache.org/builders/openoffice-linux32-snapshot
> https://ci.apache.org/builders/openoffice-linux64-nightly/
>

> The Windows ones probably do not have the fix yet, but once it is deployed
> there too, we will get past this blocker and we may able to check better
> what is still in the way before getting Windows nightly builds available
> again.
>
> Reference: https://issues.apache.org/jira/browse/INFRA-11296
>
> Regards,
>   Andrea.
>


​Good news! ​
Hopefully they can get to the linux32-nightly
​ ​
​(different VM than linux32-SNAPSHOT) ​
and win7 VM soon.



-- 
--
MzK

"Though no one can go back and make a brand new start,
 anyone can start from now and make a brand new ending."
  -- Carl Bard

Buildbots are back

[Andrea Pescetti]

As you may have noticed, our buildbots are back. We now have development 
builds available.


A missing package needed to be installed by Infra on the buildbots and 
they started installing it on the various VMs.


The Linux buildbots already picked up the change:
https://ci.apache.org/builders/openoffice-linux32-snapshot
https://ci.apache.org/builders/openoffice-linux64-nightly/

The Windows ones probably do not have the fix yet, but once it is 
deployed there too, we will get past this blocker and we may able to 
check better what is still in the way before getting Windows nightly 
builds available again.


Reference: https://issues.apache.org/jira/browse/INFRA-11296

Regards,
  Andrea.

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

Re: Buildbots update

[Andrea Pescetti]

Damjan Jovanovic wrote:

I've asked infra to get LWP::Protocol::https installed on all the
buildbots and they're working on it.


Thanks for debugging, this will hopefully solve it. So indeed the issue 
is on the buildbots side but it was related to SourceForge now enforcing 
HTTPS downloads. I hope Infra will fix it soon. By the way, this is 
tracked in https://issues.apache.org/jira/browse/INFRA-11296 for reference.



We also need to update our build instructions to install it when building.


Done for Fedora here:

https://wiki.openoffice.org/w/index.php?title=Fedora_Build_Instructions=237350=230515

If someone can look up at package names for Ubuntu (and at whatever is 
needed for Windows), we can update 
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step 
too.


Regards,
  Andrea.

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

Re: Buildbots update

[Damjan Jovanovic]

Steps 1-4 first delete the "source" directory, do a fresh SVN checkout
(not update) into "source", delete the "build" directory, and copy
"source" to "build". The build is then run in "build". This was the
only robust way to get it working and fix all the errors and timeouts
that were happening earlier. I think that's confusing you here.

On linux64-nightly I've changed the buildbot script to cache downloads
across builds. In 9 builds, it hasn't helped one bit: all 14 missing
tarballs must have failed every single time.

The only thing that made a difference, getting it reduced from 15
missing tarballs to 14, is fixing the upstream URL for vigra in
main/external_deps.lst. This tells me it's access to SourceForge that
is the problem here.

In r1731307 I patched
main/solenv/bin/download_external_dependencies.pl to log the HTTP
status line when a download fails, and it finally showed what's really
wrong:

download from 
http://sourceforge.net/projects/oooextras.mirror/files/067201ea8b126597670b5eff72e1f66c-mythes-1.2.0.tar.gz
failed (501 Protocol scheme 'https' is not supported
(LWP::Protocol::https not installed))

I've asked infra to get LWP::Protocol::https installed on all the
buildbots and they're working on it.

We also need to update our build instructions to install it when building.

On Sat, Feb 20, 2016 at 12:06 AM, Kay Schenk <kay.sch...@gmail.com> wrote:
> [top posting]
>
> hmmm...maybe I've figured out the problem?
>
> using Linux-32 nightly as the example.
>
> Take a look at the PWD variable in this listing:
>
> https://ci.apache.org/builders/openoffice-linux32-nightly/builds/191/steps/configure/logs/stdio
>
> and the corresponding TARFILE_LOCATION (which is correct for the PWD
> specified) --
>
> "The variable TARFILE_LOCATION  is set to:
> /home/buildslave20/slave20/openoffice-linux32-nightly/build/ext_sources"
>
> so conceptually NO downloads from 3rd party locations should happen
> at all in normal building with the buildbots since they have the
> correct local file info for 3rd party sources. This is the case for
> our local builds as well.
>
> However, when you look at the output for the svn update for this
> same run, look at where the update dumps --
>
> PWD=/home/buildslave20/slave20/openoffice-linux32-nightly/source
>
> so, in my mind, it's not in
> /home/buildslave20/slave20/openoffice-linux32-nightly/build/
>
> where I think it should be to make the build work correctly.
>
> What do others think?
>
>
>
> On 02/17/2016 03:40 PM, Kay Schenk wrote:
>>
>> On Tue, Feb 16, 2016 at 2:47 PM, Andrea Pescetti
>> <pesce...@apache.org <mailto:pesce...@apache.org>> wrote:
>>
>> Kay Schenk wrote:
>>
>> On 02/13/2016 11:45 AM, Andrea Pescetti wrote:
>>
>> it seems that buildbots are having issues with network
>> in general
>>
>> Do we have any additional news on the download failures
>> specifically
>> from the buildbots to SourceForge downloads?
>>
>>
>> Why SourceForge? Look at
>> 
>> https://ci.apache.org/builders/openoffice-linux64-nightly/builds/243/steps/retry%20bootstrap/logs/stdio
>> to see that ALL downloads in ./bootstrap are failing; sure, most
>> of them are from SourceForge, but this is irrelevant, since
>> downloads from Mozilla and other sources are failing too.
>>
>> The problem is most likely on the buildbot side. For some
>> reason, be it a full disk or a firewall restriction, it can't
>> download stuff, and this should be checked with someone who has
>> shell access to that machine.
>>
>> The following, failed from buildbot, were OK with my test script
>>
>>
>> I confirm I've run ./boostrap without any problems too last
>> weekend. Again, the problem is on the buildbots and not elsewhere.
>>
>>
>> Regards,
>>   Andrea.
>>
>>
>> I got on HipChat a while ago and all that was suggested was we use
>> "https" instead of "http" to SourceForge. But, given that my little
>> stripped down download script worked fine without this, I doubt this
>> is it.
>> I didn't ask about filled up disk and perhaps I should have.  :(
>>
>> We COULD get around this but just using the sources already in our
>> trunk and changing the SVN call to that to just a file URL for the
>> time being, and referencing that as URL1 for these, but I guess that
>> might be considered  bad. We don't distribute these with the source
>> and we would need to remember to chang

Re: Buildbots update

[Kay Schenk]

[top posting]

hmmm...maybe I've figured out the problem?

using Linux-32 nightly as the example.

Take a look at the PWD variable in this listing:

https://ci.apache.org/builders/openoffice-linux32-nightly/builds/191/steps/configure/logs/stdio

and the corresponding TARFILE_LOCATION (which is correct for the PWD
specified) --

"The variable TARFILE_LOCATION  is set to:
/home/buildslave20/slave20/openoffice-linux32-nightly/build/ext_sources"

so conceptually NO downloads from 3rd party locations should happen
at all in normal building with the buildbots since they have the
correct local file info for 3rd party sources. This is the case for
our local builds as well.

However, when you look at the output for the svn update for this
same run, look at where the update dumps --

PWD=/home/buildslave20/slave20/openoffice-linux32-nightly/source

so, in my mind, it's not in
/home/buildslave20/slave20/openoffice-linux32-nightly/build/

where I think it should be to make the build work correctly.

What do others think?



On 02/17/2016 03:40 PM, Kay Schenk wrote:
> 
> On Tue, Feb 16, 2016 at 2:47 PM, Andrea Pescetti
> <pesce...@apache.org <mailto:pesce...@apache.org>> wrote:
> 
> Kay Schenk wrote:
> 
> On 02/13/2016 11:45 AM, Andrea Pescetti wrote:
> 
> it seems that buildbots are having issues with network
> in general
> 
> Do we have any additional news on the download failures
> specifically
> from the buildbots to SourceForge downloads?
> 
> 
> Why SourceForge? Look at
> 
> https://ci.apache.org/builders/openoffice-linux64-nightly/builds/243/steps/retry%20bootstrap/logs/stdio
> to see that ALL downloads in ./bootstrap are failing; sure, most
> of them are from SourceForge, but this is irrelevant, since
> downloads from Mozilla and other sources are failing too.
> 
> The problem is most likely on the buildbot side. For some
> reason, be it a full disk or a firewall restriction, it can't
> download stuff, and this should be checked with someone who has
> shell access to that machine.
> 
> The following, failed from buildbot, were OK with my test script
> 
> 
> I confirm I've run ./boostrap without any problems too last
> weekend. Again, the problem is on the buildbots and not elsewhere.
> 
> 
> Regards,
>   Andrea.
> 
> 
> ​I got on HipChat a while ago and all that was suggested was we use
> "https" instead of "http" to SourceForge. But, given that my little
> stripped down download script worked fine without this, I doubt this
> is it.
> I didn't ask about filled up disk and perhaps I should have.  :(
> 
> ​We COULD get around this but just using the sources already in our
> trunk and changing the SVN call to that to just a file URL for the
> time being, and referencing that as URL1 for these, but I guess that
> might be considered  bad.​ We don't distribute these with the source
> and we would need to remember to change this back for a release. But
> just a thought.
> 
> -- 
> --
> MzK
> 
> "Though no one can go back and make a brand new start,
>  anyone can start from now and make a brand new ending."
>   -- Carl Bard
>   
> 

-- 

MzK

"Though no one can go back and make a brand new start,
 anyone can start from now and make a brand new ending."
-- Carl Bard

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

Re: Buildbots update

[Kay Schenk]

On Tue, Feb 16, 2016 at 2:47 PM, Andrea Pescetti <pesce...@apache.org>
wrote:

> Kay Schenk wrote:
>
>> On 02/13/2016 11:45 AM, Andrea Pescetti wrote:
>>
>>> it seems that buildbots are having issues with network in general
>>>
>> Do we have any additional news on the download failures specifically
>> from the buildbots to SourceForge downloads?
>>
>
> Why SourceForge? Look at
>
> https://ci.apache.org/builders/openoffice-linux64-nightly/builds/243/steps/retry%20bootstrap/logs/stdio
> to see that ALL downloads in ./bootstrap are failing; sure, most of them
> are from SourceForge, but this is irrelevant, since downloads from Mozilla
> and other sources are failing too.
>
> The problem is most likely on the buildbot side. For some reason, be it a
> full disk or a firewall restriction, it can't download stuff, and this
> should be checked with someone who has shell access to that machine.
>
> The following, failed from buildbot, were OK with my test script
>>
>
> I confirm I've run ./boostrap without any problems too last weekend.
> Again, the problem is on the buildbots and not elsewhere.
>
>
> Regards,
>   Andrea.
>

​I got on HipChat a while ago and all that was suggested was we use "https"
instead of "http" to SourceForge. But, given that my little stripped down
download script worked fine without this, I doubt this is it.
I didn't ask about filled up disk and perhaps I should have.  :(

​We COULD get around this but just using the sources already in our trunk
and changing the SVN call to that to just a file URL for the time being,
and referencing that as URL1 for these, but I guess that might be
considered  bad.​ We don't distribute these with the source and we would
need to remember to change this back for a release. But just a thought.

-- 
--
MzK

"Though no one can go back and make a brand new start,
 anyone can start from now and make a brand new ending."
  -- Carl Bard