Build #2

Plan branch:

Build: #2 failed Changes by 5 people

Build result summary

Details

Completed
Duration
2 minutes
Labels
None
Revision
0fac5e54c6e1a22da0d882d2d60495a6da161418
Failing since
#1 (First build for this plan – )
No failed test found. A possible compilation error occurred.

Responsible

This build has been failing since #1
No one has taken responsibility

Code commits

Author Commit Message Commit date
Mike Beckerle Mike Beckerle 0fac5e54c6e1a22da0d882d2d60495a6da161418 Clean up some tdml issues before modifying tdml runner to support bitOrder.
Added test for Scala's trim showing that it is faulty.

Created our own trim replacement.
Mike Beckerle Mike Beckerle 579c14123ba380dac9a0b28b8aeb2675203e237b Changes to make CR (0xD) character appear as 0xE00D character in the DFDL infoset.
Turns out XML eats CRLFs and replaces them with LF, and converts
isolated CR to LF. So while CR is legal in XML, it's never
part of the XML Infoset.

So, in order to support it as part of the DFDL infoset, we have
to treat it like the xml illegal chars and map it into the Unicode
PUA area. Hence, 0xE00D, not 0xD.

Also some test changes to better characterize the odd (buggy)
behavior of scala.xml.Utility.trim() that the TDML runner calls.

Turns out this does more than collapse whitespaces. It seems to
flat out remove them in some cases.

Also there's a scala bug in that xml ' is not supported.

The test testChars2 illustrates how, in a TDML file, you can
represent all 256 bytes of iso-8859-1 in data, and how you can
represent those same characters in a tdml expected infoset value.

Converted a large number of tdml and xsd files to use Unix line endings
not Windows CRLF style. Verified that there are no regressions due to
this change. This eliminates line-ending sensitivities where the tdml
file contained data inside CDATA regions which happened to have Windows
line-endings, in that case the CRs seem to be preserved into the data,
and as a result tests were wanting to see 0xE00D in the result.

This is too fragile - line-endings are usually invisible. So having a
tdml file depend on being saved in Windows CRLF style in order for the
tests to work is problematic.

DFDL-941, DFDL-938
Mike Beckerle Mike Beckerle d47e2f9ea449a15c05b6b11748dd71760a33576d update gitignore to ignore eclipse-projects/*/lib directories (which are supposed to be eclipse symlinks to the real project lib directory.)
Mike Beckerle Mike Beckerle cdfb898923508809c3fd2e75645f22cfb2e63624 Changes to add bitOrder property needed for support of MIL-STD-2045-47001D format.
DFDL-896
Mike Beckerle Mike Beckerle d385fc4b577c5d52b914c7f138266c0bac365a8f Computation of termsUntilFirstRequiredTerm had bug.

61 more changes...

Jira issues

IssueDescriptionStatus
34 more issues…
Unknown Issue TypeDFDL-174Could not obtain issue details from Jira
Unknown Issue TypeDFDL-299Could not obtain issue details from Jira
Unknown Issue TypeDFDL-319Could not obtain issue details from Jira
Unknown Issue TypeDFDL-400Could not obtain issue details from Jira
Unknown Issue TypeDFDL-419Could not obtain issue details from Jira

Error summary for build, test, publish

The job generated some errors, drill down into the full build log for more details.

Could not find test result reports in the /home/opensource/data/bamboo/xml-data/build-dir/DFDL-REV3-JOB1 directory.