I am not sure which tests you are talking about and at what stage of the build process they occur. The Google Test unit tests don't bring up dialogs AFAIK, but can be disabled by passing --disable-unit-tests to ./configure. If this happens after starting AOO then see https://wiki.openoffice.org/wiki/Non_Product_Build - in brief Alt+Shift+Ctrl+D, set "Error" to something other than "MessageBox", "OK", exit AOO, back up the .dbgsv.ini somewhere, and from then on start AOO with the environment variable DBGSV_INIT set to the path of that .dbgsv.ini you backed up.
On Sun, Mar 13, 2016 at 4:57 PM, Patricia Shanahan <[email protected]> wrote: > I am currently building a debug version of AOO, including using > --enable-dbgutil. I lost a few hours overnight because it did a test that > triggered an assertion dialog, and waited for me to wake up and click "No" > to continue. > > I would prefer to separate building and the tests that are normally done > during "build --all", so that I can build while I am away from the computer > and test while I'm there to respond to any dialogs. > > Patricia --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
