[JIRA] (JENKINS-8636) TestLink Plugin FATAL: Error creating test project
Ruslan Strazhnyk updated JENKINS-8636 TestLink Plugin FATAL: Error creating test project Change By: Ruslan Strazhnyk (13/Mar/13 11:24 AM) Environment: HudsonrunningonLinux(Ubuntu10.04LTS)withTestLink(1.9RC1)onthesamebox. Jenkinsver.1.499,TestLink1.9.5andTestlinkplugin3.1.8 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 -- 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/groups/opt_out.
[JIRA] (JENKINS-8636) TestLink Plugin FATAL: Error creating test project
Ruslan Strazhnyk reopened JENKINS-8636 TestLink Plugin FATAL: Error creating test project The same problem is reproducible on Jenkins ver. 1.499, TestLink 1.9.5 and Testlink plugin 3.1.8 Change By: Ruslan Strazhnyk (23/Jan/13 3:55 PM) Resolution: NotADefect Status: Closed 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-8636) TestLink Plugin FATAL: Error creating test project
Ruslan Strazhnyk edited a comment on JENKINS-8636 TestLink Plugin FATAL: Error creating test project The same problem is reproducible on Jenkins ver. 1.499, TestLink 1.9.5 and Testlink plugin 3.1.8 Preparing TestLink client API. Using TestLink URL: http:///testlink/lib/api/xmlrpc.php FATAL: Error verifying developer key: Failed to parse server's response: The processing instruction target matching "[xX][mM][lL]" is not allowed. br.eti.kinoshita.testlinkjavaapi.util.TestLinkAPIException: Error verifying developer key: Failed to parse server's response: The processing instruction target matching "[xX][mM][lL]" is not allowed. at br.eti.kinoshita.testlinkjavaapi.MiscService.checkDevKey(MiscService.java:66) at br.eti.kinoshita.testlinkjavaapi.TestLinkAPI.init(TestLinkAPI.java:162) at hudson.plugins.testlink.TestLinkBuilder.getTestLinkSite(TestLinkBuilder.java:244) at hudson.plugins.testlink.TestLinkBuilder.perform(TestLinkBuilder.java:134) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:592) at hudson.model.Run.execute(Run.java:1543) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: org.apache.xmlrpc.client.XmlRpcClientException: Failed to parse server's response: The processing instruction target matching "[xX][mM][lL]" is not allowed. at org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTransport.java:188) at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:156) at org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:143) at org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTransport.java:69) at org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:56) at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:167) at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:158) at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:147) at br.eti.kinoshita.testlinkjavaapi.BaseService.executeXmlRpcCall(BaseService.java:90) at br.eti.kinoshita.testlinkjavaapi.MiscService.checkDevKey(MiscService.java:62) ... 12 more Caused by: org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 6; The processing instruction target matching "[xX][mM][lL]" is not allowed. at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1234) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525) at org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTransport.java:186) 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-13214) Tests with the same name are no longer reported in the test results
[ https://issues.jenkins-ci.org/browse/JENKINS-13214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161324#comment-161324 ] Ruslan Strazhnyk edited comment on JENKINS-13214 at 4/6/12 8:45 AM: Greg, I disagree. The same happens when gather result with Publish JUnit test result report option. So the bug is not in the plugins, but in Jenkins code was (Author: desperado): Greg, I disagree. The same happens when gather result with Publish JUnit test result report option. Tests with the same name are no longer reported in the test results --- Key: JENKINS-13214 URL: https://issues.jenkins-ci.org/browse/JENKINS-13214 Project: Jenkins Issue Type: Bug Components: maven2 Affects Versions: current Reporter: ajbanck Assignee: kutzi Attachments: xml_result.zip After updating from 1.425 to 1.456 test results will only show one test for tests having the same name. Test set having tests executed with parameters: ... ..Executing TestMyTest#testDefault(true) ..Executing TestMyTest#testDefault(false) .Finished test set [Unit Tests] on Fri Mar 23 12:26:08 CET 2012. Executed [132] tests. Resulting test results: xml ... testcase time=0.047 classname=TestMyTest name=testDefault/ testcase time=0.043 classname=TestMyTest name=testDefault/ /testsuite In version 1.425 the 132 test results where correctly displayed. In version 1.456 the test results page is only having one entry for these tests, total amount of tests reported is no longer valid and is the count per test method and not the count of tests actually executed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13214) Tests with the same name are no longer reported in the test results
[ https://issues.jenkins-ci.org/browse/JENKINS-13214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruslan Strazhnyk updated JENKINS-13214: --- Attachment: xml_result.zip Yes, here it is. I run one testfile with a couple of config files, and though name of the test is the same, but any of them could fail. So I need statistic for each of them. In Jenkins I gather result through Publish Test Results in Labeled Groups with report file mask test-reports/*.xml. It worked until the changes in v 1.452 Tests with the same name are no longer reported in the test results --- Key: JENKINS-13214 URL: https://issues.jenkins-ci.org/browse/JENKINS-13214 Project: Jenkins Issue Type: Bug Components: maven2 Affects Versions: current Reporter: ajbanck Assignee: kutzi Attachments: xml_result.zip After updating from 1.425 to 1.456 test results will only show one test for tests having the same name. Test set having tests executed with parameters: ... ..Executing TestMyTest#testDefault(true) ..Executing TestMyTest#testDefault(false) .Finished test set [Unit Tests] on Fri Mar 23 12:26:08 CET 2012. Executed [132] tests. Resulting test results: xml ... testcase time=0.047 classname=TestMyTest name=testDefault/ testcase time=0.043 classname=TestMyTest name=testDefault/ /testsuite In version 1.425 the 132 test results where correctly displayed. In version 1.456 the test results page is only having one entry for these tests, total amount of tests reported is no longer valid and is the count per test method and not the count of tests actually executed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13214) Tests with the same name are no longer reported in the test results
[ https://issues.jenkins-ci.org/browse/JENKINS-13214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161223#comment-161223 ] Ruslan Strazhnyk commented on JENKINS-13214: Got the same problem. It is broken from 1.455 Tests with the same name are no longer reported in the test results --- Key: JENKINS-13214 URL: https://issues.jenkins-ci.org/browse/JENKINS-13214 Project: Jenkins Issue Type: Bug Components: maven2 Affects Versions: current Reporter: ajbanck After updating from 1.425 to 1.456 test results will only show one test for tests having the same name. Test set having tests executed with parameters: ... ..Executing TestMyTest#testDefault(true) ..Executing TestMyTest#testDefault(false) .Finished test set [Unit Tests] on Fri Mar 23 12:26:08 CET 2012. Executed [132] tests. Resulting test results: xml ... testcase time=0.047 classname=TestMyTest name=testDefault/ testcase time=0.043 classname=TestMyTest name=testDefault/ /testsuite In version 1.425 the 132 test results where correctly displayed. In version 1.456 the test results page is only having one entry for these tests, total amount of tests reported is no longer valid and is the count per test method and not the count of tests actually executed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13214) Tests with the same name are no longer reported in the test results
[ https://issues.jenkins-ci.org/browse/JENKINS-13214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161223#comment-161223 ] Ruslan Strazhnyk edited comment on JENKINS-13214 at 4/4/12 12:51 PM: - Got the same problem. It is broken from 1.453 Still works good on 1.452 - I discovered it afer series of downgrades was (Author: desperado): Got the same problem. It is broken from 1.455 Tests with the same name are no longer reported in the test results --- Key: JENKINS-13214 URL: https://issues.jenkins-ci.org/browse/JENKINS-13214 Project: Jenkins Issue Type: Bug Components: maven2 Affects Versions: current Reporter: ajbanck After updating from 1.425 to 1.456 test results will only show one test for tests having the same name. Test set having tests executed with parameters: ... ..Executing TestMyTest#testDefault(true) ..Executing TestMyTest#testDefault(false) .Finished test set [Unit Tests] on Fri Mar 23 12:26:08 CET 2012. Executed [132] tests. Resulting test results: xml ... testcase time=0.047 classname=TestMyTest name=testDefault/ testcase time=0.043 classname=TestMyTest name=testDefault/ /testsuite In version 1.425 the 132 test results where correctly displayed. In version 1.456 the test results page is only having one entry for these tests, total amount of tests reported is no longer valid and is the count per test method and not the count of tests actually executed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12457) 'Age' column on 'Test Result' tab may show incorrect value when a test suite divided into multiple junit files
[
https://issues.jenkins-ci.org/browse/JENKINS-12457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruslan Strazhnyk reopened JENKINS-12457:
'Age' column on 'Test Result' tab may show incorrect value when a test suite
divided into multiple junit files
--
Key: JENKINS-12457
URL: https://issues.jenkins-ci.org/browse/JENKINS-12457
Project: Jenkins
Issue Type: Improvement
Components: junit
Affects Versions: current
Reporter: Greg Temchenko
Assignee: kutzi
Somebody described the problem a year ago here:
http://jenkins.361315.n4.nabble.com/Problem-with-Age-column-on-Test-Results-tab-td3172208.html
{quote}
I have a problem with 'Age' column on 'Test Results' tab. For couple of my
tests, all the time this column has value equals '1', despite the fact that
those tests start failing earlier than one build ago. When I switch to
'History' tab, in 'Test Result' column there is a 'Regression' value for all
builds, and it should be 'Regression' value only for the first build and
'Failed' for next builds.
{quote}
For me this happens because I have many junit xmls that containing the same
test suite name.
In this case hudson.tasks.junit.CaseResult.getPreviousResult() gets the only
last junit xml result and if it's not failed then the Age column won't be
calculated properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12457) 'Age' column on 'Test Result' tab may show incorrect value when a test suite divided into multiple junit files
[
https://issues.jenkins-ci.org/browse/JENKINS-12457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161226#comment-161226
]
Ruslan Strazhnyk commented on JENKINS-12457:
Seems like fix is defective - See JENKINS-13214
'Age' column on 'Test Result' tab may show incorrect value when a test suite
divided into multiple junit files
--
Key: JENKINS-12457
URL: https://issues.jenkins-ci.org/browse/JENKINS-12457
Project: Jenkins
Issue Type: Improvement
Components: junit
Affects Versions: current
Reporter: Greg Temchenko
Assignee: kutzi
Somebody described the problem a year ago here:
http://jenkins.361315.n4.nabble.com/Problem-with-Age-column-on-Test-Results-tab-td3172208.html
{quote}
I have a problem with 'Age' column on 'Test Results' tab. For couple of my
tests, all the time this column has value equals '1', despite the fact that
those tests start failing earlier than one build ago. When I switch to
'History' tab, in 'Test Result' column there is a 'Regression' value for all
builds, and it should be 'Regression' value only for the first build and
'Failed' for next builds.
{quote}
For me this happens because I have many junit xmls that containing the same
test suite name.
In this case hudson.tasks.junit.CaseResult.getPreviousResult() gets the only
last junit xml result and if it's not failed then the Age column won't be
calculated properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
