[Libreoffice-qa] Trouble bibisecting - 'com::sun::star::uno::RuntimeException'

[Mirosław Zalewski]

Hi

I am trying to bibisect one particular issue, but have no luck thus far.

I have downloaded huge file with bibisect repo, zsync'ed it with
newest changes and unpacked into working directory, as wiki page says
to do.

When I did:
./opt/program/soffice -env:UserInstallation=file:///tmp/soffice-bisect
I got error message about libreglo.so not found. According to bug
67313, lo prefixes were introduced recently to differentiate
LibreOffice libraries from other libraries on some systems.

So I did
ln -s opt/ure/lib/libreg.so opt/ure/lib/libreglo.so
to make sure that file exists.

Problem persisted, so I figured out that soffice.bin is simply not
looking where it should be for libreglo.so file.

Therefore, I added opt/ure/lib/ to my LD_LIBRARY_PATH:
export
LD_LIBRARY_PATH='/lib/i386-linux-gnu:/usr/lib/i386-linux-gnu:/lib/i486-linux-gnu:/usr/lib/i486-linux-gnu:/usr/local/lib:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/lib32:/usr/lib32:opt/ure/lib/'
(I am not sure if mentioning all system paths written
in /etc/ld.so.conf.d/ is necessary, but it wouldn't hurt, would it?)

But now LO splash screen appears for a brief moment and then
disappears, with messages left in terminal window:
"
Warning: failed to launch javaldx - java may not function correctly
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve 
property `gtk-toolbar-style' of type `GtkToolbarStyle' from rc file value 
"((GString*) 0x1facee0)" of type `GtkToolbarStyle'
/home/minio/.gtkrc-2.0:14: error: unexpected character `=', expected keyword - 
e.g. `style'
terminate called after throwing an instance of 
'com::sun::star::uno::RuntimeException'
"

I figured out it might be problem with GTK libraries, so I forced
generic X interface:
export SAL_USE_VCLPLUGIN=gen
export OOO_FORCE_DESKTOP=none

But then, problem persists. The only message I get is:
terminate called after throwing an instance of 
'com::sun::star::uno::RuntimeException'

I have also tried debugging startup process; gdb log is attached by the
end of the message.

Does any of that makes any sense to you? How can I fix this error and
start bibisecting?
I am using Debian testing updated on daily manner, amd64 architecture.

gdb log:
GNU gdb (GDB) 7.6 (Debian 7.6-5)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from 
/home/minio/sources/lo-bibisect/binrepo/opt/program/soffice.bin...(no debugging 
symbols found)...done.
/home/minio/sources/lo-bibisect/binrepo/opt/program/gdbtrace: Nie ma takiego 
pliku ani katalogu.
(gdb) run
Starting program: 
/home/minio/sources/lo-bibisect/binrepo/opt/program/soffice.bin --backtrace 
-env:UserInstallation=file:///tmp/soffice-bisect
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe881d700 (LWP 32762)]
[New Thread 0x7fffe53c3700 (LWP 306)]
terminate called after throwing an instance of 
'com::sun::star::uno::RuntimeException'

Program received signal SIGABRT, Aborted.
0x76d6e1e5 in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x76d6e1e5 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x76d71398 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x77659605 in __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x77657766 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x77657793 in std::terminate() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x776579bf in __cxa_throw () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x7fffe5f293dc in 
configmgr::Components::Components(com::sun::star::uno::Reference
 const&) ()
   from 
/home/minio/sources/lo-bibisect/binrepo/opt/program/../program/configmgr.uno.so
#7  0x7fffe5f29dcf in 
configmgr::Components::getSingleton(com::sun::star::uno::Reference
 const&) ()
   from 
/home/minio/sources/lo-bibisect/binrepo/opt/program/../program/configmgr.uno.so
#8  0x7fffe5f2c9b9 in configmgr::configuration_provider::(anonymous 
namespace)::Service::createInstanceWithArguments(rtl::OUString const&, 
com::sun::star::uno::Sequence const&) () from 
/home/minio/sources/lo-bibisect/binrepo/opt/program/../program/configmgr.uno.so
#9  0x73af7983 in utl::ConfigManager::acquireTree(utl::ConfigItem&) () 
from /home/minio/sources/lo-bibisect/binrepo/opt/program/libutllo.so
#10 0x73af87c2 in utl::ConfigManager::addConfigItem(utl::ConfigItem&) 
() fr

Re: [Libreoffice-qa] Trouble bibisecting - 'com::sun::star::uno::RuntimeException'

[Mirosław Zalewski]

Dnia 2013-10-24, o godz. 10:54:10
Mirosław Zalewski  napisał(a):

> I have downloaded huge file with bibisect repo

If anyone wonders, by "huge file" I mean 17G 4.0+ version:
http://people.canonical.com/~j-lallement/libreoffice/binrepo/bibisect-4.0.tar.lzma
It seems that there are also other bibsect archives, around 4G in
size, but I have not touched them yet.
-- 
Best regards
Mirosław Zalewski
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

Re: [Libreoffice-qa] Trouble bibisecting - 'com::sun::star::uno::RuntimeException'

[Mirosław Zalewski]

I decided to use violence and removed my binrepo directory and then
extracted bibisect.tar.lzma content again.

After following these guides step-by-step:
https://wiki.documentfoundation.org/QA/HowToBibisect
http://flosmind.wordpress.com/libreoffice-bisecting/
http://www.youtube.com/watch?v=SA88flop4MM

Bibisected LibreOffice is starting as it should be and I have managed
to track down commit I was looking for.

I am not sure why it did not work before and does work now.
It might be that git checkout command is neccessary, and Florian's blog
post does not mention it.
Or maybe I have messed up my repo to the state that git tracking
mechanism and source tree were out of sync.

If anyone knows why it might have happened, please share - it might be
useful information for future bibisecters.
-- 
Best regards
Mirosław Zalewski
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

Re: [Libreoffice-qa] Trouble bibisecting - 'com::sun::star::uno::RuntimeException'

[Robinson Tryon]

On Thu, Oct 24, 2013 at 8:41 AM, Mirosław Zalewski
 wrote:
> I decided to use violence and removed my binrepo directory and then
> extracted bibisect.tar.lzma content again.

:-)

> After following these guides step-by-step:
> https://wiki.documentfoundation.org/QA/HowToBibisect
> http://flosmind.wordpress.com/libreoffice-bisecting/
> http://www.youtube.com/watch?v=SA88flop4MM
>
> Bibisected LibreOffice is starting as it should be and I have managed
> to track down commit I was looking for.

Good, good.

>
> I am not sure why it did not work before and does work now.
> It might be that git checkout command is neccessary, and Florian's blog
> post does not mention it.
> Or maybe I have messed up my repo to the state that git tracking
> mechanism and source tree were out of sync.

That's possible. IIRC, Joren said that he had a problem with his git
tree being stuck in a weird state. Joren -- did you ever figured out
what went wrong with your bibisect repo, and have you managed to
repair it?

I wonder if it would be possible to wipe out local changes in the git
repo just using zsync commands?  (I'm not so familiar with the way
that zsync works)

>
> If anyone knows why it might have happened, please share - it might be
> useful information for future bibisecters.

Bjoern might have some insight here, but it might just be gremlins in
the repo. It's unfortunate that the repo is such a large re-download
if/when it breaks.

--R
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

Re: [Libreoffice-qa] [ANN] LibreOffice 4.0.6 RC2 test builds available

[Pedro]

Hi Jean-Baptiste


Jean-Baptiste Faure wrote
> This link (for example) :
> https://www.libreoffice.org/download/?type=deb-x86_64&version=4.0.6&lang=fr
> It gives only the RC1.

Never mind RC2. The final version (aka 4.0.6.2 or just 4.0.6) was already
announced

http://nabble.documentfoundation.org/The-Document-Foundation-announces-LibreOffice-4-0-6-tp4079543.html

Best regards,
Pedro



--
View this message in context: 
http://nabble.documentfoundation.org/Libreoffice-qa-ANN-LibreOffice-4-0-6-RC2-test-builds-available-tp4078636p4079627.html
Sent from the QA mailing list archive at Nabble.com.
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

[Libreoffice-qa] minutes of ESC call ...

[Michael Meeks]

* Present:
+ Norbert, David, Eike, Robinson, Lionel, Tsahi, Caolan, Kendy,
  Markus, Ahmad, Adam, Michael M, Michael S, cloph, Stephan, Miklos,
  Andras, Bjoern

* Completed Action Items:
+ setup infrastructure to build bibisect repos (Cloph / Bjoern /
  Norbert)
[ The ubuntu one is now up to date again, is published:
  https://bugs.freedesktop.org/show_bug.cgi?id=70652 ]
+ create script to auto-mail users list for each API Change commit (Bjoern)
[ Easyhack: https://bugs.freedesktop.org/show_bug.cgi?id=70667 ]
+ find better way to export from Coverity categories of non-security
  critical bugs (Caolan)
[ In progress. Works in theory, but in practice slow and due to
  network issues practical limit of just a few hundred ]
[ discussed with Coverity at LinxConEurope - they're implementing
  a feature to do what we need => punt ]
+ ask Florian for a minimal / simple solution for larger bug docs (Robinson)
[ use a directory on OwnCloud for now ]
  
* Pending Action Items:
+ Include new C* font google replacements into vanilla install
  (Caolan)
+ New templates (Ahmad)
+ Template has to be hard-coded in code. Ideally as real documents.
[ work in progress hard-coding templates as code ]
+ produce a VM for the load / crash regressions (Cloph / Markus)
[ VM created, currently busy harvesting test documents,
  should be done in parallel - 9x scripts side by side ... ]
+ partition document test loads / run them on tinderboxen (Norbert)
+ produce a VM with callgrind metrics (Matus)
AI:  poke Matus (Michael)
+ get setup wrt. mobile app-store access (Cloph / Thorsten)
[ in progress around 4.1.3 ]
+ draw bugzilla migration threads together & propose funding to the
  board (Robinson)
[ discuss on the QA list, proposal in the next week ]


* Release Engineering update (Cloph)
+ 4.0.6 retrospective
+ released today at noon, delayed by couple of missing approvals ?
+ 4.1.3 status
+ test builds for RC2 up-loaded, but Windows late.
+ otherwise on-track for release next week
+ 4.2 Alpha release planned for Nov 4th.
+ GSOC / Android & iOS remote releases from master
+ as above, in progress for 4.1.3
+ reinvestigate/clarify our communication on review deadlines etc. (Bjoern)
+ Petr used to lean on people to review open patches before tag creation
+ missed patches before 4.0.6 and 4.1.3 - not enough review before tag 
creation.
+ what to do ?
   + make developers more responsible for deadlines ?
   + or ask Cloph to help baby-sit un-reviewed patches ?
+ need some advanced notice / baby-sitting of patch reviews.
   + Cloph been extremely busy
   + sometimes we're not sure if we already passed the deadline (Miklos)
   + possible to poke on IRC to get these unwound noisily !


* Best-practise around commit messages (Michael)
eg. commit c3ef735fd5d8866c8ce28b89744150e733087427 [ not truly mine ]
eg. commit 359472b2b50165966c27c239eccd3ecfb03e2acc
+ git scales well with the real data not the meta-data so much (Miklos)
   + concern that we don't put lots of IRC log, gdb traces in commit msgs 
(Michael)
   + concern that commit msgs are too short generally (Norbert)
   + commit msgs should have a length that reflects the complexity of the 
change,
 but not too verbose.


* larger code structural changes - eg. external/ move ? (Bjoern)
+ good idea but surprising - discussed at ESC ?
  
http://nabble.documentfoundation.org/move-external-builds-into-subfolder-fdo-70393-td4078160.html
+ after sitting for 4 days on gerrit / bugzilla etc.
+ silent approval by at least two core devs (Eike replied, David T. 
CCed on bug)
+ David T. also merged a lot of the changes :-)
+ the 'make ' on cmdline doesn't work anymore (Norbert)
+ can do 'make liborcus' still - fixed it (Mst)


* EasyHack exhaustion (Michael)
+ purpose of easy hacks is to get people involved in the project.
+ creating them takes work.
+ experienced guys having done a few should move onto harder ones
  and not fix the easiest of hacks: leaving them for newbies.
+ a great thing to work on 'next' is .ui file conversion:
+ a huge & almost un-bounded problem.
+ or onto finishing the string conversion bits.
+ really positive progress from interaction with the ML, thanks Bjoern


* FOSDEM:
+ I believe we need to submit talks directly to Pentabarf ourselves
AI: + poke people more, and get submission details from Italo (Kendy)
+ Travel can be covered by TDF - planned for 2x days after FOSDEM.
   + is 2x days long enough ?


* Google C* font replacements / update (Caolan)
+ should we back-port to 4.1.x ?


* QA update (Robinson)
+ OSX

Re: [Libreoffice-qa] daily vs. 4.-0+ bibisect repos [was: Trouble bibisecting - 'com::sun::star::uno::RuntimeException']

[Mirosław Zalewski]

Hi all

I spent afternoon with git manual and repeatedly removing/unpacking
bibisect archives and I think I understand a little more now.

Dnia 2013-10-24, o godz. 11:29:42
dk...@torfree.net napisał(a):

> I am confused about the names "daily" and "4.0+" for bibisect
> repositoriies.  Does it make sense now to say "daily" at all?
> 
> I gather vaguely from messages on the dev list that the maintenance
> process for the bibisect repository or repositories has not settled
> down to its final state.  But if my confusion has led Mirosław
> into confusion, I should correct HowToBibisect
>  promptly, even
> if only as an interim measure.
> 
> But first, somebody please tell me what is what.

As far as I am concerned, "daily" and "4.0+" were the smallest source of
my confusion. But there are many other problems with instructions.

First and foremost, we have two repositories from two men. These not
only serve different purpose, but also are set up differently, which
means that user must perform different steps depending on which one he
has. Unfortunately, these differences are never laid out
systematically. I learned them by trial and error.
I think that "versions" table could use another column with name of man
who created archive in question. Then we can reference to them as
"Bjoern archive" and "Jean archive".

If one is to seriously bibisect, he has to download two packages:
1. Bjoern 4.0, which covers everything from 2011-08-06 (about midway
between branching 3.4 and 3.5 from master) to 2012-12-08 (around
branching 4.0 from master).

2. Either Bjoern 2013-10-12 or Jean 4.0+. They both cover roughly the
same area, since 2012-12-08 to 2013-09-17 (later date is subject to
change). The difference between them is density of builds - Jean
archive is far denser, which means that each build covers fewer
commits, which means that finding patch that introduced regression is
easier for developer with bisect log. But we pay for this with almost 4
times bigger package.
Also, Jean package was supposed to be updated daily, while Bjoern
apparently never made such commitment. But at the moment they both are
not updated for a month and they both stop at about the same moment in
time.

Of course second package is more important, as we are mainly interested
in newer regressions. But there are still bugs that can be bibisected
only with older package.

When we download and unpack archive, we must set up working
environment. And that depends which package we have used.

In Bjoern packages (well, "4.0" that is; I did not checked
"2012-10-12", but assume it is set up the same way) our main concern is
HEAD set up at oldest commit. This way `git rev-parse HEAD` will
produce ID of oldest commit. If we blindly follow instructions at wiki,
we will end up assigning "latest" tag to oldest possible commit.
Our second problem is that we have empty git working tree.
Both of them can be fixed by issuing:
git checkout master

We are ready to go. We can assign "latest" tag to ID returned by git
rev-parse and "oldest" tag to 65fd30f5cb4. Then we can issue bibisect
command.

In Jean package, on the other hand, HEAD is set up to latest commit.
But since our git working tree is empty, git thinks that we have one
uncommitted change (the one that removes everything...). 
We can assign tags to commits, but then bibisect command will bring
working tree to messed state.
This command, mentioned at very beginning of "Bibisecting" section at
wiki:
git checkout latest
will not refresh working directory content, because git IS already at
latest tree version. Wiki says that we should execute `soffice`
command, but this will not be possible.
The second command, `git checkout oldest`, will leave us with broken
git tree. My assumptions why it happens are outlined below.

We can fix all these problems and go ahead with wiki instructions by
forcing git to restore working tree content to state it was supposed to
be at current revision:
git checkout-index -a
Then we can tag latest and oldest commits (commands are already on the
wiki), checkout any commit and start bisecting.

BTW: git bisect will pick up commit in the middle between known good
and bad version and bring working tree to state of that revision.
Therefore, `git checkout {oldest,latest}` are needed only to verify
that bug was introduced in one of builds that we have access to.
Actually, we can check only oldest commit. If we are on "4.0+" or
"2012-10-12" and the bug is present, then we must check Bjoern "4.0"
archive; if we are on Bjoern "4.0" and bug is present in oldest
revision, then we must set whiteboard to "prebibisect", because it was
introduced somewhere before August of 2011.

Finally, there is that thing why `git checkout oldest` does not work in
Jean archive (it leaves with broken LO due to renamed libraries).
I suppose that `git checkout` does not use full restore, but
differential/incremental one. That is: if we want to switch

[Libreoffice-qa] [Solved] Re: Windows builds (last 2013-10-16)

[mariosv]

Hi,

Nice to see Tinderbox #42 producing again daily installation files for
master, from 23-Oct-2013 20:21.

Thanks.
Miguel Ángel.



--
View this message in context: 
http://nabble.documentfoundation.org/Windows-builds-last-2013-10-16-tp4078857p4079693.html
Sent from the QA mailing list archive at Nabble.com.
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/