DesktopLOKTest::testRedlineWriter is failing
sbergman at redhat.com
Fri Nov 10 09:39:43 UTC 2017
On 11/10/2017 10:17 AM, Tomáš Chvátal wrote:
> 2017-11-06 9:58 GMT+01:00 Stephan Bergmann <sbergman at redhat.com
> <mailto:sbergman at redhat.com>>:
> Looking at the surrounding code
> // Get redline info.
> boost::property_tree::ptree aTree;
> char* pJSON =
> std::stringstream aStream(pJSON);
> boost::property_tree::read_json(aStream, aTree);
> // Make sure that pressing a key creates exactly one redline.
> what's the binary content of that "char* pJSON" stream? If that's
> still intact, then it's apparently boost::property_tree::read_json
> that's breaking things. And if that's already garbled, then it's
> apparently the producer side of that
> pDocument->m_pDocumentClass->getCommandValues (whatever that is)
> that is breaking it and needs further investigation.
> I checked the read_json function and it was indeed rewritten in between
> the boost versions on the distro (and there were some comments about
> unicode support). So I had updated the boost function (basically to use
> latest boost code) in my testing repo and it still fails:
> [ 6427s] /home/abuild/rpmbuild/BUILD/libreoffice-22.214.171.124/desktop/qa/desktop_lib/test_desktop_lib.cxx:1660:DesktopLOKTest::testRedlineWriter
> [ 6427s] equality assertion failed
> [ 6427s] - Expected: Insert “t”
> [ 6427s] - Actual : Insert â€œtâ€
> FWIW I enabled it on the OBS so the full build log is tracked here:
> Any idea how to check the getCommandValues behaviour if it is the proper
so, again, "what's the binary content of that "char* pJSON" stream?"
can't you just dump it in gdb?
More information about the LibreOffice