Re: [ajdt-dev] Test failures

[Andrew Eisenberg <andrew@xxxxxxxxxxxx>]

That's strange.  It's one of those tests that was written a long time
ago and has been passing on the build server for a long time.  I don't
often run the full suite locally since it takes so long.  But, I did
run this test and it is failing for me in the same way it is for you.

When I tried to recreate a similar file in a runtime workspace, I
couldn't reproduce the problem. I'm going to do some more exploring.
I don't think that this is a big problem since all tests are passing
on the build server and I can't find anyway to exhibit this
problematic behavior locally.  Most likely there is some kind of race
condition being found in the tests when run outside the build server.
I'll explore deeper.


On Mon, Dec 13, 2010 at 3:09 PM, F.A. Bourbonnais <fab.lists@xxxxxxxxxxx> wrote:
>> Looking in there, it seems like there is 1 failing test.
>> AspectRenameRefactoringTests.testRenamePointcut1.  All other failing
>> tests are not relevant.
>
> After an update and running only AllUITests suite, I have only one
> failure (testAJHandlerIdentifiers).
>
> JUnit test results are attached.
>
>> ps- if you are brave enough to run the AJDT UI tests, then you should
>> be running the AllUITests suite.  Please let me know what the results
>> are.
>
> I will do that this night or tomorrow.
>
>
>> On Mon, Dec 6, 2010 at 1:13 PM, F.A. Bourbonnais <fab.lists@xxxxxxxxxxx> wrote:
>>> Hi,
>>>
>>> I downloaded the head from the CVS of AJDT and AspectJ. But I have
>>> several failures while running tests and some build problems:
>>>
>>>
>>> 1. I have 11 failures in ajdt.core.tests
>>>
>>>    In short (some are run twice in two suites I think...)
>>>       - TestRenamePointcut1
>>>       - AbstractITDSearchTest
>>>       - 6 in builder.RefreshTests
>>>
>>>   JUnit result is attached in AJDT Core Tests 20101204-175650.xml
>>>
>>>
>>> 2. I tried to execute the test harness for AspectJ but the ant target
>>> "build-harness-jar" doesn't produce the jar "testing-drivers-all.jar".
>>> I do have "testing-drivers.jar" (not -all) and a
>>> "testing-drivers-test-all.jar". The last one seems to do the job but I
>>> have an error about a missing dependency (apache-commons) which may be
>>> voluntarily not added to the jar? Is it the right jar ?
>>>
>>>
>>> 3. So, I tried to run those tests directly into Eclipse by using the
>>> class "org.aspectj.testing.drivers.Harness". Some test runs and after
>>> a short time it fails with some errors:
>>>
>>>    ? Util.write() suid=Test: static final long serialVersionUID =
>>> 179572068006061281L;
>>>    ? Util.fail() ex=java.io.InvalidClassException: Test; local class
>>> incompatible: stream classdesc serialVersionUID = 179572068006061281,
>>> local class serialVersionUID = -5805535058418760185
>>>
>>>    ... many times
>>>
>>>    Complete console output is attached in test-harness-aj_2010-12-06.txt
>>>
>>>
>>> 4. Finally, when I launched JUnit tests for AspectJ, it ends with 6 failures:
>>>
>>>    - org.aspectj.weaver.bcel.TjpWeaveTestCase  (4 failures)
>>>    - JDK 1.5 -
>>> org.aspectj.systemtest.incremental.tools.MultiProjectIncrementalTests
>>> (2 failures)
>>>
>>>    JUnit result is attached in AJ JUnit Tests 20101204-233248.xml.
>>>
>>>
>>> I'm running those tests on an GNU/Linux Ubuntu 10.10 amd64 with
>>> Eclipse 3.6 and Java OpenJDK 64-Bit 1.6.0_20.
>>>
>>>
>>> Thanks,
>>>
>>> _______________________________________________
>>> ajdt-dev mailing list
>>> ajdt-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/ajdt-dev
>>>
>>>
>> _______________________________________________
>> ajdt-dev mailing list
>> ajdt-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/ajdt-dev
>>
>