Now that the aoo-win7 buildbot is running and still failing (with an exception), I have two kinds of observations.
A. The Exception and Failure itself. See <https://ci.apache.org/builders/aoo-win7/builds/105> and the bootstrap exception information from stdio, err.txt, and err.html). 1. The buildbot is killing a Cygwin bash ./bootstrap operation after a failure for there to be output after 1200 seconds. This may or may not have something to do with whether the bash that is run can't find an output terminal or not [;<). 2. The attempt to kill the job runs into an exception handling problem in a python utility. 3. ASIDE: This is not likely to be related but it is a concern. Cygwin (as does MSYS2) treats the Windows environment as case-sensitive. Indeed, there can be duplicate named entries that differ only in case (namely, TEMP, temp, TMP, and tmp). Unfortunately, Windows utilities access the environment as if it is case-insensitive. This can lead to problems when executing the Windows VC++ command-line compiler, cl.exe, and the other tools that are run beneath a cl.exe call. I have no reason to suspect this as related to the problem we are seeing. It does remind me that using cygwin to cross-execute in the Microsoft developer tool chain is fragile. B. The RISK Warning Sign. This is a risk topic not because of the specifics (A) but with regard to availability of capacity and capability to trouble-shoot this within the AOO developer community. Silence on this with respect to the buildbot operation is worrisome. The apparent lack needs to be assessed and confirmed somehow. (Speaking for myself, I have neither capacity nor capability, although I am ever hopeful about finding ways to develop more expertise at carrying out Windows builds and perhaps then being able to understand the buildbot situation.) - Dennis > -----Original Message----- > From: Kay Schenk [mailto:kay.sch...@gmail.com] > Sent: Sunday, December 6, 2015 10:21 > To: dev@openoffice.apache.org > Subject: Re: [RISK?] FW: Daily/Nightly builds for Windows? > > > > On 12/04/2015 09:55 AM, Kay Schenk wrote: > > > > > > On 12/04/2015 08:27 AM, Dennis E. Hamilton wrote: > >> [BCC PMC and QA Lists. This is a serious topic for dev@ community > >> discussion.] > >> > >> Can we have some visibility on this, please? > >> > >> The last aoo-win7 ASF Buildbot success was on 2015-07-28. > >> Thereafter, the Buildbot reported exceptions until 2015-10-03. > >> There have been no reports at all from that Buildbot since. > >> > >> For 4.1.2, the only current builds were the Release Candidates. > >> This left very little time for QA testing, with each new RC > >> required retesting to some degree. Those were very short > >> windows. > >> > >> This also means that the only way to verify anything about > >> Windows functions by developers, QA, and anyone else is to have > >> the personal means and the computer capacity to do development > >> builds, matching the build parameters and other dependencies used > >> for release builds. Isn't that too select and narrow for the > >> attention that is required? > >> > >> This seems to be at least a quality risk. > >> > >> There is also a question of exactly what the present capability > >> and capacity is in contrast to what is required to support > >> continuous integration of Windows builds. > >> > >> - Dennis > > > > I recently modified the buildbot instructions for Linux-32 which > > worked one time and now also seems to be non-functioning. I haven't > > had time to check on this yet. > > Correction to my statement on the Linux-32 nightly buildbot. It is > running successfully nightly but we aren't getting notices on it any > more. I will ask infra about this. > > > > > As far as the windows buildbot. Some suggestions/approaches. > > > > * take a look at the output from the last build: > > > > > https://ci.apache.org/projects/openoffice/buildlogs/win/log/wntmsci12.pr > o.build.html > > > > I submitted a Jira issue on this a while back. I don't know if the > > issue lies in our build scripts for Windows or something else. > > > > ref: https://issues.apache.org/jira/browse/INFRA-10481 > > > > * take a look at the buildbot setup for Windows (committers only): > > > > > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildma > ster/master1/projects/openofficeorg.conf > > > > Does the configuration for Windows need to be changed in some way? > > > > We can fix buildbot configurations but not resource problems with > > the buildbots. > > > > > >> > >> > >>> -----Original Message----- From: Pedro Lino > >>> [mailto:pedl...@gmail.com] Sent: Friday, December 4, 2015 > >>> 03:58 To: q...@openoffice.apache.org Subject: Daily/Nightly > >>> builds for Windows? > >>> > >>> Hi all > >>> > >>> Now that 4.1.2 is out and development is again active, I > >>> believe it would be good to have the Apache OpenOffice > >>> buildbots releasing daily binaries for Windows as well? > >>> > >>> This has been broken long before the 4.1.2 RC stage but maybe > >>> now someone could give some love to the buildbot? > >>> > >>> With nearly 1 million downloads per day for the Windows > >>> platform alone, I believe that it would make sense to make sure > >>> that AOO is improved and that any regressions are detected > >>> early. > >>> > >>> Best regards, Pedro > >> > >> > >> --------------------------------------------------------------------- > >> > >> > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >> For additional commands, e-mail: dev-h...@openoffice.apache.org > >> > > > > -- > -------------------------------------------- > MzK > > "Somebody's gotta win, somebody's gotta lose. > Just don't fight about it. > Just try to get better." > -- Yogi Berra > > > > > --------------------------------------------------------------------- > 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
