[JIRA] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title
Vladimir Sitnikov commented on JENKINS-26971
Re: looking at failed TestNG result causes an exception
{quote}there should be a button that says "Downgrade to X.X". {quote} The sad thing is 1.13 is not compatible with "pipeline"
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title Brian Wilson commented on JENKINS-26971 Re: looking at failed TestNG result causes an exception Our team experienced a similar result and rolled back to 1.13 with no problems. I believe this issue has been reported under another ticket for some time with no action. We are looking at alternatives to TestNG as a result. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title Nalin Makar assigned an issue to Unassigned Jenkins / JENKINS-26971 looking at failed TestNG result causes an exception Change By: Nalin Makar Assignee: Nalin Makar Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title Arun Davis updated an issue Jenkins / JENKINS-26971 looking at failed TestNG result causes an exception Change By: Arun Davis Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title Andrew Newell edited a comment on JENKINS-26971 Re: looking at failed TestNG result causes an exception I have also run into this issue when working with the TestNG plugin locally.[~nullin] I have attached my testng-results.xml file and I can easily reproduce it because every test failure causes this so far.This job was created by me this morning as a Freestyle job.Jenkins version 2 1 . 9 580.1 TestNG plugin version 1.14If you need any information from me I am happy to help, this is blocking some work I'd like to do so please don't hesitate to contact me.Thanks,-Andrew [^HugeJenkinsStacktrace.txt] [^testng-results.xml] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title Andrew Newell commented on JENKINS-26971 Re: looking at failed TestNG result causes an exception I have also run into this issue when working with the TestNG plugin locally. Nalin Makar I have attached my testng-results.xml file and I can easily reproduce it because every test failure causes this so far. This job was created by me this morning as a Freestyle job. Jenkins version 2.9 TestNG plugin version 1.14 If you need any information from me I am happy to help, this is blocking some work I'd like to do so please don't hesitate to contact me. Thanks, -Andrew HugeJenkinsStacktrace.txt testng-results.xml Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title Andrew Newell updated an issue Jenkins / JENKINS-26971 looking at failed TestNG result causes an exception Change By: Andrew Newell Attachment: testng-results.xml Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title Andrew Newell updated an issue Jenkins / JENKINS-26971 looking at failed TestNG result causes an exception Change By: Andrew Newell Attachment: HugeJenkinsStacktrace.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title Cam Spencer commented on JENKINS-26971 Re: looking at failed TestNG result causes an exception Hey Nalin Makar 1) Existing job 2) FreeStyle 3) Jenkins 2.12 4) It's been a few months so I no longer have the testng-results.xml file Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title Nalin Makar commented on JENKINS-26971 Re: looking at failed TestNG result causes an exception I tried reproducing this (with latest plugin code & Jenkins v1.580.1 and 2.12), but couldn't. More concrete information could be useful. Is this issue seen on: 1. on new jobs or existing jobs 2. FreeStyle or Maven or Workflow or doesn't matter.. 3. Jenkins version 4. If possible a copy of the testng-results.xml file The problem is that testngProjAction is being set to null at https://github.com/jenkinsci/testng-plugin-plugin/blob/master/src/main/resources/hudson/plugins/testng/results/MethodResult/reportDetail.groovy#L12 when it shouldn't. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title Peter Nguyen commented on JENKINS-26971 Re: looking at failed TestNG result causes an exception have the same issue, need to roll back to 1.13. Please prioritize this bug. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title Zach David commented on JENKINS-26971 Re: looking at failed TestNG result causes an exception Experiencing the same issues with 1.14, rolled back to 1.10 and working correctly Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title Brian Wilson commented on JENKINS-26971 Re: looking at failed TestNG result causes an exception I rolled back the 1.14 version to 1.13 and the plugin started working again. It looks like 1.14 has some "issues" that need to be addressed quickly. Our environment is RHEL5. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title Brian Wilson commented on JENKINS-26971 Re: looking at failed TestNG result causes an exception I'm also experiencing this same issue, unfortunately the Tester/Developer did not notify me (Buld Engineer) when the issue first started. I'm going to try to debug this tomorrow and will roll back to the previous revision (currently on 1.14, will roll back to 1.13). I'll post the results when I have them. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title Cam Spencer commented on JENKINS-26971 Re: looking at failed TestNG result causes an exception Hey Nalin Makar, I did a rollback from 1.14 to 1.13, and the exception was not thrown when I went to look at the same testNG failure that previously threw an exception. It's possible this issue was resolved in previous versions and then re-introduced in the latest changes (1.14). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26971) looking at failed TestNG result causes an exception
Title: Message Title Cam Spencer commented on JENKINS-26971 Re: looking at failed TestNG result causes an exception I've experienced this issue with Jenkins 2.12, and testng-plugin 1.14 java.lang.RuntimeException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Users/tdjenkins/.jenkins/war/WEB-INF/lib/jenkins-core-2.12.jar!/lib/layout/layout.jelly:258:25: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Users/tdjenkins/.jenkins/war/WEB-INF/lib/jenkins-core-2.12.jar!/lib/layout/main-panel.jelly:36:21: org.apache.commons.jelly.JellyTagException: Cannot get property 'escapeExceptionMsg' on null object at org.kohsuke.stapler.jelly.groovy.JellyBuilder.doInvokeMethod(JellyBuilder.java:280) at org.kohsuke.stapler.jelly.groovy.Namespace$ProxyImpl.invoke(Namespace.java:92) at com.sun.proxy.$Proxy58.layout(Unknown Source) at lib.LayoutTagLib$layout.call(Unknown Source) at hudson.plugins.testng.results.MethodResult.index.run(index.groovy:8) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:74) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:62) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:55) at org.kohsuke.stapler.jelly.groovy.GroovyFacet.handleIndexRequest(GroovyFacet.java:121) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at
