[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Stéphane Nicoll commented on JENKINS-15895 Job stuck collecting compiler warnings with the eclipse compiler it does work with only the Javac compiler as the problem is in the eclipse parser it seems. I can only use the Javac compiler and I get a proper list of warnings. Thanks! (Hint: maybe we should document somewhere that Maven-based jobs using the jdt compiler do not need to use the eclipse parser) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Ulli Hafner commented on JENKINS-15895 Job stuck collecting compiler warnings with the eclipse compiler Well, actually the warnings are different if you build with maven and tycho (then you need the Eclipse parser...). But I think it would be worth adding a note in the documentation at least. Are you using a maven job or freestyle job to build your project? Currently there is no special support for maven jobs in my plug-in, maybe I should add that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Ulli Hafner reopened JENKINS-15895 Job stuck collecting compiler warnings with the eclipse compiler Change By: Ulli Hafner (27/Nov/12 8:56 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Ulli Hafner resolved JENKINS-15895 as Fixed Job stuck collecting compiler warnings with the eclipse compiler I create JENKINS-15933 as a followup for this issue. Change By: Ulli Hafner (27/Nov/12 8:54 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Ulli Hafner resolved JENKINS-15895 as Wont Fix Job stuck collecting compiler warnings with the eclipse compiler Setting the resolution to won't fix since there is almost no way to improve the speed of the multi-line Eclipse parser. Change By: Ulli Hafner (27/Nov/12 8:57 AM) Status: Reopened Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Stéphane Nicoll commented on JENKINS-15895 Job stuck collecting compiler warnings with the eclipse compiler I am using a maven-based job. According to JENINS-15933, eclipse would be detected automatically as far as I understand. That's probably not what I want. By the way, I am not so sure that it's a performance problem, really. Parsing 4000 lines in more than 2 hours, something must definitely be wrong. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Ulli Hafner commented on JENKINS-15895 Job stuck collecting compiler warnings with the eclipse compiler I need something like the following snipped from YOUR console log: compile-warning: [mkdir] Created dir: C:\Desenvolvimento\Java\jfg\build\build\warning [javac] Compiling 34 source files to C:\Desenvolvimento\Java\jfg\build\build\warning [javac] -- [javac] 1. WARNING in C:\Desenvolvimento\Java\jfg\src\jfg\AttributeException.java (at line 3) [javac] public class AttributeException extends RuntimeException [javac] ^^ [javac] The serializable class AttributeException does not declare a static final serialVersionUID field of type long [javac] -- [javac] -- [javac] 2. WARNING in C:\Desenvolvimento\Java\jfg\src\jfg\gui\swt\SWTTextBuilder.java (at line 85) [javac] protected void addValidation(Text text, Object type) [javac] [javac] The parameter text is never read Then I need to know, if the path in a warning above is relative (contains no C: or / in the beginning) or absolute. If you would paste one of your actual warnings I will see it anyway... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Ulli Hafner commented on JENKINS-15895 Job stuck collecting compiler warnings with the eclipse compiler And the thread dump is still missing This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Stéphane Nicoll commented on JENKINS-15895 Job stuck collecting compiler warnings with the eclipse compiler [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ com.bsb.fluid.core.ui-incubator --- [INFO] Compiling (JDT) 26 source files to C:\stuff\ci\jenkins\jobs\incubator-fluid\workspace\core\com.bsb.fluid.core.ui-incubator\target\test-classes [WARNING] C:\stuff\ci\jenkins\jobs\incubator-fluid\workspace\core\com.bsb.fluid.core.ui-incubator\target\generated-sources\test-annotations\com\bsb\fluid\test\core\ui\task\MDummyPersonCrudTaskController.java:[34,0] Type safety: Unchecked invocation cast(PathFactory) of the generic method cast(PathFactoryA) of type BasePathDummyPersonCrudTaskController [WARNING] C:\stuff\ci\jenkins\jobs\incubator-fluid\workspace\core\com.bsb.fluid.core.ui-incubator\target\generated-sources\test-annotations\com\bsb\fluid\test\core\ui\task\MDummyPersonCrudTaskController.java:[34,0] Type safety: The _expression_ of type MDefaultCrudTaskController needs unchecked conversion to conform to MDefaultCrudTaskControllerPerson,InMemoryCrudTaskEntityHandlerPerson [WARNING] C:\stuff\ci\jenkins\jobs\incubator-fluid\workspace\core\com.bsb.fluid.core.ui-incubator\target\generated-sources\test-annotations\com\bsb\fluid\test\core\ui\task\MDummyPersonCrudTaskController.java:[34,0] Type safety: Unchecked invocation type(ClassPerson, ClassInMemoryCrudTaskEntityHandler) of the generic method type(ClassMT, ClassMH) of type MDefaultCrudTaskController [WARNING] C:\stuff\ci\jenkins\jobs\incubator-fluid\workspace\core\com.bsb.fluid.core.ui-incubator\target\generated-sources\test-annotations\com\bsb\fluid\test\core\ui\task\MDummyPersonCrudTaskController.java:[34,0] Type safety: The _expression_ of type PathFactory needs unchecked conversion to conform to PathFactoryMDefaultCrudTaskControllerPerson,InMemoryCrudTaskEntityHandlerPerson mojoSucceeded org.apache.maven.plugins:maven-compiler-plugin:2.3.2(default-testCompile) mojoStarted org.apache.maven.plugins:maven-surefire-plugin:2.12(default-test) [INFO] This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Stéphane Nicoll commented on JENKINS-15895 Job stuck collecting compiler warnings with the eclipse compiler Sorry it took so long to get those info. Let me know if you need anything else. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Ulli Hafner commented on JENKINS-15895 Job stuck collecting compiler warnings with the eclipse compiler Ok, thanks, seems that the problem is unrelated to JENKINS-10097. The process "hangs" while scanning for warnings using a regular _expression_ matcher. How large is your console log? The eclipse parsers is a slow multi-line parser that reads the whole console log into a buffer. Would it be possible to pipe the warnings to an additional file? BTW: I think you do not need to activate the Eclipse parser, since the warnings seems to be in the default javac format (due to the maven plugin). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Stéphane Nicoll commented on JENKINS-15895 Job stuck collecting compiler warnings with the eclipse compiler 350kb. After 1h15, it is still on at hudson.plugins.warnings.parser.RegexpParser.findAnnotations(RegexpParser.java:86) Seems a lot for ~4000 lines This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Ulli Hafner commented on JENKINS-15895 Job stuck collecting compiler warnings with the eclipse compiler Can you please check if that happens with the plain Java parser, too? Or why are you using the Eclipse Parser? Are there warnings not covered? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Stéphane Nicoll updated JENKINS-15895 Job stuck collecting compiler warnings with the eclipse compiler The compiler warnings. They all relates to Java source files. I don't know what you mean by relative path. Change By: Stéphane Nicoll (26/Nov/12 7:52 AM) Attachment: compiler-warnings.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Stéphane Nicoll updated JENKINS-15895 Job stuck collecting compiler warnings with the eclipse compiler Change By: Stéphane Nicoll (26/Nov/12 7:54 AM) Attachment: compiler-warnings-2.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Stéphane Nicoll updated JENKINS-15895 Job stuck collecting compiler warnings with the eclipse compiler Change By: Stéphane Nicoll (23/Nov/12 1:18 PM) Summary: Jobstuck collection collecting compilerwarningswiththeeclipsecompiler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15895) Job stuck collecting compiler warnings with the eclipse compiler
Ulli Hafner commented on JENKINS-15895 Job stuck collecting compiler warnings with the eclipse compiler For thread dumps see: https://wiki.jenkins-ci.org/display/JENKINS/Build+is+hanging Do the warnings contain relative paths? Can you please show a single warning? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
