You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2018/11/18 18:17:01 UTC

[jira] [Closed] (DERBY-7019) Failure in XMLBindingTest

     [ https://issues.apache.org/jira/browse/DERBY-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas closed DERBY-7019.
--------------------------------

> Failure in XMLBindingTest
> -------------------------
>
>                 Key: DERBY-7019
>                 URL: https://issues.apache.org/jira/browse/DERBY-7019
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.15.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>            Priority: Major
>
> All of a sudden I have started to see a failure in XMLBindingTest on my machine. Via binary search, I have determined that the failure does NOT appear as of revision 1826416, but it does appear in revision 1826417. The checkin at that revision does not seem related:
> {noformat}
> ------------------------------------------------------------------------
> r1826417 | rhillegas | 2018-03-10 08:24:00 -0800 (Sat, 10 Mar 2018) | 1 line
> DERBY-6945: Split generated class directory into separate subdirectories for generated shared, engine, and tools classes; commit derby-6945-22-af-isolateClassesByArtifact.diff.
> {noformat}
> I am confused. Why did this failure suddenly appear? Why does it correspond to that checkin? But that is the evidence I have.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)