[Libreoffice-qa] QA work with Windows Tinderbox builds -- need help

[V Stuart Foote]

Roman, David

Thank you both!  Roman's steps make perfect sense, although I was scratching
my head about the "b3a49f990273c9fa6e2b90245c271a14b38280f0"  ID, before I
realized it was the commit ID for the patcth to 3.6 and that the cgit
interface allows a toggle between Master and 3.6

Anyhow,  turns out to be simple to follow along once you know the module
stanza of the daily build log contains ID of the last commit from each of
the modules (e.g. for 3.6:  core, binfilter, dictionaries, help,
translations) and then reviewing the log for position of the commit being
verified.

No trouble navigating with cgit.  But will need to work with git on a Linux
box, and at some point I'll have to try loading a git client for Windows and
pulling the repository since I spend about 90% or my time in Windows. 

Unfortunately, while this confirms the patch was applied, it also means the
patch does not correct the issues with Java Accessibility - JAB interface to
LibO UNO accessibility where the LOdev 3.6 daily remains mute in javaferret
and javamonkey  test utilities as well as the NVDA screen reader.

Stuart



--
View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-QA-work-with-Windows-Tinderbox-builds-need-help-tp4013785p4015145.html
Sent from the QA mailing list archive at Nabble.com.