<?xml ver="blah"?>
<sections>
    <build>
        <field name="build time"></field>
        <!--
            This a non-delimited section of text that will be parsed .
+..
        -->
        <fields type="section of text 1">
        <!--
            A token-delimited section of text that will be parsed into
+ this area...
        -->
        </fields>
    </build>
    <run>
        <errors>
            <error time="some_integer" some_attr="more helpful info ab
+out error gets put here" />
            <!--
                ... etc
            -->
        </errors>
        <mismatches>
            <mismatch time="another_integer" some_attr="more helpful i
+nfo about mismatch goes here" />
            <!--
                ... etc
            -->
        </mismatches>
        <perf_stats>
            <stat type="performance item name">value</stat>
            <!--
                stats about speed, test time, etc go here ...
            -->
        </perf_stats>
    </run>
</sections>

[download]

Extra notes (about flat logs): - Flat logs which are parsed are 400~100k lines large. - Current system uses sections of text vs a 'gold log' (good existing known output), and does either specialized subset field checking or straight diff(1)'ing. This unfortunately is a bad idea with a large number of tests because the number of logs is ( 1000 tests * (1-2 logs) * (1-3 test sets) ) => 1000 ~ 6000 logs. So, if the file format changes (i.e. a new feature is introduced to the toolchain) so will all affected logs, and bringing the 'gold logs' up to date will consume a lot of unnecessary time, and this is going to occur in the future.

Thus, by moving to a more structured data store, I can get away from the flat file's formats and get to a content based comparison system.

In reply to Re^4: Perl has plenty of XML parsers, but is there an XML printer? by yaneurabeya
in thread Perl has plenty of XML parsers, but is there an XML printer? by yaneurabeya

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.