xml issues with oprofile-1.0.0-rc1

[William C. <wc...@re...>]

On 08/28/2014 01:22 PM, Maynard Johnson wrote:
> On 08/28/2014 11:11 AM, William Cohen wrote:

> Will,
> Many thanks for all the testing you've done!  I will defer to Will Deacon on the problem with running operf/ocount on cortex-a9, but I have answers for the XML-related test failures for you.  See below.
>>
>> -Will
>>
>> (1)
>> Running ./oprofile-operf/oprofile-operf-run.exp ...
>> FAIL:     XML opreport output with callgraph option=1 is invalid
>> warning: failed to load external entity "/share/doc/oprofile/opreport.xsd"
>> Schemas parser error : Failed to locate the main schema resource at '//share/doc
>> /oprofile/opreport.xsd'.
> Coincidentally, I have recently seen this error reported to me by one of my IBM colleagues when testing the RC1 on ubuntu.  Turned out that, for some reason, the deb package had opreport.xsd installed as a tar file (opreport.xsd.gz) instead of plain text.  Probably something like that happening here, too -- or simply missing from the install.

There does seems to be an opreport.xsd installed by the rpm, but it looks like something is looking in the wrong place, /share/doc/oprofile.xsd:

$ rpm -qs oprofile|grep xsd
normal        /usr/share/doc/oprofile/ophelp.xsd
normal        /usr/share/doc/oprofile/opreport.xsd

The wierd thing is that on one f20 x86_64 machine it is working, but on another it doesn't.

>>
>> (2)
>> Running ./oprofile-operf/oprofile-operf-run.exp ...
>> FAIL:     XML opreport output with callgraph option=1 is invalid
>> out.xml:19: element count: Schemas validity error : Element 'count': This element is not expected. Expected is one of ( symbol, module ).
>> out.xml fails to validate
> This is exactly the error you'd see if a new XML instance doc was being validated against an old schema (e.g, from 0.9.9).  There was a fix to the cardinality of the 'count' field in the opreport schema (fixed in bug 236) for release 1.0.0.
>       opreport schema: Fix count field maxOccurs (changed to 'unbounded')
> Somehow, the testsuite is finding an old opreport schema instead of the new 1.0.0 schema file.

It might be using the something in /usr/local/. I went through and removed the various oprofile stuff in /usr/local/. I then found that there was /usr/share/doc/oprofile and /usr/share/oprofile/doc/oprofile-1.0.0git.  I copied over the newer files in /usr/share/doc/oprofile-1.0.0git into /usr/share/doc/oprofile.  The tests are now happy on that machine.



-Will