Date: prev next · Thread: first prev next last
2019 Archives by date, by thread · List index


While I was improving some of the python unit tests, I found something strange in 
/sw/qa/python/xtext.py: you can remove the same annotation twice without any kind of warning or 
error.

What follows is the description of the bug at 
https://bugs.documentfoundation.org/show_bug.cgi?id=123404

When creating and removing annotations as shown in /sw/qa/python/xtext.py, annotations can be 
removed twice without causing exceptions or any kind of warning. This seems to be a silent failure, 
but I don't know if there are any side effects of doing this.

Steps to Reproduce:
1. Run the xtext unit test:
2. cd sw
3. make PythonTest_sw_python PYTHON_TEST_NAME="xtext"
4. The test completes successfully, even though it removes annotations twice.

Actual Results:
The test completes - unexpected success.

Expected Results:
The test as it is at the moment should fail in some way - throw an exception. I expected it to 
segfault, but it doesn't.


Reproducible: Always


User Profile Reset: No

I'm wondering whether this is intended behaviour, or whether this is something that should be 
fixed. The note in the unit test seems to imply it was unexpected. I''m happy to help fix this if 
it is decided that a fix is needed, but I may need some help as I don't have very much experience 
with Libreoffice's codebase yet.

Hamish McIntyre-Bhatty


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.