Bug 50384 - failing unit tests when building from source
Summary: failing unit tests when building from source
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
Master old -3.6
Hardware: x86-64 (AMD64) Linux (All)
: low major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-27 01:53 UTC by Arno
Modified: 2020-12-01 10:31 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arno 2012-05-27 01:53:12 UTC
While building libreoffice from source HEAD it fails as follows:


[ build MOD ] sal
[ build ALL ] top level modules: sal
[ build ALL ] loaded modules: sal

[ build CUT ] Module_DLL
[ build CUT ] sal_bytesequence
[ build CUT ] sal_osl_condition
[ build LNK ] CppunitTest/libtest_sal_osl_file.so
[ build CUT ] sal_osl_file
[ build CUT ] sal_osl_module
[ build CUT ] sal_osl_old_test_file
[ build CUT ] sal_osl_security
[ build CUT ] sal_osl_thread
[ build CUT ] sal_osl_process
[ build CUT ] sal_rtl_alloc
[ build CUT ] sal_rtl_cipher
[ build CUT ] sal_rtl_crc32
[ build CUT ] sal_rtl_doublelock
[ build CUT ] sal_rtl_locale
[ build LNK ] CppunitTest/libtest_sal_rtl_ostringbuffer.so
[ build CUT ] sal_rtl_ostringbuffer
[ build CUT ] sal_rtl_oustringbuffer
[ build CUT ] sal_rtl_strings
test_strings_replace.cxx:230:Assertion
Test name: N12_GLOBAL__N_14TestE::ustringReplaceFirstAsciiLAsciiL
equality assertion failed
- Expected: otherbarfoo
- Actual  : 

test_strings_replace.cxx:309:Assertion
Test name: N12_GLOBAL__N_14TestE::ustringReplaceAllAsciiLAsciiL
equality assertion failed
- Expected: otherbarother
- Actual  : 

test_oustring_stringliterals.cxx:143:Assertion
Test name: N4test8oustring14StringLiteralsE::checkUsage
assertion failed
- Expression: foobarfoo.replaceFirst( "foo", "test" ) == "testbarfoo"

test_oustring_stringliterals.cxx:164:Assertion
Test name: N4test8oustring14StringLiteralsE::checkNonconstChar
equality assertion failed
- Expected: foobar
- Actual  : foo

Failures !!!
Run: 20   Failure total: 4   Failures: 4   Errors: 0

Error: a unit test failed, please do one of:

export DEBUGCPPUNIT=TRUE            # for exception catching
export GDBCPPUNITTRACE="gdb --args" # for interactive debugging
export VALGRIND=memcheck            # for memory checking
and retry.
make[2]: *** [/home/arno/src/libreoffice/workdir/unxlngx6.pro/CppunitTest/sal_rtl_strings.test] Fehler 1

-----------------------------------------------------------------------
        Oh dear - something failed during the build - sorry !
  For more help with debugging build errors, please see the section in:
            http://wiki.documentfoundation.org/Development

  internal build errors:

ERROR: error 512 occurred while making /home/arno/src/libreoffice/sal/prj

 it seems that the error is inside 'sal', please re-run build
 inside this module to isolate the error and/or test your fix:

build_error.log should contain the captured output of the failed module(s)

-----------------------------------------------------------------------
To rebuild a specific module:

make sal.clean # optional
make sal

when the problem is isolated and fixed, re-run 'make'
make[1]: *** [build-packimages] Fehler 1
make[1]: Verlasse Verzeichnis '/home/arno/src/libreoffice'
make: *** [all] Fehler 2
Comment 1 Korrawit Pruegsanusak 2012-05-30 04:00:40 UTC
The common answers for this are
1. try as it suggested:
> make sal.clean
> make sal

2. try ./g pull -r to update the source

And when reporting this type of problem, could you please tell:
1. what exactly the HEAD commit is, by 'git show' and tell the commit ID
2. your autogen.lastrun (build configuration)

Looking at the tinderbox <http://tinderbox.libreoffice.org/MASTER/status.html>, some linux builds are green by now, so ./g pull -r might help.
Comment 2 Markus Mohrhard 2012-08-07 13:38:44 UTC
Is this still an issue?
Comment 3 Joel Madero 2012-10-23 17:16:48 UTC
I now have this issue, just pulled yesterday but I've had the problem for nearly 2 weeks. New issue for me. Tried a clean build and that didn't solve anything
Comment 4 Joel Madero 2012-10-23 17:18:11 UTC
Marked as NEW and prioritizing relatively high as I can confirm that I can't even get a build to work. 

Major: Prevents build

Importance: Low, doesn't seem to be affecting many users but for those who it does...it's a show stopper
Comment 5 Jorendc 2014-06-25 15:12:39 UTC
If someone still see this issue, please send an email to the development mailing list https://wiki.documentfoundation.org/Development

Kind regards,
Joren
Comment 6 Maathew Peter 2020-12-01 10:31:48 UTC
Does the problem still persist?

https://bugs.documentfoundation.org/show_bug.cgi?id=120632