Bug 552615 - 4 test failures on ep414I-unit-cen64-gtk3-java13 linux.gtk.x86_64 13
Summary: 4 test failures on ep414I-unit-cen64-gtk3-java13 linux.gtk.x86_64 13
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: APT (show other bugs)
Version: 4.14   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Generic inbox for the JDT-APT component CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-01 05:22 EDT by Vikas Chandra CLA
Modified: 2023-10-15 15:52 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vikas Chandra CLA 2019-11-01 05:22:20 EDT 
testModuleJavaBase4Javac	Failure	expected:<[succeeded]> but was:<[incorrect no of uses, expected 34 but was 33 at apttestprocessors8/org.eclipse.jdt.compiler.apt.tests.processors.elements.Java9ElementProcessor.reportError(Java9ElementProcessor.java:903) at apttestprocessors8/org.eclipse.jdt.compiler.apt.tests.processors.elements.Java9ElementProcessor.assertEquals(Java9ElementProcessor.java:984) at apttestprocessors8/org.eclipse.jdt.compiler.apt.tests.processors.elements.Java9ElementProcessor.testModuleJavaBase4(Java9ElementProcessor.java:481) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:567) at apttestprocessors8/org.eclipse.jdt.compiler.apt.tests.processors.elements.Java9ElementProcessor.invokeTestMethods(Java9ElementProcessor.java:129) at apttestprocessors8/org.eclipse.jdt.compiler.apt.tests.processors.elements.Java9ElementProcessor.process(Java9ElementProcessor.java:104) at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:1023) at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:939) at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1267) at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1381)]>

junit.framework.ComparisonFailure: expected:<[succeeded]> but was:<[incorrect no of uses, expected 34 but was 33
at apttestprocessors8/org.eclipse.jdt.compiler.apt.tests.processors.elements.Java9ElementProcessor.reportError(Java9ElementProcessor.java:903)
at apttestprocessors8/org.eclipse.jdt.compiler.apt.tests.processors.elements.Java9ElementProcessor.assertEquals(Java9ElementProcessor.java:984)
at apttestprocessors8/org.eclipse.jdt.compiler.apt.tests.processors.elements.Java9ElementProcessor.testModuleJavaBase4(Java9ElementProcessor.java:481)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMe
Comment 1 Eclipse Genie CLA 2021-10-22 06:27:43 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2023-10-15 15:52:39 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.