Tomáš Chvátal
Tomáš Chvátal
It is not a specific in a form of a patch for SUSE. We just enforce `-werror=return-type` as it leads otherwise to quite bad behaviour if that unreachable case happens....
Looking at the code it indeed looks fine. The traceback for the crash: ``` Program received signal SIGSEGV, Segmentation fault. damerau_levenshtein_distance (s1=0xf74d5010 L'a' ..., s2=0xf7411010 L'b' ..., len1=200000, len2=200000) at...
Valgrind output with >1GB allocation attempt: ``` >>> print(damerau_levenshtein_distance('a' * 200000, 'b' * 200000)) ==4532== Warning: set address range perms: large range [0x5a18028, 0x46909438) (undefined) ==4532== Invalid write of size...
I forgot to mention we are talking about the precise-runner-0.3.1 here.
Generated package as a proof of concept: https://build.opensuse.org/package/show/LibreOffice:Factory/QR-Code-generator
@lwhsu rebased.
This is also FilesCheck, it makes sense to inspect this after it is redone and cleaned up.
We will never use that dependency generator in openSUSE, we can't and won't do those cycles that it causes. There are 2 cases: 1. tests are directly in site-pacakges/tests so...
It does not make much sense to be there at all. You won't be ever able to install it from there as it has deps on direct rpm bindings and...
In signature check we have test that outputs whitespace garbage while it should not and should be part of the signature check: ```apache-commons-collections-testframework-javadoc.noarch: E: no-signature You have to include your...