Re: Buildbot problems
Hi Damjan, I think it now breaks at the point where the external libraries should get pulled in from: https://github.com/apache/openoffice-externals I don't know what was changed recently with our buildbots. They were running perfectly for some time after Gavin moved them to the new server... This seems to be a constant battle. Meanwhile I will do my Windows test builds as usual. Regards, Matthias Am 07.03.23 um 05:50 schrieb Damjan Jovanovic: > Unfortunately that's not our only problem. > > Even before the MozillaBuild update, every "build --all" got "cancelled" > after about 37 minutes. For example see > https://ci2.apache.org/#/builders/67/builds/628 > > Regards > Damjan > > On Sun, Mar 5, 2023 at 10:16 PM Matthias Seidel > wrote: > >> Hi Damjan, >> >> Thank you for all the work on the buildbots! >> >> Looking at the Windows bot now: >> >> checking whether to build LDAP configuration backend... checking whether to >> build the internal NSS module... yes >> configure: error: Mozilla build tooling incomplete! >> >> It seems like MozillaBuild was updated to 4.x, which we do not support yet. >> >> Regards, >> >>Matthias >> >> Am 02.03.23 um 05:46 schrieb Damjan Jovanovic: >> >> On Sun, Jan 22, 2023 at 1:33 PM Matthias Seidel >> >> wrote: >> >> >> Now regarding Awk, instead of doing: >> rm /bin/awk >> mv /bin/gawk.exe /bin/awk.exe >> can't we prepend PATH with a directory containing an "awk" script that >> >> just >> >> calls gawk.exe? >> >> It would be great if there is a better way to do it. I just followed our >> Windows building guide all these years. >> >> But this is beyond my capabilities and one of the reasons why I cannot >> maintain our buildbots anymore. >> >> >> This approach did eventually work. I eventually succeeded in creating an >> "awk" script that calls "gawk" and setting PATH to its directory within >> Cygwin, and ./configure now gets further. >> >> Now the next problem is that Cygwin doesn't have gcc and g++ >> (https://ci2.apache.org/#/builders/67/builds/516/steps/9/logs/stdio): >> >> which: no gcc in >> >> >> (/cygdrive/e/buildbot/openoffice-win10/utils:/usr/local/bin:/usr/bin:/cygdrive/e/Python39/Scripts:/cygdrive/e/Python39:/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Windows/System32/OpenSSH:/cygdrive/c/Program >> >> Files/Puppet Labs/Puppet/bin:/cygdrive/c/Program Files >> (x86)/Subversion/bin:/cygdrive/c/Program >> Files/Git/cmd:/cygdrive/e/buildbot/tools/Windows Kits/10/Windows >> Performance >> Toolkit:/cygdrive/c/Users/buildbot/AppData/Local/Microsoft/WindowsApps) >> configure: error: cygwin gcc and g++ are needed, please install them. >> >> How can we install them? >> >> That's an Infra job. ;-) >> >> >> >> Weeks ago, on the openoffice-win10 buildbot, many Cygwin dependencies >> somehow got deleted, and days of battling Buildbot and working with Infra >> on https://issues.apache.org/jira/browse/INFRA-24114 were needed to install >> them again. >> >> The git crlf problem on Cygwin was another major issue that needed fixing. >> >> Awk was another, my idea for an "awk" script that calls gawk didn't work, I >> ended up copying /usr/bin/gawk.exe to awk.exe in a directory that is then >> prepended to the PATH environment variable passed to "configure" and >> "build", which worked in my own build and should work on the buildbot too. >> Since this copies gawk on every build, this approach won't be broken by >> future Cygwin upgrades like our previous renaming of gawk to awk by Infra >> was. >> >> I also changed haltOnFailure to False for the "build" step, so that the >> logs are uploaded even when the build fails, like the Linux buildbots do. >> Haven't checked whether that works yet. >> >> It eventually got through configure and started building, but every time >> that happened, the build was cancelled somehow. >> >> Then Java 8 changed somehow (upgrade or whatever), and Java detection >> broke. That has taken several more weeks to fix, and a command I was trying >> to run to log Java's files wasn't working due to a missing bracket which I >> eventually found and fixed. >> >> A further Java problem is that oowintool fails to detect Java, as it's >> looking for the 32 bit Java registry key, while we only have a 64 bit Java >> installed. I had to dig through the buildbot script's history to find a >> working 32 bit Java directory to specify (which oowintool can't detect >> because it's just unzipped, not installed and added to the registry). >> >> With those endless problems fixed, the build is now progressing >> nicely:https://ci2.apache.org/#/builders/67/builds/625 >> >> >> Regards, >> >>Matthias >> >> >> >> Regards >> Damjan >> >> >> smime.p7s Description: S/MIME Cryptographic Signature
Re: Buildbot problems
Unfortunately that's not our only problem. Even before the MozillaBuild update, every "build --all" got "cancelled" after about 37 minutes. For example see https://ci2.apache.org/#/builders/67/builds/628 Regards Damjan On Sun, Mar 5, 2023 at 10:16 PM Matthias Seidel wrote: > Hi Damjan, > > Thank you for all the work on the buildbots! > > Looking at the Windows bot now: > > checking whether to build LDAP configuration backend... checking whether to > build the internal NSS module... yes > configure: error: Mozilla build tooling incomplete! > > It seems like MozillaBuild was updated to 4.x, which we do not support yet. > > Regards, > >Matthias > > Am 02.03.23 um 05:46 schrieb Damjan Jovanovic: > > On Sun, Jan 22, 2023 at 1:33 PM Matthias Seidel > > wrote: > > > Now regarding Awk, instead of doing: > rm /bin/awk > mv /bin/gawk.exe /bin/awk.exe > can't we prepend PATH with a directory containing an "awk" script that > > just > > calls gawk.exe? > > It would be great if there is a better way to do it. I just followed our > Windows building guide all these years. > > But this is beyond my capabilities and one of the reasons why I cannot > maintain our buildbots anymore. > > > This approach did eventually work. I eventually succeeded in creating an > "awk" script that calls "gawk" and setting PATH to its directory within > Cygwin, and ./configure now gets further. > > Now the next problem is that Cygwin doesn't have gcc and g++ > (https://ci2.apache.org/#/builders/67/builds/516/steps/9/logs/stdio): > > which: no gcc in > > > (/cygdrive/e/buildbot/openoffice-win10/utils:/usr/local/bin:/usr/bin:/cygdrive/e/Python39/Scripts:/cygdrive/e/Python39:/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Windows/System32/OpenSSH:/cygdrive/c/Program > > Files/Puppet Labs/Puppet/bin:/cygdrive/c/Program Files > (x86)/Subversion/bin:/cygdrive/c/Program > Files/Git/cmd:/cygdrive/e/buildbot/tools/Windows Kits/10/Windows > Performance > Toolkit:/cygdrive/c/Users/buildbot/AppData/Local/Microsoft/WindowsApps) > configure: error: cygwin gcc and g++ are needed, please install them. > > How can we install them? > > That's an Infra job. ;-) > > > > Weeks ago, on the openoffice-win10 buildbot, many Cygwin dependencies > somehow got deleted, and days of battling Buildbot and working with Infra > on https://issues.apache.org/jira/browse/INFRA-24114 were needed to install > them again. > > The git crlf problem on Cygwin was another major issue that needed fixing. > > Awk was another, my idea for an "awk" script that calls gawk didn't work, I > ended up copying /usr/bin/gawk.exe to awk.exe in a directory that is then > prepended to the PATH environment variable passed to "configure" and > "build", which worked in my own build and should work on the buildbot too. > Since this copies gawk on every build, this approach won't be broken by > future Cygwin upgrades like our previous renaming of gawk to awk by Infra > was. > > I also changed haltOnFailure to False for the "build" step, so that the > logs are uploaded even when the build fails, like the Linux buildbots do. > Haven't checked whether that works yet. > > It eventually got through configure and started building, but every time > that happened, the build was cancelled somehow. > > Then Java 8 changed somehow (upgrade or whatever), and Java detection > broke. That has taken several more weeks to fix, and a command I was trying > to run to log Java's files wasn't working due to a missing bracket which I > eventually found and fixed. > > A further Java problem is that oowintool fails to detect Java, as it's > looking for the 32 bit Java registry key, while we only have a 64 bit Java > installed. I had to dig through the buildbot script's history to find a > working 32 bit Java directory to specify (which oowintool can't detect > because it's just unzipped, not installed and added to the registry). > > With those endless problems fixed, the build is now progressing > nicely:https://ci2.apache.org/#/builders/67/builds/625 > > > Regards, > >Matthias > > > > Regards > Damjan > > >
Re: Buildbot problems
Hi Damjan, Thank you for all the work on the buildbots! Looking at the Windows bot now: checking whether to build LDAP configuration backend... checking whether to build the internal NSS module... yes configure: error: Mozilla build tooling incomplete! It seems like MozillaBuild was updated to 4.x, which we do not support yet. Regards, Matthias Am 02.03.23 um 05:46 schrieb Damjan Jovanovic: > On Sun, Jan 22, 2023 at 1:33 PM Matthias Seidel > wrote: > >>> > Now regarding Awk, instead of doing: > rm /bin/awk > mv /bin/gawk.exe /bin/awk.exe > can't we prepend PATH with a directory containing an "awk" script that just > calls gawk.exe? It would be great if there is a better way to do it. I just followed our Windows building guide all these years. But this is beyond my capabilities and one of the reasons why I cannot maintain our buildbots anymore. >>> This approach did eventually work. I eventually succeeded in creating an >>> "awk" script that calls "gawk" and setting PATH to its directory within >>> Cygwin, and ./configure now gets further. >>> >>> Now the next problem is that Cygwin doesn't have gcc and g++ ( >>> https://ci2.apache.org/#/builders/67/builds/516/steps/9/logs/stdio): >>> >>> which: no gcc in >>> >> (/cygdrive/e/buildbot/openoffice-win10/utils:/usr/local/bin:/usr/bin:/cygdrive/e/Python39/Scripts:/cygdrive/e/Python39:/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Windows/System32/OpenSSH:/cygdrive/c/Program >>> Files/Puppet Labs/Puppet/bin:/cygdrive/c/Program Files >>> (x86)/Subversion/bin:/cygdrive/c/Program >>> Files/Git/cmd:/cygdrive/e/buildbot/tools/Windows Kits/10/Windows >>> Performance >>> Toolkit:/cygdrive/c/Users/buildbot/AppData/Local/Microsoft/WindowsApps) >>> configure: error: cygwin gcc and g++ are needed, please install them. >>> >>> How can we install them? >> That's an Infra job. ;-) >> >> > Weeks ago, on the openoffice-win10 buildbot, many Cygwin dependencies > somehow got deleted, and days of battling Buildbot and working with Infra > on https://issues.apache.org/jira/browse/INFRA-24114 were needed to install > them again. > > The git crlf problem on Cygwin was another major issue that needed fixing. > > Awk was another, my idea for an "awk" script that calls gawk didn't work, I > ended up copying /usr/bin/gawk.exe to awk.exe in a directory that is then > prepended to the PATH environment variable passed to "configure" and > "build", which worked in my own build and should work on the buildbot too. > Since this copies gawk on every build, this approach won't be broken by > future Cygwin upgrades like our previous renaming of gawk to awk by Infra > was. > > I also changed haltOnFailure to False for the "build" step, so that the > logs are uploaded even when the build fails, like the Linux buildbots do. > Haven't checked whether that works yet. > > It eventually got through configure and started building, but every time > that happened, the build was cancelled somehow. > > Then Java 8 changed somehow (upgrade or whatever), and Java detection > broke. That has taken several more weeks to fix, and a command I was trying > to run to log Java's files wasn't working due to a missing bracket which I > eventually found and fixed. > > A further Java problem is that oowintool fails to detect Java, as it's > looking for the 32 bit Java registry key, while we only have a 64 bit Java > installed. I had to dig through the buildbot script's history to find a > working 32 bit Java directory to specify (which oowintool can't detect > because it's just unzipped, not installed and added to the registry). > > With those endless problems fixed, the build is now progressing nicely: > https://ci2.apache.org/#/builders/67/builds/625 > > > Regards, >>Matthias >> >> > Regards > Damjan > smime.p7s Description: S/MIME Cryptographic Signature
Re: Buildbot problems
On Sun, Jan 22, 2023 at 1:33 PM Matthias Seidel wrote: > > > > > > >>> Now regarding Awk, instead of doing: > >>> rm /bin/awk > >>> mv /bin/gawk.exe /bin/awk.exe > >>> can't we prepend PATH with a directory containing an "awk" script that > >> just > >>> calls gawk.exe? > >> It would be great if there is a better way to do it. I just followed our > >> Windows building guide all these years. > >> > >> But this is beyond my capabilities and one of the reasons why I cannot > >> maintain our buildbots anymore. > >> > > This approach did eventually work. I eventually succeeded in creating an > > "awk" script that calls "gawk" and setting PATH to its directory within > > Cygwin, and ./configure now gets further. > > > > Now the next problem is that Cygwin doesn't have gcc and g++ ( > > https://ci2.apache.org/#/builders/67/builds/516/steps/9/logs/stdio): > > > > which: no gcc in > > > (/cygdrive/e/buildbot/openoffice-win10/utils:/usr/local/bin:/usr/bin:/cygdrive/e/Python39/Scripts:/cygdrive/e/Python39:/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Windows/System32/OpenSSH:/cygdrive/c/Program > > Files/Puppet Labs/Puppet/bin:/cygdrive/c/Program Files > > (x86)/Subversion/bin:/cygdrive/c/Program > > Files/Git/cmd:/cygdrive/e/buildbot/tools/Windows Kits/10/Windows > > Performance > > Toolkit:/cygdrive/c/Users/buildbot/AppData/Local/Microsoft/WindowsApps) > > configure: error: cygwin gcc and g++ are needed, please install them. > > > > How can we install them? > > That's an Infra job. ;-) > > Weeks ago, on the openoffice-win10 buildbot, many Cygwin dependencies somehow got deleted, and days of battling Buildbot and working with Infra on https://issues.apache.org/jira/browse/INFRA-24114 were needed to install them again. The git crlf problem on Cygwin was another major issue that needed fixing. Awk was another, my idea for an "awk" script that calls gawk didn't work, I ended up copying /usr/bin/gawk.exe to awk.exe in a directory that is then prepended to the PATH environment variable passed to "configure" and "build", which worked in my own build and should work on the buildbot too. Since this copies gawk on every build, this approach won't be broken by future Cygwin upgrades like our previous renaming of gawk to awk by Infra was. I also changed haltOnFailure to False for the "build" step, so that the logs are uploaded even when the build fails, like the Linux buildbots do. Haven't checked whether that works yet. It eventually got through configure and started building, but every time that happened, the build was cancelled somehow. Then Java 8 changed somehow (upgrade or whatever), and Java detection broke. That has taken several more weeks to fix, and a command I was trying to run to log Java's files wasn't working due to a missing bracket which I eventually found and fixed. A further Java problem is that oowintool fails to detect Java, as it's looking for the 32 bit Java registry key, while we only have a 64 bit Java installed. I had to dig through the buildbot script's history to find a working 32 bit Java directory to specify (which oowintool can't detect because it's just unzipped, not installed and added to the registry). With those endless problems fixed, the build is now progressing nicely: https://ci2.apache.org/#/builders/67/builds/625 Regards, > >Matthias > > Regards Damjan
Re: Buildbot problems
Hi Damjan, Am 22.01.23 um 11:53 schrieb Damjan Jovanovic: > On Wed, Jan 18, 2023 at 8:26 PM Matthias Seidel > wrote: > >> Hi, >> >> Am 16.01.23 um 03:47 schrieb Damjan Jovanovic: >>> Hi >>> >>> That's progress, because if you compare it to the previous build's >>> ./configure: >>> https://ci2.apache.org/#/builders/67/builds/509/steps/8/logs/stdio >>> it no longer stops on the error: >>> "configure: error: cannot run /bin/sh ./config.sub", >>> we got further to reach the awk error. >>> >>> So the automatic changing of line endings by git really was a problem, >> and: >>> git clone -c core.autocrlf=false ... >>> really did fix it :-). >> Yes, it looks better! >> >> Is this a native Windows git or the one inside Cygwin? >> > It's called from within Cygwin, but it could be the Windows one, I am not > sure. It could explain the problems with CRLF. On the "old" buildbots we definitely used the git from Cygwin. But then, even on the new machine it definitely did build (before the Cygwin update without changing awk/gawk). > > >>> Now regarding Awk, instead of doing: >>> rm /bin/awk >>> mv /bin/gawk.exe /bin/awk.exe >>> can't we prepend PATH with a directory containing an "awk" script that >> just >>> calls gawk.exe? >> It would be great if there is a better way to do it. I just followed our >> Windows building guide all these years. >> >> But this is beyond my capabilities and one of the reasons why I cannot >> maintain our buildbots anymore. >> > This approach did eventually work. I eventually succeeded in creating an > "awk" script that calls "gawk" and setting PATH to its directory within > Cygwin, and ./configure now gets further. > > Now the next problem is that Cygwin doesn't have gcc and g++ ( > https://ci2.apache.org/#/builders/67/builds/516/steps/9/logs/stdio): > > which: no gcc in > (/cygdrive/e/buildbot/openoffice-win10/utils:/usr/local/bin:/usr/bin:/cygdrive/e/Python39/Scripts:/cygdrive/e/Python39:/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Windows/System32/OpenSSH:/cygdrive/c/Program > Files/Puppet Labs/Puppet/bin:/cygdrive/c/Program Files > (x86)/Subversion/bin:/cygdrive/c/Program > Files/Git/cmd:/cygdrive/e/buildbot/tools/Windows Kits/10/Windows > Performance > Toolkit:/cygdrive/c/Users/buildbot/AppData/Local/Microsoft/WindowsApps) > configure: error: cygwin gcc and g++ are needed, please install them. > > How can we install them? That's an Infra job. ;-) Regards, Matthias > > >> Regards, >> >>Matthias >> >> > Regards > Damjan > smime.p7s Description: S/MIME Cryptographic Signature
Re: Buildbot problems
On Wed, Jan 18, 2023 at 8:26 PM Matthias Seidel wrote: > Hi, > > Am 16.01.23 um 03:47 schrieb Damjan Jovanovic: > > Hi > > > > That's progress, because if you compare it to the previous build's > > ./configure: > > https://ci2.apache.org/#/builders/67/builds/509/steps/8/logs/stdio > > it no longer stops on the error: > > "configure: error: cannot run /bin/sh ./config.sub", > > we got further to reach the awk error. > > > > So the automatic changing of line endings by git really was a problem, > and: > > git clone -c core.autocrlf=false ... > > really did fix it :-). > > Yes, it looks better! > > Is this a native Windows git or the one inside Cygwin? > It's called from within Cygwin, but it could be the Windows one, I am not sure. > > > > > Now regarding Awk, instead of doing: > > rm /bin/awk > > mv /bin/gawk.exe /bin/awk.exe > > can't we prepend PATH with a directory containing an "awk" script that > just > > calls gawk.exe? > > It would be great if there is a better way to do it. I just followed our > Windows building guide all these years. > > But this is beyond my capabilities and one of the reasons why I cannot > maintain our buildbots anymore. > This approach did eventually work. I eventually succeeded in creating an "awk" script that calls "gawk" and setting PATH to its directory within Cygwin, and ./configure now gets further. Now the next problem is that Cygwin doesn't have gcc and g++ ( https://ci2.apache.org/#/builders/67/builds/516/steps/9/logs/stdio): which: no gcc in (/cygdrive/e/buildbot/openoffice-win10/utils:/usr/local/bin:/usr/bin:/cygdrive/e/Python39/Scripts:/cygdrive/e/Python39:/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Windows/System32/OpenSSH:/cygdrive/c/Program Files/Puppet Labs/Puppet/bin:/cygdrive/c/Program Files (x86)/Subversion/bin:/cygdrive/c/Program Files/Git/cmd:/cygdrive/e/buildbot/tools/Windows Kits/10/Windows Performance Toolkit:/cygdrive/c/Users/buildbot/AppData/Local/Microsoft/WindowsApps) configure: error: cygwin gcc and g++ are needed, please install them. How can we install them? > Regards, > >Matthias > > Regards Damjan
Re: Buildbot problems
Hi, Am 16.01.23 um 03:47 schrieb Damjan Jovanovic: > Hi > > That's progress, because if you compare it to the previous build's > ./configure: > https://ci2.apache.org/#/builders/67/builds/509/steps/8/logs/stdio > it no longer stops on the error: > "configure: error: cannot run /bin/sh ./config.sub", > we got further to reach the awk error. > > So the automatic changing of line endings by git really was a problem, and: > git clone -c core.autocrlf=false ... > really did fix it :-). Yes, it looks better! Is this a native Windows git or the one inside Cygwin? > > Now regarding Awk, instead of doing: > rm /bin/awk > mv /bin/gawk.exe /bin/awk.exe > can't we prepend PATH with a directory containing an "awk" script that just > calls gawk.exe? It would be great if there is a better way to do it. I just followed our Windows building guide all these years. But this is beyond my capabilities and one of the reasons why I cannot maintain our buildbots anymore. Regards, Matthias > > Regards > Damjan > > On Mon, Jan 16, 2023 at 12:54 AM Matthias Seidel > wrote: > >> Hi all, >> >> Looking at: >> >> https://ci2.apache.org/#/builders/67/builds/510/steps/8/logs/stdio >> >> the problem is definitely awk/gawk. >> >> Cygwin is at 3.3.3 and could be updated to 3.4.3. But remember to >> downgrade make then... >> >> Regards, >> >>Matthias >> >> Am 15.01.23 um 12:25 schrieb Matthias Seidel: >>> Hi Damjan, Peter, >>> >>> Am 15.01.23 um 09:58 schrieb Damjan Jovanovic: On Sun, Jan 15, 2023 at 10:11 AM Peter Kovacs wrote: > Am 15.01.23 um 07:12 schrieb Damjan Jovanovic: >> Hi >> >> I am trying to get all the buildbots working again, but there are many >> problems... >> >> 1. All the Windows buildbots are failing in "./configure" with: >> configure: error: cannot run /bin/sh ./config.sub >> >> This could be due to \r\n line endings or a BOM on main/config.sub, >> but >> I've checked and it uses neither in Git, so I have no idea what's >> wrong. >> How do we retrieve config.log from the buildbot? > maybe autoconf is missing? the win bots will fail anyways because of > wrong awk. > > autoconf is there. I've now added "-c core.autocrlf=false" to "git clone" for the nightly build, in case git is converting line endings during checkout. Let's >> hope it works. >>> I don't think that this is necessary, the buildbots did work before with >>> the old configuration. >>> >>> But every time gawk/awk is updated in Cygwin we need to run manual steps >>> inside Cygwin: >>> >>> rm /bin/awk >>> mv /bin/gawk.exe /bin/awk.exe >>> >>> (I hope I got it right, the instructions in Wiki were wrong before) >>> >>> This can be done by Infra. >>> >>> I already did the changes for Cygwin64, so Cygwin32 can now be removed >>> from the machine. >>> >> 2. Git-based projects are supposed to use >> https://github.com/apache/infrastructure-bb2 instead of the SVN-based >> https://svn.apache.org/repos/infra/infrastructure/buildbot2 that we >> use. >> They're different repositories, not different links to the same >>> Gavin wanted to move our config location at some time. There are still >>> other projects in SVN, though. >>> >>> Regards, >>> >>>Matthias >>> > repository. > > I have updated the links in build column. > Thank you :). >> 3. The "puppet" links on >> https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info >> are >> dead. In the table on that page, all the "Build", "Host VM", and >> "Logs" >> links are dead. >> >> It turns out that for "Logs", the link should be, for instance: >> https://nightlies.apache.org/openoffice/buildlogs/linux64*/log/log/* >> unxlngx6.pro.build.html >> instead of: >> https://nightlies.apache.org/openoffice/buildlogs/linux64*/log/* >> unxlngx6.pro.build.html >> probably because the buildbot's openoffice.py file does: >> 'mkdir' , '-p' , 'log/logarch/log' >> 'cp -fv log/*.html log/logarch/log' >> mkdir -p buildlogs/linux64/log && cp -rp log/logarch/* > buildlogs/linux64/log >> so that's why we end up with the .../log/log/... in the path. >> Ideas? > no idea. >> 4. On https://wiki.openoffice.org/wiki/Buildbot, the "Buildbot >> Configuration File" link was dead, but I was able to fix it to use the > new >> link. The link to the "overview" probably goes to the wrong page > (shouldn't >> it be the "Waterfall View" page on ci2.apache.org?). >> >> 5. On https://nightlies.apache.org/openoffice/ all the "Build Logs" > links >> are dead. Many/all of the SDK links are dead. > I am not sure but i think the sdks were deactivated. > > we can add them anytime if needed. > > We need SDKs to build the test/ directory, though I am working towards changing that. Thank you Damjan >> smime.p7s Description: S/MIME
Re: Buildbot problems
Hi That's progress, because if you compare it to the previous build's ./configure: https://ci2.apache.org/#/builders/67/builds/509/steps/8/logs/stdio it no longer stops on the error: "configure: error: cannot run /bin/sh ./config.sub", we got further to reach the awk error. So the automatic changing of line endings by git really was a problem, and: git clone -c core.autocrlf=false ... really did fix it :-). Now regarding Awk, instead of doing: rm /bin/awk mv /bin/gawk.exe /bin/awk.exe can't we prepend PATH with a directory containing an "awk" script that just calls gawk.exe? Regards Damjan On Mon, Jan 16, 2023 at 12:54 AM Matthias Seidel wrote: > Hi all, > > Looking at: > > https://ci2.apache.org/#/builders/67/builds/510/steps/8/logs/stdio > > the problem is definitely awk/gawk. > > Cygwin is at 3.3.3 and could be updated to 3.4.3. But remember to > downgrade make then... > > Regards, > >Matthias > > Am 15.01.23 um 12:25 schrieb Matthias Seidel: > > Hi Damjan, Peter, > > > > Am 15.01.23 um 09:58 schrieb Damjan Jovanovic: > >> On Sun, Jan 15, 2023 at 10:11 AM Peter Kovacs wrote: > >> > >>> Am 15.01.23 um 07:12 schrieb Damjan Jovanovic: > Hi > > I am trying to get all the buildbots working again, but there are many > problems... > > 1. All the Windows buildbots are failing in "./configure" with: > configure: error: cannot run /bin/sh ./config.sub > > This could be due to \r\n line endings or a BOM on main/config.sub, > but > I've checked and it uses neither in Git, so I have no idea what's > wrong. > How do we retrieve config.log from the buildbot? > >>> maybe autoconf is missing? the win bots will fail anyways because of > >>> wrong awk. > >>> > >>> > >> autoconf is there. > >> > >> I've now added "-c core.autocrlf=false" to "git clone" for the nightly > >> build, in case git is converting line endings during checkout. Let's > hope > >> it works. > > I don't think that this is necessary, the buildbots did work before with > > the old configuration. > > > > But every time gawk/awk is updated in Cygwin we need to run manual steps > > inside Cygwin: > > > > rm /bin/awk > > mv /bin/gawk.exe /bin/awk.exe > > > > (I hope I got it right, the instructions in Wiki were wrong before) > > > > This can be done by Infra. > > > > I already did the changes for Cygwin64, so Cygwin32 can now be removed > > from the machine. > > > >> > 2. Git-based projects are supposed to use > https://github.com/apache/infrastructure-bb2 instead of the SVN-based > https://svn.apache.org/repos/infra/infrastructure/buildbot2 that we > use. > They're different repositories, not different links to the same > > Gavin wanted to move our config location at some time. There are still > > other projects in SVN, though. > > > > Regards, > > > >Matthias > > > >>> repository. > >>> > >>> I have updated the links in build column. > >>> > >> Thank you :). > >> > >> > 3. The "puppet" links on > https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info > are > dead. In the table on that page, all the "Build", "Host VM", and > "Logs" > links are dead. > > It turns out that for "Logs", the link should be, for instance: > https://nightlies.apache.org/openoffice/buildlogs/linux64*/log/log/* > unxlngx6.pro.build.html > instead of: > https://nightlies.apache.org/openoffice/buildlogs/linux64*/log/* > unxlngx6.pro.build.html > probably because the buildbot's openoffice.py file does: > 'mkdir' , '-p' , 'log/logarch/log' > 'cp -fv log/*.html log/logarch/log' > mkdir -p buildlogs/linux64/log && cp -rp log/logarch/* > >>> buildlogs/linux64/log > so that's why we end up with the .../log/log/... in the path. > Ideas? > >>> no idea. > 4. On https://wiki.openoffice.org/wiki/Buildbot, the "Buildbot > Configuration File" link was dead, but I was able to fix it to use the > >>> new > link. The link to the "overview" probably goes to the wrong page > >>> (shouldn't > it be the "Waterfall View" page on ci2.apache.org?). > > 5. On https://nightlies.apache.org/openoffice/ all the "Build Logs" > >>> links > are dead. Many/all of the SDK links are dead. > >>> I am not sure but i think the sdks were deactivated. > >>> > >>> we can add them anytime if needed. > >>> > >>> > >> We need SDKs to build the test/ directory, though I am working towards > >> changing that. > >> > >> Thank you > >> Damjan > >> > >
Re: Buildbot problems
Hi all, Looking at: https://ci2.apache.org/#/builders/67/builds/510/steps/8/logs/stdio the problem is definitely awk/gawk. Cygwin is at 3.3.3 and could be updated to 3.4.3. But remember to downgrade make then... Regards, Matthias Am 15.01.23 um 12:25 schrieb Matthias Seidel: > Hi Damjan, Peter, > > Am 15.01.23 um 09:58 schrieb Damjan Jovanovic: >> On Sun, Jan 15, 2023 at 10:11 AM Peter Kovacs wrote: >> >>> Am 15.01.23 um 07:12 schrieb Damjan Jovanovic: Hi I am trying to get all the buildbots working again, but there are many problems... 1. All the Windows buildbots are failing in "./configure" with: configure: error: cannot run /bin/sh ./config.sub This could be due to \r\n line endings or a BOM on main/config.sub, but I've checked and it uses neither in Git, so I have no idea what's wrong. How do we retrieve config.log from the buildbot? >>> maybe autoconf is missing? the win bots will fail anyways because of >>> wrong awk. >>> >>> >> autoconf is there. >> >> I've now added "-c core.autocrlf=false" to "git clone" for the nightly >> build, in case git is converting line endings during checkout. Let's hope >> it works. > I don't think that this is necessary, the buildbots did work before with > the old configuration. > > But every time gawk/awk is updated in Cygwin we need to run manual steps > inside Cygwin: > > rm /bin/awk > mv /bin/gawk.exe /bin/awk.exe > > (I hope I got it right, the instructions in Wiki were wrong before) > > This can be done by Infra. > > I already did the changes for Cygwin64, so Cygwin32 can now be removed > from the machine. > >> 2. Git-based projects are supposed to use https://github.com/apache/infrastructure-bb2 instead of the SVN-based https://svn.apache.org/repos/infra/infrastructure/buildbot2 that we use. They're different repositories, not different links to the same > Gavin wanted to move our config location at some time. There are still > other projects in SVN, though. > > Regards, > > Matthias > >>> repository. >>> >>> I have updated the links in build column. >>> >> Thank you :). >> >> 3. The "puppet" links on https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info are dead. In the table on that page, all the "Build", "Host VM", and "Logs" links are dead. It turns out that for "Logs", the link should be, for instance: https://nightlies.apache.org/openoffice/buildlogs/linux64*/log/log/* unxlngx6.pro.build.html instead of: https://nightlies.apache.org/openoffice/buildlogs/linux64*/log/* unxlngx6.pro.build.html probably because the buildbot's openoffice.py file does: 'mkdir' , '-p' , 'log/logarch/log' 'cp -fv log/*.html log/logarch/log' mkdir -p buildlogs/linux64/log && cp -rp log/logarch/* >>> buildlogs/linux64/log so that's why we end up with the .../log/log/... in the path. Ideas? >>> no idea. 4. On https://wiki.openoffice.org/wiki/Buildbot, the "Buildbot Configuration File" link was dead, but I was able to fix it to use the >>> new link. The link to the "overview" probably goes to the wrong page >>> (shouldn't it be the "Waterfall View" page on ci2.apache.org?). 5. On https://nightlies.apache.org/openoffice/ all the "Build Logs" >>> links are dead. Many/all of the SDK links are dead. >>> I am not sure but i think the sdks were deactivated. >>> >>> we can add them anytime if needed. >>> >>> >> We need SDKs to build the test/ directory, though I am working towards >> changing that. >> >> Thank you >> Damjan >> smime.p7s Description: S/MIME Cryptographic Signature
Re: Buildbot problems
Hi Damjan, Peter, Am 15.01.23 um 09:58 schrieb Damjan Jovanovic: > On Sun, Jan 15, 2023 at 10:11 AM Peter Kovacs wrote: > >> Am 15.01.23 um 07:12 schrieb Damjan Jovanovic: >>> Hi >>> >>> I am trying to get all the buildbots working again, but there are many >>> problems... >>> >>> 1. All the Windows buildbots are failing in "./configure" with: >>> configure: error: cannot run /bin/sh ./config.sub >>> >>> This could be due to \r\n line endings or a BOM on main/config.sub, but >>> I've checked and it uses neither in Git, so I have no idea what's wrong. >>> How do we retrieve config.log from the buildbot? >> maybe autoconf is missing? the win bots will fail anyways because of >> wrong awk. >> >> > autoconf is there. > > I've now added "-c core.autocrlf=false" to "git clone" for the nightly > build, in case git is converting line endings during checkout. Let's hope > it works. I don't think that this is necessary, the buildbots did work before with the old configuration. But every time gawk/awk is updated in Cygwin we need to run manual steps inside Cygwin: rm /bin/awk mv /bin/gawk.exe /bin/awk.exe (I hope I got it right, the instructions in Wiki were wrong before) This can be done by Infra. I already did the changes for Cygwin64, so Cygwin32 can now be removed from the machine. > > >>> 2. Git-based projects are supposed to use >>> https://github.com/apache/infrastructure-bb2 instead of the SVN-based >>> https://svn.apache.org/repos/infra/infrastructure/buildbot2 that we use. >>> They're different repositories, not different links to the same Gavin wanted to move our config location at some time. There are still other projects in SVN, though. Regards, Matthias >> repository. >> >> I have updated the links in build column. >> > Thank you :). > > >>> 3. The "puppet" links on >>> https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info are >>> dead. In the table on that page, all the "Build", "Host VM", and "Logs" >>> links are dead. >>> >>> It turns out that for "Logs", the link should be, for instance: >>> https://nightlies.apache.org/openoffice/buildlogs/linux64*/log/log/* >>> unxlngx6.pro.build.html >>> instead of: >>> https://nightlies.apache.org/openoffice/buildlogs/linux64*/log/* >>> unxlngx6.pro.build.html >>> probably because the buildbot's openoffice.py file does: >>> 'mkdir' , '-p' , 'log/logarch/log' >>> 'cp -fv log/*.html log/logarch/log' >>> mkdir -p buildlogs/linux64/log && cp -rp log/logarch/* >> buildlogs/linux64/log >>> so that's why we end up with the .../log/log/... in the path. >>> Ideas? >> no idea. >>> 4. On https://wiki.openoffice.org/wiki/Buildbot, the "Buildbot >>> Configuration File" link was dead, but I was able to fix it to use the >> new >>> link. The link to the "overview" probably goes to the wrong page >> (shouldn't >>> it be the "Waterfall View" page on ci2.apache.org?). >>> >>> 5. On https://nightlies.apache.org/openoffice/ all the "Build Logs" >> links >>> are dead. Many/all of the SDK links are dead. >> I am not sure but i think the sdks were deactivated. >> >> we can add them anytime if needed. >> >> > We need SDKs to build the test/ directory, though I am working towards > changing that. > > Thank you > Damjan > smime.p7s Description: S/MIME Cryptographic Signature
Re: Buildbot problems
On Sun, Jan 15, 2023 at 10:11 AM Peter Kovacs wrote: > > Am 15.01.23 um 07:12 schrieb Damjan Jovanovic: > > Hi > > > > I am trying to get all the buildbots working again, but there are many > > problems... > > > > 1. All the Windows buildbots are failing in "./configure" with: > > configure: error: cannot run /bin/sh ./config.sub > > > > This could be due to \r\n line endings or a BOM on main/config.sub, but > > I've checked and it uses neither in Git, so I have no idea what's wrong. > > How do we retrieve config.log from the buildbot? > > maybe autoconf is missing? the win bots will fail anyways because of > wrong awk. > > autoconf is there. I've now added "-c core.autocrlf=false" to "git clone" for the nightly build, in case git is converting line endings during checkout. Let's hope it works. > > > > 2. Git-based projects are supposed to use > > https://github.com/apache/infrastructure-bb2 instead of the SVN-based > > https://svn.apache.org/repos/infra/infrastructure/buildbot2 that we use. > > They're different repositories, not different links to the same > repository. > > I have updated the links in build column. > Thank you :). > > > 3. The "puppet" links on > > https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info are > > dead. In the table on that page, all the "Build", "Host VM", and "Logs" > > links are dead. > > > > It turns out that for "Logs", the link should be, for instance: > > https://nightlies.apache.org/openoffice/buildlogs/linux64*/log/log/* > > unxlngx6.pro.build.html > > instead of: > > https://nightlies.apache.org/openoffice/buildlogs/linux64*/log/* > > unxlngx6.pro.build.html > > probably because the buildbot's openoffice.py file does: > > 'mkdir' , '-p' , 'log/logarch/log' > > 'cp -fv log/*.html log/logarch/log' > > mkdir -p buildlogs/linux64/log && cp -rp log/logarch/* > buildlogs/linux64/log > > so that's why we end up with the .../log/log/... in the path. > > Ideas? > no idea. > > > > 4. On https://wiki.openoffice.org/wiki/Buildbot, the "Buildbot > > Configuration File" link was dead, but I was able to fix it to use the > new > > link. The link to the "overview" probably goes to the wrong page > (shouldn't > > it be the "Waterfall View" page on ci2.apache.org?). > > > > 5. On https://nightlies.apache.org/openoffice/ all the "Build Logs" > links > > are dead. Many/all of the SDK links are dead. > > I am not sure but i think the sdks were deactivated. > > we can add them anytime if needed. > > We need SDKs to build the test/ directory, though I am working towards changing that. Thank you Damjan
Re: Buildbot problems
Am 15.01.23 um 07:12 schrieb Damjan Jovanovic: Hi I am trying to get all the buildbots working again, but there are many problems... 1. All the Windows buildbots are failing in "./configure" with: configure: error: cannot run /bin/sh ./config.sub This could be due to \r\n line endings or a BOM on main/config.sub, but I've checked and it uses neither in Git, so I have no idea what's wrong. How do we retrieve config.log from the buildbot? maybe autoconf is missing? the win bots will fail anyways because of wrong awk. 2. Git-based projects are supposed to use https://github.com/apache/infrastructure-bb2 instead of the SVN-based https://svn.apache.org/repos/infra/infrastructure/buildbot2 that we use. They're different repositories, not different links to the same repository. I have updated the links in build column. 3. The "puppet" links on https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info are dead. In the table on that page, all the "Build", "Host VM", and "Logs" links are dead. It turns out that for "Logs", the link should be, for instance: https://nightlies.apache.org/openoffice/buildlogs/linux64*/log/log/* unxlngx6.pro.build.html instead of: https://nightlies.apache.org/openoffice/buildlogs/linux64*/log/* unxlngx6.pro.build.html probably because the buildbot's openoffice.py file does: 'mkdir' , '-p' , 'log/logarch/log' 'cp -fv log/*.html log/logarch/log' mkdir -p buildlogs/linux64/log && cp -rp log/logarch/* buildlogs/linux64/log so that's why we end up with the .../log/log/... in the path. Ideas? no idea. 4. On https://wiki.openoffice.org/wiki/Buildbot, the "Buildbot Configuration File" link was dead, but I was able to fix it to use the new link. The link to the "overview" probably goes to the wrong page (shouldn't it be the "Waterfall View" page on ci2.apache.org?). 5. On https://nightlies.apache.org/openoffice/ all the "Build Logs" links are dead. Many/all of the SDK links are dead. I am not sure but i think the sdks were deactivated. we can add them anytime if needed. Please help? Thank you Damjan - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Buildbot problems
Hi I am trying to get all the buildbots working again, but there are many problems... 1. All the Windows buildbots are failing in "./configure" with: configure: error: cannot run /bin/sh ./config.sub This could be due to \r\n line endings or a BOM on main/config.sub, but I've checked and it uses neither in Git, so I have no idea what's wrong. How do we retrieve config.log from the buildbot? 2. Git-based projects are supposed to use https://github.com/apache/infrastructure-bb2 instead of the SVN-based https://svn.apache.org/repos/infra/infrastructure/buildbot2 that we use. They're different repositories, not different links to the same repository. 3. The "puppet" links on https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info are dead. In the table on that page, all the "Build", "Host VM", and "Logs" links are dead. It turns out that for "Logs", the link should be, for instance: https://nightlies.apache.org/openoffice/buildlogs/linux64*/log/log/* unxlngx6.pro.build.html instead of: https://nightlies.apache.org/openoffice/buildlogs/linux64*/log/* unxlngx6.pro.build.html probably because the buildbot's openoffice.py file does: 'mkdir' , '-p' , 'log/logarch/log' 'cp -fv log/*.html log/logarch/log' mkdir -p buildlogs/linux64/log && cp -rp log/logarch/* buildlogs/linux64/log so that's why we end up with the .../log/log/... in the path. Ideas? 4. On https://wiki.openoffice.org/wiki/Buildbot, the "Buildbot Configuration File" link was dead, but I was able to fix it to use the new link. The link to the "overview" probably goes to the wrong page (shouldn't it be the "Waterfall View" page on ci2.apache.org?). 5. On https://nightlies.apache.org/openoffice/ all the "Build Logs" links are dead. Many/all of the SDK links are dead. Please help? Thank you Damjan
Help needed from Windows builders on buildbot problems
I am not a Windows builder. I am looking at the overview logs from the nightly Windows buildbot from here: https://ci.apache.org/builders/aoo-win7 I know we have a problem with apr and possibly elsewhere but if you click the links on builds #70 and #71 in the configure steps, right now I am concerned about the error on build #71 concerning perl not found when it never appeared before. If you are building on Windows 7, are you having this same problem now? If not, can you help troubleshoot the configure step for build #71? Thanks. -- MzK “The journey of a thousand miles begins with a single step.” --Lao Tzu - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
