QA/Bibisect/Windows
TDF LibreOffice Document Liberation Project Community Blogs Weblate Nextcloud Redmine Ask LibreOffice Donate
This page provides information about using our Bibisect repositories on computers running MS Windows.
Introduction
For the bibisecting workflow, see the General Instructions section in the main article.
If you're testing cross-platform and wish to test Windows bugs on a different OS, one option is to set up a virtual machine running Windows (see #VM below).
Limitations
Unlike GNU/Linux and macOS, there are some speed issues with Git running on Windows. The speed of git may somewhat influence the speed at which one can switch between LibreOffice versions while bibisecting, but will not affect the operation of LibreOffice or the speed of the program.
Setting up your environment
Before you download the bibisect repository, make sure your machine has the right software installed. For all OSes, you'll need to install git. On Windows, we suggest that you install Git for Windows. When installing Git for Windows, it is a good idea to select the option ”Checkout as-is, commit Unix-style line endings” because this is required, if you ever get into LibreOffice development.
The example commands for Windows assume you are using the new PowerShell. If you don't have the new PowerShell yet, launch the old PowerShell version 5 and install the new one with this command:
winget install --id Microsoft.PowerShell --source winget
Previously, we recommended Cygwin, but running git under it is rather slow. Note that you can't mix Cygwin and Git for Windows when dealing with a specific repository. Cygwin is still required to use the win86-releases repository.
Windows notes
In win32-5.1, due to the backslash (possibly related to this issue) you might get this error:
error: invalid path 'instdir/program/python-core-3.3.3/lib\__pycache__/quopri.cpython-33.pyc'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You have to do this config change:
git config core.protectNTFS false
and then
git reset --hard
Download command for git bundles to use with PowerShell on Windows:
Invoke-WebRequest -Uri https://bibisect.libreoffice.org/win32-x.x.git-bundle -OutFile win32-x.x.git-bundle -Resume
To run versions from the 4 and 5 series, one needs to have Microsoft Visual C++ redistributables 2010, 2012, 2013 and 2015-2022 installed - both the 32-bit and 64-bit versions for every one of them. There is a convenient installation package, which includes the required versions.
If you are using the win32-5.0 repo and already see the bug in its oldest commit, replace bibisectRequest with preBibisect in Keywords and set the Version field to 5.0.0.0.alpha0+ Master.
Adding missing tags for oldest and latest commits
Sometimes a bibisect repo does not have any tags. In this situation you can git bisect start using the latest and oldest commit hashes, but you might find it convenient to create tags for them. Sometimes only the latest tag is missing in which case you can use "master".
Run
git log
Copy the commit hash from the topmost commit and use it for the tagging command (replace example hash with what you've got in your clipboard):
git tag latest e3f920c8fe63c14ebb83ca9c4a86247043b054df
Run
git log --reverse
Again, copy the topmost commit hash and:
git tag oldest 633bfe84509c1953415e5dd0f564098a16890131
Now you can list your tags with:
git tag -l
VM
Testing Windows bugs inside a VM is a great way to leverage the large number of bibisect repositories available for this platform if you're using macOS or GNU/Linux as your host OS.
Suggested setup:
- Virtualization Software: VirtualBox
- Guest OS: Windows 10 or later
- (Virtual) Hard drive: at least 40GB (some bibisect repositories are over 10GB each, so it is better to download them into a shared folder instead of taking space from the VM)
Versions
Built on | Version | Maintainer | Commit range from | Commit range to | Commits in range | Number of builds | Download links | Download size | Comments |
---|---|---|---|---|---|---|---|---|---|
Windows 32bit | bibisect-win32-4.3 | Cloph | fc8f44e8 | 2d13cf60 | 12910+672 builds | TDF: repo | 8.42GiB | libreoffice-4-2-branch-point up to libreoffice-4-3-branch-point. Fetch commit notes: git fetch origin refs/notes/commits:refs/notes/commits Do regular bibisect with tag oldest and latest, and if you end up on a commit that has a note attached, do as it says (continue between the tags fixup_oldest and fixup_latest) | |
Windows 32bit | bibisect-win32-4.4 | Cloph | dea4a3b9 | 3f94c9e9 | 1010 builds | TDF: repo | 3.71GiB | libreoffice-4-3-branch-point up to libreoffice-4-4-branch-point with an interval of ~8 commits. | |
Windows 32bit | bibisect-win32-5.0 | Norbert Thiebaud | 57d6b92b | 87ac0b1e | 8652 builds | TDF: repo | 4.87GiB | libreoffice-4-4-branch-point to libreoffice-5-0-branch-point and then libreoffice-5-0 | |
Windows 32bit | bibisect-win32-5.1 | Norbert Thiebaud | ab465b90 | 5616d22b | 9383 builds | TDF: repo | 5.37GiB | libreoffice-5-0-branch-point to libreoffice-5-1-branch-point and then libreoffice-5-1 | |
Windows 32bit | bibisect-win32-5.2 | Norbert Thiebaud | 49c2b980 | e5ebc3d7 | 8819 builds | TDF: repo | 4.58GiB | libreoffice-5-1-branch-point to libreoffice-5-2-branch-point and then libreoffice-5-2 | |
Windows 32bit | bibisect-win32-5.3 | Norbert Thiebaud | 5b168b3f | e7738ab7 | 8039 builds | TDF: repo | 4.34GiB | libreoffice-5-2-branch-point to libreoffice-5-3-branch-point and then libreoffice-5-3 | |
Windows 32bit | bibisect-win32-5.4 | Xisco Fauli | 4136757b | 534fd9aa | 7647 builds | TDF: repo | 3.30GiB | libreoffice-5-3-branch-point to libreoffice-5-4-branch-point and then libreoffice-5-4 | |
Windows 32bit | bibisect-win32-6.0 | Xisco Fauli | 9feb7f70 | c30963b8 | 8608 builds | TDF: repo | 3.98GiB | libreoffice-5-4-branch-point to libreoffice-6-0-branch-point and then libreoffice-6-0 | |
Windows 32bit | bibisect-win32-6.1 | Xisco Fauli | 6eeac353 | 5b3765f4 | 8845 builds | TDF: repo | 5.05GiB | libreoffice-6-0-branch-point to libreoffice-6-1-branch-point and then libreoffice-6-1 | |
Windows 32bit | bibisect-win32-6.2 | Xisco Fauli | 3a801799 | 5f01fe15 | 8553 builds | TDF: repo | 6.84GiB | libreoffice-6-1-branch-point to libreoffice-6-2-branch-point and then libreoffice-6-2 | |
Windows 32bit | bibisect-win32-6.3 | Xisco Fauli | a20a2d7e | 13152ad8 | 7492 builds | TDF: repo | 7.25GiB | libreoffice-6-2-branch-point to libreoffice-6-3-branch-point and then libreoffice-6-3 | |
Windows 64bit | bibisect-win64-6.4 | Xisco Fauli | c98b1f1c | 188ddcd4 | 6894 builds | TDF: repo | 10.5GiB | libreoffice-6-3-branch-point to libreoffice-6-4-branch-point and then libreoffice-6-4 | |
Windows 64bit | bibisect-win64-7.0 | Xisco Fauli | 9bc848cf | 2891e91a | 6816 builds | TDF: repo | 13.13GiB | libreoffice-6-4-branch-point to libreoffice-7-0-branch-point and then libreoffice-7-0 | |
Windows 64bit | bibisect-win64-7.1 | Xisco Fauli | 574c5709 | a94b5827 | 7013 builds | TDF: repo | 11.81GiB | libreoffice-7-0-branch-point to libreoffice-7-1-branch-point and then libreoffice-7-1. | |
Windows 64bit | bibisect-win64-7.2 | Xisco Fauli | 738bcf5e | ffa09959 | 7877 builds | TDF: repo | 11.65GiB | libreoffice-7-1-branch-point to libreoffice-7-2-branch-point and then libreoffice-7-2. | |
Windows 64bit | bibisect-win64-7.3 | Xisco Fauli | ff2ba77f | e1ad83dd | 6997 builds | TDF: repo | 11.25GiB | libreoffice-7-2-branch-point to libreoffice-7-3-branch-point and then libreoffice-7-3. | |
Windows 64bit | bibisect-win64-7.4 | Xisco Fauli | 436f14c2 | f8ba7c6f | 7788 builds | TDF: repo | 9.83GiB | libreoffice-7-3-branch-point to libreoffice-7-4-branch-point and then libreoffice-7-4. | |
Windows 64bit | bibisect-win64-7.5 | Xisco Fauli | c94961c6 | TDF: repo | 7.86 GiB | libreoffice-7-4-branch-point to libreoffice-7-5-branch-point and then libreoffice-7-5. | |||
Windows 64bit | bibisect-win64-7.6 | Xisco Fauli | 1c629ca0 | TDF: repo | libreoffice-7-5-branch-point to libreoffice-7-6-branch-point and then libreoffice-7-6. | ||||
Windows 64bit | bibisect-win64-24.2 | Xisco Fauli | 6f227b0d | TDF: repo | libreoffice-7-6-branch-point to libreoffice-24-2-branch-point and then libreoffice-24-2. | ||||
Windows 64bit | bibisect-win64-24.8 | Xisco Fauli | 898d5d47 | TDF: repo | libreoffice-24-2-branch-point to libreoffice-24-8-branch-point and then libreoffice-24-8. | ||||
Windows 64bit | bibisect-win64-25.2 | Xisco Fauli | 798b43c4 | TDF: repo | libreoffice-24-8-branch-point to libreoffice-25-2-branch-point and then libreoffice-25-2. | ||||
Windows 64bit | bibisect-win64-25.8 | Xisco Fauli | 8fb31e76 | TDF: repo | libreoffice-25-2-branch-point to latest master. | ||||
Releases | releases | Xisco Fauli | 321 releases | TDF: repo | 17+ GB | Release builds of OOo 3.3.0, LO 3.3.0 - LO 6.4.7.2. To bisect versions 4.2 and older, you can't use Windows Git. Instead, you need to use Cygwin's git package. To be sure, check in Cygwin shell that git --version does not include the string "windows". You can use Cygwin's Git from PowerShell, if you want to.
|
Testing Versions
These are for testing purposes only.
Build on | Version | Maintainer | Auto-fed? | Commit range from | Commit range to | Commits in range | Number of builds | Download links | Download size | Bibisected bugs in range | Comments |
---|---|---|---|---|---|---|---|---|---|---|---|
WIN | win 2013-12-13_2013-12-19 | Cloph? | No | ? | ? | ? | ? | TDF: repo | 3.5GB | not active, for testing only |
How to fix 'instdir/cache/opengl_device.log' error
This happens with bibisect-win32-6.2 due to an untracked file
error: The following untracked working tree files would be overwritten by checkout: instdir/cache/opengl_device.log Please move or remove them before you switch branches. Aborting
Fix:
rm instdir/cache/opengl_device.log