Created attachment 46528 [details] hid.lst Platform: SLED 11 sp1 i586 build info: Libreoffice master [Steps] Regarding to: https://bugs.freedesktop.org/show_bug.cgi?id=36802 In the latest master build, testtool.bin can launch standalone now. However 'testtool.bin -run' is still not available to perform tests. For example: $ cd install/basis-link/program $ ./testtool.bin -run ../../../clone/testing/testautomation/framework/optional/f_basic_first.bas LibreOffice: Using system memory allocator. LibreOffice: This is for debugging only. To disable, LibreOffice: unset the environment variable G_SLICE. ./testtool.bin: symbol lookup error: ./testtool.bin: undefined symbol: _ZN8DirEntry5ToRelERKS_ The hid.lst I used is also attached.
Thanks Petr or Michael to have a review.
Yi Fan, what version have you tested? There were many problems with missing symbols in the 32-bit linux builds. They were fixed in beta4. See the bug #36275. Note that testtool.bin crashed in beta4, see the bug #36802.
this works fine for me - marking as a dup of the symbol problem. Having said that - the test loads, executes and exits -extremely- quickly, such that I find it hard to believe that the test has really run (personally) ;-)
could you add back this function as it borks the testtool :-)
(In reply to comment #4) > could you add back this function as it borks the testtool :-) nevermind, it's not clear if it's really necessary to re-add back that symbol and I see this bug is actually marked as fixed
(In reply to comment #2) > Yi Fan, what version have you tested? > > There were many problems with missing symbols in the 32-bit linux builds. They > were fixed in beta4. See the bug #36275. > > Note that testtool.bin crashed in beta4, see the bug #36802. Hi Petr, Thanks for looking at this. The version I tried yesterday are: 1. testtool.bin in the latest master built 2. testautomation script in the latest built master built 3. hid.lst 300 m9 4. a nightly libreoffice build: libreoffice-3-4~2011-05-03_07:07:13_LibO_3.4.0beta3_Linux_x86_install-rpm_en-US.tar.gz
(In reply to comment #6) > (In reply to comment #2) > Thanks for looking at this. The version I tried yesterday are: > > 1. testtool.bin in the latest master built > 2. testautomation script in the latest built master built I am confused. What do you mean with "master build"? The installation tarball mentioned below comes from the libreoffice-3-4 branch. In each case, you should not combine stuff from master and the branch. All fixes primary goes to the branch these days. > 3. hid.lst 300 m9 > 4. a nightly libreoffice build: > libreoffice-3-4~2011-05-03_07:07:13_LibO_3.4.0beta3_Linux_x86_install-rpm_en-US.tar.gz Hmm, the symbols were corrected in the build from 2011-05-02-18:50. This one is newer, so it should be correct as well.
I do not see the missing symbol in the last daily build libreoffice-3-4~2011-05-09_20:41:50_LibO_3.4.0beta4_Linux_x86_install-rpm_en-US.tar.gz => we should be on the safe side.
libreoffice-3-4~2011-05-03_07:07:13_LibO_3.4.0beta3_Linux_x86_install-rpm_en-US.tar.gz (In reply to comment #7) > I am confused. What do you mean with "master build"? The installation tarball > mentioned below comes from the libreoffice-3-4 branch. In each case, you should > not combine stuff from master and the branch. All fixes primary goes to the > branch these days. Hi Petr, Since the testtool.bin is not yet working in 3.4 beta4, so I wanted to try the latest fix of: https://bugs.freedesktop.org/show_bug.cgi?id=36802 in which Michael mentioned the testtool problem is fixed in master. So I build it in the latest master branch yesterday. Then I use the built testtool.bin to run cases against a libreoffice installation: libreoffice-3-4~2011-05-03_07:07:13_LibO_3.4.0beta3_Linux_x86_install-rpm_en-US.tar.gz from which I got the error in the top comment. Is this a right way?
(In reply to comment #9) > in which Michael mentioned the testtool problem is fixed in master. So I build > it in the latest master branch yesterday. How did you build it? Did you do it yourself? It might be a mistake on your side. > Then I use the built testtool.bin to run cases against a libreoffice > installation: > > libreoffice-3-4~2011-05-03_07:07:13_LibO_3.4.0beta3_Linux_x86_install-rpm_en-US.tar.gz Hmm, I am not sure how you combined the two builds. It sounds like a mess. I would suggest to wait for newer build from the libreoffice-3-4 branch a make sure that you have a clean LO installation.
(In reply to comment #10) > > Then I use the built testtool.bin to run cases against a libreoffice > > installation: > > > > libreoffice-3-4~2011-05-03_07:07:13_LibO_3.4.0beta3_Linux_x86_install-rpm_en-US.tar.gz > > Hmm, I am not sure how you combined the two builds. It sounds like a mess. I > would suggest to wait for newer build from the libreoffice-3-4 branch a make > sure that you have a clean LO installation. Yes, probably there are something wrong with the settings. I didn't insist to try that today :) Thanks for the info, I'll wait a new build.
RESOLVED, FIXED or CLOSED bugs cant be KEYWORD NEEDINFO.