本ページはGlobal Wikiからの有志による翻訳ページです。未翻訳があることや内容が古い場合があります。最新化、翻訳にご協力お願いします。 日本語独自の情報についてまとめることを目的として、日本語コミュニティによって運営されているページとして 日本語コミュニティ独自ページ があります。 URLが wiki.documentfoundation.org/JA で始まっていて、カテゴリーがJAのページです。 そちらもご利用ください。
Each bibisect package is a git repository populated with hundreds or thousands of builds of LibreOffice. Added to the repository in chronological order, the builds provide a fast and simple way for us to test a bug against many different versions without having to compile LibreOffice each time we switch.
We can leverage the tools built into git for binary search through commits (e.g. git bisect) as well as benefit from the compression and de-duplication included in git. For example, in a series of builds that each might take up 500MB of disk space, through de-duplication we can potentially use only 25MB per build.
A successful bibisect will leave developers with only a few commits to search through to find the 'culprit' commit that we believe introduced a regression. Depending upon the particular bibisect repository, this range might be 60, 100, or even 2 commits. (We also have some very 'coarse' bibisect repositories that use released versions + beta + RC builds, and these may have ranges spanning multiple hundreds of commits)
QA can go the additional step of fully bisecting (determining the exact commit) or can leave this to the developers. Often times, it's easy to find the commit that caused the issue after bibisecting the bug.
With approximately 10 gigs, you'll have hundreds of builds to work with. A bibisect can take as little as 15 minutes.
Currently bibisecting is possible on:
Note: Each operating system is different, please read the full instructions that correspond to your specific operating system (GNU/Linux, macOS, or Windows) for more complete instructions, instructional videos, and other related information.
Bibisecting relies on 6 steps:
- Setting up your environment, including installing any extra software
- Downloading the bibisect package
- Bibisecting the bug
- Getting a bibisect log
- Attaching the bibisect log to the bug report
- Updating the bug report fields
Performing a bibisect is only possible if we have a repository available for the correct OS, covering the correct range of LibreOffice commits. We have very good coverage on GNU/Linux, and are improving our coverage on Windows and macOS.
Some regressions are difficult to reproduce, and may require multiple test runs for a bug to appear. As you may imagine, trying to bibisect such regressions is very difficult, and requires one to perform many test runs after each checkout of a new version of LibreOffice to give some security / statistics that the bug is indeed present or not present with the given version.
We do not currently have bibisect support for
- LibreOffice for Android
- BSDs (although the GNU/Linux bibisect packages may run, with minor tweaks)
- LibreOffice Online
- LibreOffice Vanilla for Mac (in the Mac App Store)
Versions are listed on each OS page. See #Details above.
Some bugs are not bibisectable. These include
- Bugs that don't show up on a supported platform (see #Limitations)
- Bugs that predate our bibisect builds (We're working on extending the range covered)
- Bugs that depend upon build options not enabled in the TDF builds (e.g. -kde)
If a bug with bibisectRequest in the Whiteboard is found to be not bibisectable, leave a comment on the bug explaining why we're not able to use bibisect to track down the introduction of this problem, and replace bibisectRequest with notBibisectable in the Whiteboard.
Following Bugs with Whiteboard entry bibisectrequest are waiting for a bibisect:
Failed to load RSS feed from https://bugs.documentfoundation.org/buglist.cgi?list_id=145560&product=LibreOffice&query_format=advanced&status_whiteboard=bibisectrequest&status_whiteboard_type=allwordssubstr&title=Bug%20List&ctype=atom&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED: There was a problem during the HTTP request: 502 Bad Gateway Open this list in Bugzilla
In addition all unresolved regressions in LibreOffice might benefit from bibisecting.
For the links to bugzilla queries, please see here.
With the above info added to the bug a developer knows that the regression was introduced between the commits fb754a0df859e30255c25af8fa19bfaa75f257e7 (good) and 2d19e9bb07ccff3134f855812dddfda5c07b1fe4 (bad) on master. A:
git log fb754a0df859e30255c25af8fa19bfaa75f257e7..2d19e9bb07ccff3134f855812dddfda5c07b1fe4
on the source repository will then show the 128 commits including the one that introduced the bug, making it a lot easier for the developer to close in on the culprit. For more details, see:
To create separate profile directory in /tmp/ (which will be automatically removed during the next machine boot):
If you want to start fresh for each bisect iteration, you can add git commit hash to directory name. For example:
./opt/program/soffice \ -env:UserInstallation=file:///tmp/soffice-bisect-$(git rev-parse HEAD)
Sometimes a bug is a collateral damage of another (possibly minor) bug, in a non obvious way. In such cases that other bug might be fixed on master, but was not backported to the release branch. You can find the fix, just like finding a bug, except that you need to type
git bisect good
git bisect bad
and vice versa. If the fix is small and important enough, it likely can be easily backported to the release branch.
Please add your problems and how you solved them. This section covers issues that affect more than one OS. For OS-specific issues, please see the individual OS wiki pages.
If you can't extract files (you should get an error message). Try to rename the file from *.tar.lzma to *.tar.xz.
Problem / Messages:
error: Your local changes to the following files would be overwritten by checkout: opt/program/pythonloader.pyc opt/program/uno.pyc opt/program/unohelper.pyc Please, commit your changes or stash them before you can switch branches. Aborting
git checkout .
will repair the problem. Afterwards you can start the next test run as usual with
git bisect good # or git bisect bad
If that does not solve the problem, you can try
git clean -fd git reset --hard
The ultimate repair is to delete everything except one
hidden folder, and do
git checkout oldest
Problem: Upon trying to run soffice within bibisect you receive the error "unexpected operator terminate called after throwing an instance of 'com::sun::star::uno::DeploymentException'
Solution: Reset your libreoffice profile located in ~/.config/libreoffice. Make sure to backup the folder if you have any settings you'd like to preserve for use with your stable libreoffice release. After you're done with bibisect you can try to return your backed up profile to it's original location (ie. delete the new profile folder and replace it with the backed up one)
For details on how the bibisect archives are generated:
For information on merging all of our bibisect repositories into one big one, see
We want to make a GUI for bibisect: