[Building Sakai] Is trunk of entitybroker building?
Jim Eng
jimeng at umich.edu
Thu Feb 9 13:21:10 PST 2012
I added these three lines just before line 520 and just before what would have been line 534:
System.out.println("========================================================= EntityEncodingManagerTest");
System.out.println(output);
System.out.println("========================================================= EntityEncodingManagerTest");
Then I built again and got this in the console:
========================================================= EntityEncodingManagerTest
<?xml version="1.0" encoding="UTF-8" ?>
<serialize type='bean' size='6'>
<data type='map' size='4'>
<identity>AZ</identity>
<stuff>aaron0</stuff>
<name>aaronz</name>
<tra/>
</data>
<displayTitle>serialize : /serialize/AZ</displayTitle>
<entityId>AZ</entityId>
<entityProperties type='map' size='0'>
</entityProperties>
<entityReference>/serialize/AZ</entityReference>
<entityURL>http://localhost:8080/direct/serialize/AZ</entityURL>
</serialize>
========================================================= EntityEncodingManagerTest
========================================================= EntityEncodingManagerTest
<?xml version="1.0" encoding="UTF-8" ?>
<serialize_collection entityPrefix="serialize">
<serialize type='bean' size='6'>
<data type='map' size='4'>
<identity>AZ</identity>
<stuff>aaron0</stuff>
<name>aaronz</name>
<tra/>
</data>
<displayTitle>Hello1</displayTitle>
<entityId>AZ</entityId>
<entityProperties type='map' size='0'>
</entityProperties>
<entityReference>/serialize/AZ</entityReference>
<entityURL>/direct/serialize/AZ</entityURL>
</serialize>
<serialize type='bean' size='6'>
<data type='map' size='4'>
<identity>CZ</identity>
<stuff>aaron2</stuff>
<name>aaronz</name>
<tra/>
</data>
<displayTitle>Hello2</displayTitle>
<entityId>CZ</entityId>
<entityProperties type='map' size='0'>
</entityProperties>
<entityReference>/serialize/CZ</entityReference>
<entityURL>/direct/serialize/CZ</entityURL>
</serialize>
</serialize_collection>
========================================================= EntityEncodingManagerTest
HTH
Jim
On Feb 9, 2012, at 4:09 PM, Aaron Zeckoski wrote:
> Can you run the test in eclipse and put a breakpoint right at the line
> that is failing and see what the actual output is (compared to what
> the test is expecting)? I think you will be checking the value of the
> XML chunk (variable should be called: )
> The trace doesn't have much helpful info sadly.
> -AZ
>
>
>
> On Thu, Feb 9, 2012 at 3:10 PM, Jim Eng <jimeng at umich.edu> wrote:
>> The log said a test failed, and identified that test. The test results indicated that test failed at line 520. Here are the contents of rest/target/surefire-reports/org.sakaiproject.entitybroker.rest.EntityEncodingManagerTest.txt :
>>
>> -------------------------------------------------------------------------------
>> Test set: org.sakaiproject.entitybroker.rest.EntityEncodingManagerTest
>> -------------------------------------------------------------------------------
>> Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.148 sec <<< FAILURE!
>> testFormatAndOutputEntity(org.sakaiproject.entitybroker.rest.EntityEncodingManagerTest) Time elapsed: 0.022 sec <<< FAILURE!
>> junit.framework.AssertionFailedError: null
>> at junit.framework.Assert.fail(Assert.java:47)
>> at junit.framework.Assert.assertTrue(Assert.java:20)
>> at junit.framework.Assert.assertTrue(Assert.java:27)
>> at org.sakaiproject.entitybroker.rest.EntityEncodingManagerTest.testFormatAndOutputEntity(EntityEncodingManagerTest.java:520)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at junit.framework.TestCase.runTest(TestCase.java:168)
>> at junit.framework.TestCase.runBare(TestCase.java:134)
>> at junit.framework.TestResult$1.protect(TestResult.java:110)
>> at junit.framework.TestResult.runProtected(TestResult.java:128)
>> at junit.framework.TestResult.run(TestResult.java:113)
>> at junit.framework.TestCase.run(TestCase.java:124)
>> at junit.framework.TestSuite.runTest(TestSuite.java:232)
>> at junit.framework.TestSuite.run(TestSuite.java:227)
>> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:79)
>> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
>> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
>> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
>> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
>> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
>> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
>> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
>>
>>
>>
>> On Feb 9, 2012, at 2:46 PM, Aaron Zeckoski wrote:
>>
>>> What's the trace from the failure?
>>> -AZ
>>>
>>>
>>> On Thu, Feb 9, 2012 at 2:39 PM, Jim Eng <jimeng at umich.edu> wrote:
>>>> I wiped my m2 repo, did a fresh checkout of the "sakai-trunk-all" branch, and started to build it. After several minutes, the build failed again with a test failure in exactly the same place. After some trial-and-error, I commented out two lines in entitybroker's EntityEncodingManagerTest file -- lines 520 and 534. Both of these lines say this:
>>>>
>>>> assertTrue(output.contains("xtra"));
>>>>
>>>> The test no longer fails. I have no idea why the test fails on my laptop at those two lines now, and it did not fail last week (and it doesn't fail on Jenkins or on Aaron's laptop). In any event, it looks like this hack will let me work again using the "sakai-trunk-all" branch.
>>>>
>>>> Thanks.
>>>>
>>>> Jim
>>>>
>>>>
>>>> On Feb 8, 2012, at 10:05 AM, Aaron Zeckoski wrote:
>>>>
>>>>> I wiped my maven 2 repo yesterday (for other reasons) and did a
>>>>> complete rebuild of the trunk-all without any issues.
>>>>> We have other Unicon teams building from sakai trunk all daily and
>>>>> they have not reported anything either.
>>>>> Building today looks fine as well for me.
>>>>> -AZ
>>>>>
>>>>>
>>>>> On Wed, Feb 8, 2012 at 9:42 AM, Jim Eng <jimeng at umich.edu> wrote:
>>>>>> The "sakai-trunk-all" branch builds entitybroker from scratch, and that build is now failing for me with a test failure. I notice that the trunk builds on nightly2 build successfully, but I suspect they are using indie jars instead of building everything.
>>>>>>
>>>>>> Has anybody successfully built the "sakai-trunk-all" branch or entitybroker trunk since Thursday?
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> Jim
>>>>>> _______________________________________________
>>>>>> sakai-dev mailing list
>>>>>> sakai-dev at collab.sakaiproject.org
>>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>>>
>>>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>>>
>>>
>>
>
>
>
> --
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120209/4639125e/attachment.html
More information about the sakai-dev
mailing list