You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/01/16 12:38:20 UTC

[GitHub] [camel-quarkus] geoand commented on a change in pull request #603: WIP - Prepare for Quarkus 1.2

geoand commented on a change in pull request #603: WIP - Prepare for Quarkus 1.2
URL: https://github.com/apache/camel-quarkus/pull/603#discussion_r367394790
 
 

 ##########
 File path: integration-tests/http/pom.xml
 ##########
 @@ -122,13 +135,30 @@
                                     <goal>native-image</goal>
                                 </goals>
                                 <configuration>
-                                    <reportErrorsAtRuntime>false</reportErrorsAtRuntime>
+                                    <!--
+                                        With GraalVM Version 19.3.1 CE this test fails with:
+
+                                            Fatal error: com.oracle.graal.pointsto.util.AnalysisError$ParsingError: Error encountered
+                                            while parsing com.oracle.svm.reflect.ClassLoader_defineClass_c6c343b4d6dc22ca64eb2d8503b13ac9c340dcb3.invoke(java.lang.Object, java.lang.Object[])
+
+                                            Parsing context:
+                                                parsing java.lang.reflect.Method.invoke(Method.java:498)
+                                                parsing org.apache.camel.support.ObjectHelper.invokeMethod(ObjectHelper.java:182)
+                                                parsing org.apache.camel.main.BaseMainSupport.loadConfigurations(BaseMainSupport.java:467)
+                                                parsing org.apache.camel.main.BaseMainSupport.postProcessCamelContext(BaseMainSupport.java:522)
+
+                                        but it looks like the stack trace is unrelated to the actual error as that method
+                                        is invoked also in other tests hence I've enable reporting error at runtime to
+                                        get the test succeed.
+
+                                        TODO: investigate what is the real issue
+                                    -->
+                                    <reportErrorsAtRuntime>true</reportErrorsAtRuntime>
 
 Review comment:
   Yeah, I think we should do that. It will it easier to reproduce the actual problem

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services