Hi, I tried the test locally with 92f880f952a2433dd313c6f8dbfaa717a40b6886 and it seems to work for me.
Sometimes tests can fail if you don’t have the same configure options as Jenkins. Perhaps you could send your autogen.input file to compare? Otherwise it might be a good idea to install gdb on your system so that the error message will give a backtrace. That might lead to some helpful information about why it is failing. Regards, – Neil apurvrajput <[email protected]> writes: > Hello, > I am facing an error with CppunitTest_dbaccess_CRMDatabase_test, on a clean > master checkout. My changes are stashed, and this test fails reproducibly. > > Is this a known failure, or an environment issue on my end? I've forwarded > the email displaying the error message. > > Best, > Apurv Rajput. > > Sent with [Proton Mail](https://proton.me/mail/home) secure email. > > ------- Forwarded Message ------- > From: apurvrajput <[email protected]> > Date: On Wednesday, August 19th, 2026 at 2:55 PM > Subject: Doubt about procedure when master is broken > To: Ilmari Lauhakangas <[email protected]> > >> Hi, >> >> I was working on a bug when a few unexpected tests failed. Checked on >> master, and the same tests are failing. Should I still be submitting my >> patch, or wait till master is broken? The error messages are as below : >> >>>>[CUT] dbaccess_embeddeddb_performancetest >>> Running as unit: >>> -home-apu-projects\x2dand\x2dcode-libreoffice\x2dcode-libreoffice-workdir-CppunitTest-dbaccess_CRMDatabase_test.test:20260819090917:548678.scope; >>> invocation ID: 7ea0bc647d80435d80f82ef9935dea18 >>> terminate called after throwing an instance of >>> 'com::sun::star::uno::DeploymentException' >>> You need gdb in your path to show backtraces >>> >>> Error: a unit test failed, please do one of: >>> >>> make CppunitTest_dbaccess_CRMDatabase_test CPPUNITTRACE="gdb --args" >>> # for interactive debugging on Linux >>> make CppunitTest_dbaccess_CRMDatabase_test VALGRIND=memcheck >>> # for memory checking >>> make CppunitTest_dbaccess_CRMDatabase_test DEBUGCPPUNIT=TRUE >>> # for exception catching >>> >>> You can limit the execution to just one particular test by: >>> >>> make CPPUNIT_TEST_NAME="testXYZ" ...above mentioned params... >>> >>> make[1]: *** >>> [/home/apu/projects-and-code/libreoffice-code/libreoffice/solenv/gbuild/CppunitTest.mk:145: >>> >>> /home/apu/projects-and-code/libreoffice-code/libreoffice/workdir/CppunitTest/dbaccess_CRMDatabase_test.test] >>> Error 1 >>> make[1]: *** Waiting for unfinished jobs.... >>> make: *** [Makefile:312: build] Error 2 >> >> Best, >> Apurv >> >> Sent with [Proton Mail](https://proton.me/mail/home) secure email.
