bulia byak wrote:
On Sun, Jan 11, 2009 at 9:47 AM, Jasper van de Gronde <th.v.d.gronde@...528...> wrote:
The bad news: we have three tests that crash at the moment (introduced between 2008-12-28 and 2009-01-04)
I tried to reproduce the crash of https://bugs.launchpad.net/inkscape/+bug/181995 but could not - it loads fine for me and exports to png from command line without problems. Can you also include in the table the exact command line you use, so these crashes could be easily reproduced?
I just use the runtests.py from SVN, it's not a manually run test. But at the end of this mail I included the relevant part of the executionlog (including the exact command line used).
However, I clearly have been too busy with other things for a while (and have been using the command line too much), as currently Inkscape crashes for me as soon as I start it! (I made a clean build today, and do so for each test run.) I'll try to have a closer look tomorrow to see what the problem is. "Hopefully" it's just a local problem.
- Any additional tests (based on bug reports for example) would
obviously be welcome.
I will certainly contribute some of the most demanding and bug-prone SVGs from my collection, and I urge others to do the same.
Sounds good :) Note that for references you can either include one or more pngs (for failure and/or pass cases) and/or a "patch" file, which is a simpler SVG file that should yield the exact same output. This can even be useful when you know that in practice it won't produce the exact same output, to help judge the results (for example, for feComposite I did this).
- I'd love to be able to link a bug report to a certain fail result
(linking it to a file is probably not a good idea, as one test may exhibit different bugs over time).
Right now I see links to both in the table.
A few files are based on specific bug reports, and they link to the bug report so you can easily see what it's about, but especially for other files it might make more sense to link specific failures to bugs. (Also, at the moment I don't even have a way to link arbitrary files to bugs, as the links are simply generated based on the test name, so even doing that could be an improvement.)
----------- Begin Quote ----------- Executing: tester "inkscape -e "E:\Inkscape\gsoc-testsuite\tester.\output\bugs\bug181995.png" "E:\Inkscape\gsoc-testsuite\tester.\testcases\bugs\bug181995.svg"" "E:\Inkscape\gsoc-testsuite\tester.\output\bugs\bug181995.png" -compare perceptualdiff.exe -pass "E:\Inkscape\gsoc-testsuite\tester.\references\pass\bugs\bug181995-1.png" -pass "E:\Inkscape\gsoc-testsuite\tester.\references\pass\bugs\bug181995-2.png" -fail "E:\Inkscape\gsoc-testsuite\tester.\references\fail\bugs\bug181995.png" ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Background RRGGBBAA: ffffff00 Area 0:0:300:150 exported to 300 x 150 pixels (90 dpi) Bitmap saved as: E:\Inkscape\gsoc-testsuite\tester.\output\bugs\bug181995.png ** Message: Error: Er is een interne fout opgetreden in Inkscape. Het programma wordt afgesloten.
RegistryTool: Could not set the value 'e:\inkscape\trunk\inkscape\inkscape.exe'
Emergency save activated! Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. ----------- End Quote -----------