Community
Participate
Working Groups
Some Bugzilla tests are still failing due to changes to the test infrastructure. A initial set of headless tests has been fixed as part of bug 287226 but the remaining tests still need to be ported.
Created attachment 148066 [details] fix connection leaks
Status update: Tests are in better shape now. Time tracking needs to be enabled to fix some tests. BugzillaRepository32Test and one other. Should have them fixed before release date.
Rob, what is the current status of this?
BugzillaRepository32Test had failures. Looking at this now...
Created attachment 154168 [details] current state first failure was a network timeout that passed after rerun
Do you think it's feasible to aim for having this fixed within in the next weeks so we can get a green test run for all of Mylyn before contributing to Helios M4?
Yes, lets consider the Bugzilla component locked until we have these tests passing. BugzillaTaskHyperlinkDetectorTest - Frank could you investigates since you've been working on link detection improvements. BugzillaRepositoryConnectorTest - I'll look into getting time tracking enabled in the configuration for the test servers. BugzillaRepository32Test - Frank, another one for you. I'll commit what porting I've done then if you could look at the failing tests that would be great. BugzillaDateTimeTests - I'll take a look at this.
Created attachment 154373 [details] fix BugzillaTaskHyperlinkDetectorTest here the commited patch
Created attachment 154374 [details] mylyn/context/zip
Created attachment 154375 [details] date time fix / refactoring Great Frank. Here's the timing test patch as committed.
Created attachment 154376 [details] mylyn/context/zip
Created attachment 154377 [details] rev
Rob, can you please correct the Flag definition in teh test repositories. What is need for testFlags requestable multiplicable specifically_requestable 1) BugFlag1 no no no 2) BugFlag2 yes no no 3) BugFlag3 yes yes no 4) BugFlag4 yes no yes
Created attachment 154384 [details] commited patch Here is what I have commited. I did some changes in the test bugzilla repositories (3.2 and 3.4) for the Flags
Created attachment 154385 [details] mylyn/context/zip
Great. Time test now passing as well. Marking resolved!
Great stuff! I have added the Bugzilla tests back to the AllConnectorTests test suite.
The last build failed with the error which could be related to our local test server setup being outdated. Frank, Rob, please let me know if I need to make any changes to the test server to fix any of these failures. It also looks like AllBugzillaTests does not actually run tests against multiple repository configurations like AllBugzillaHeadlessStandaloneTests does. Can you change AllBugzillaTests to follow the same pattern of creating nested test suites to run relevant tests against all fixtures? BugzillaRepositoryConnectorTest : Time tracker (testTimeTracker) History java.lang.NullPointerException at org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.testTimeTracker(BugzillaRepositoryConnectorTest.java:787) at org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) (24 more lines...) BugzillaRepositoryConnectorTest : Mid air collision (testMidAirCollision) History Mid-air collision expected junit.framework.AssertionFailedError: Mid-air collision expected at org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.testMidAirCollision(BugzillaRepositoryConnectorTest.java:577) at org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) (25 more lines...) BugzillaRepositoryConnectorTest : Std workflow32 (testStdWorkflow32) History org.eclipse.core.runtime.CoreException: An unkown repository error has occurred. at org.eclipse.mylyn.internal.bugzilla.core.BugzillaClient.parseHtmlError(BugzillaClient.java:1691) at org.eclipse.mylyn.internal.bugzilla.core.BugzillaClient.postTaskData(BugzillaClient.java:1093) at org.eclipse.mylyn.bugzilla.tests.support.BugzillaFixture.submitTask(BugzillaFixture.java:228) at org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.doStdWorkflow(BugzillaRepositoryConnectorTest.java:415) at org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.testStdWorkflow32(BugzillaRepositoryConnectorTest.java:347) at org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) (28 more lines...) BugzillaAttachmentHandlerTest : Attach to existing report (testAttachToExistingReport) History null expected:<A[] repository error ha...> but was:<A[n unkown] repository error ha...> junit.framework.ComparisonFailure: null expected:<A[] repository error ha...> but was:<A[n unkown] repository error ha...> at org.eclipse.mylyn.bugzilla.tests.BugzillaAttachmentHandlerTest.testAttachToExistingReport(BugzillaAttachmentHandlerTest.java:96) at org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) (25 more lines...) BugzillaAttachmentHandlerTest : Attachment token (testAttachmentToken) History null junit.framework.AssertionFailedError: null at org.eclipse.mylyn.bugzilla.tests.BugzillaAttachmentHandlerTest.testAttachmentToken(BugzillaAttachmentHandlerTest.java:178) at org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) (25 more lines...) BugzillaRepository32Test : Custom attributes (testCustomAttributes) History no colors set junit.framework.AssertionFailedError: no colors set at org.eclipse.mylyn.bugzilla.tests.BugzillaRepository32Test.testCustomAttributes(BugzillaRepository32Test.java:379) at org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) (25 more lines...) BugzillaRepository32Test : Flags (testFlags) History null junit.framework.AssertionFailedError: null at org.eclipse.mylyn.bugzilla.tests.BugzillaRepository32Test.testFlags(BugzillaRepository32Test.java:188) at org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) (25 more lines...)
(In reply to comment #18) > It also looks like AllBugzillaTests does not actually run tests against multiple > repository configurations like AllBugzillaHeadlessStandaloneTests does. Can you > change AllBugzillaTests to follow the same pattern of creating nested test > suites to run relevant tests against all fixtures? I'll look into that now. > BugzillaRepositoryConnectorTest : Time tracker (testTimeTracker) History > java.lang.NullPointerException > at > org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.testTimeTracker(BugzillaRepositoryConnectorTest.java:787) > at > org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) > at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) > at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) > at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) Under Group Security option in the server preferences the timetrackinggroup needs to be editbugs for this to pass I believe. > (24 more lines...) > BugzillaRepositoryConnectorTest : Mid air collision (testMidAirCollision) > History > Mid-air collision expected > junit.framework.AssertionFailedError: Mid-air collision expected > at > org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.testMidAirCollision(BugzillaRepositoryConnectorTest.java:577) > at > org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) > at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) > at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) > at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > (25 more lines...) > BugzillaRepositoryConnectorTest : Std workflow32 (testStdWorkflow32) History > org.eclipse.core.runtime.CoreException: An unkown repository error has occurred. > at > org.eclipse.mylyn.internal.bugzilla.core.BugzillaClient.parseHtmlError(BugzillaClient.java:1691) > at > org.eclipse.mylyn.internal.bugzilla.core.BugzillaClient.postTaskData(BugzillaClient.java:1093) > at > org.eclipse.mylyn.bugzilla.tests.support.BugzillaFixture.submitTask(BugzillaFixture.java:228) > at > org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.doStdWorkflow(BugzillaRepositoryConnectorTest.java:415) > at > org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.testStdWorkflow32(BugzillaRepositoryConnectorTest.java:347) > at > org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) > at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) > (28 more lines...) Not sure about this one, Frank? > BugzillaAttachmentHandlerTest : Attach to existing report > (testAttachToExistingReport) History > null expected:<A[] repository error ha...> but was:<A[n unkown] repository error > ha...> > junit.framework.ComparisonFailure: null expected:<A[] repository error ha...> > but was:<A[n unkown] repository error ha...> > at > org.eclipse.mylyn.bugzilla.tests.BugzillaAttachmentHandlerTest.testAttachToExistingReport(BugzillaAttachmentHandlerTest.java:96) > at > org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) > at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) > at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) > at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > (25 more lines...) Fixed in head. > BugzillaAttachmentHandlerTest : Attachment token (testAttachmentToken) History > null > junit.framework.AssertionFailedError: null > at > org.eclipse.mylyn.bugzilla.tests.BugzillaAttachmentHandlerTest.testAttachmentToken(BugzillaAttachmentHandlerTest.java:178) > at > org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) > at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) > at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) > at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > (25 more lines...) Lets see if this fails again. > BugzillaRepository32Test : Custom attributes (testCustomAttributes) History > no colors set > junit.framework.AssertionFailedError: no colors set > at > org.eclipse.mylyn.bugzilla.tests.BugzillaRepository32Test.testCustomAttributes(BugzillaRepository32Test.java:379) > at > org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) > at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) > at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) > at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > (25 more lines...) Custom attributes are missing from the test instance. Name: cf_multiselect with values Red, Green, Yellow, Blue > BugzillaRepository32Test : Flags (testFlags) History > null > junit.framework.AssertionFailedError: null > at > org.eclipse.mylyn.bugzilla.tests.BugzillaRepository32Test.testFlags(BugzillaRepository32Test.java:188) > at > org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) > at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) > at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) > at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > (25 more lines...) There are some flags that need to be enabled on the test repository. Frank?
Created attachment 156891 [details] patch to use fixture Looks like we have a number of failures against 3.4.1 mostly due to suite configuration so I'll need to look into cleaning this up.
Steffen, after the next run, could you post a revised failure dump. Thanks.
I have exported the databases from mylyn.eclipse.org and imported them on the test server. Rob, please check the results of the last test run, there are 33 failures. We should also do the following: * Go through all of the test classes and figure out which need to run against different repository configuration (e.g. it's sufficient to run BugzillaSearchPageTest once outside of the fixture suites since it doesn't do anything repository specific). * Add version check or modify the fixture suite setup to exclude tests that are not compatible with older Bugzilla versions (e.g. when testing custom fields). * Remove all init..() methods in AbstractBugzillaTest and replace them by usage of the fixture. * Remove Bugzilla 3.2.2 and 3.2.3 specific tests as 3.2.4 and later are the only supported versions in the 3.2.x stream now.
Created attachment 157178 [details] screenshot
Thanks for fixing the tests, Rob. Looks like we are down to 4 failures: org.eclipse.mylyn.bugzilla.tests.BugzillaAttachmentHandlerTest Attachment token@3.2.4 null junit.framework.AssertionFailedError: null at org.eclipse.mylyn.bugzilla.tests.BugzillaAttachmentHandlerTest.testAttachmentToken(BugzillaAttachmentHandlerTest.java:346) at org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) Attachment token@3.4.4 null junit.framework.AssertionFailedError: null at org.eclipse.mylyn.bugzilla.tests.BugzillaAttachmentHandlerTest.testAttachmentToken(BugzillaAttachmentHandlerTest.java:346) at org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) org.eclipse.mylyn.bugzilla.tests.EncodingTest Proper encoding upon post@3.4.4 org.apache.commons.httpclient.ProtocolException: The server localhost failed to respond with a valid HTTP response at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1987) at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098) at org.eclipse.mylyn.internal.bugzilla.core.GzipPostMethod.execute(GzipPostMethod.java:55) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.eclipse.mylyn.commons.net.WebUtil$2.execute(WebUtil.java:319) at org.eclipse.mylyn.commons.net.WebUtil$2.execute(WebUtil.java:1) at org.eclipse.mylyn.internal.commons.net.MonitoredRequest.call(MonitoredRequest.java:51) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) at java.lang.Thread.run(Thread.java:595) org.eclipse.mylyn.bugzilla.tests.core.BugzillaCustomFieldsTest Custom attributes new task@3.2.4 null junit.framework.AssertionFailedError: null at org.eclipse.mylyn.bugzilla.tests.core.BugzillaCustomFieldsTest.testCustomAttributesNewTask(BugzillaCustomFieldsTest.java:172) at org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127)
And this test also fails intermittently: org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest Mid air collision@3.4.4 Mid-air collision expected junit.framework.AssertionFailedError: Mid-air collision expected at org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.testMidAirCollision(BugzillaRepositoryConnectorTest.java:578) at org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354)
I saw that you have disabled all tests that were previously running against Bugzilla < 3.0. While we don't officially support those versions anymore wouldn't it make sense to run a very basic set of tests against them? We already have the setup in place and know that most tests were passing. Don't bother with it if you think the cost of maintaining these tests is too high in the end.
Added 222 back to the list. The others are going to be too much overhead (and are relatively old). Still a couple spurious failures but otherwise passing green locally. Hopefully I'll get some more time to look into these odd failures today.
Created attachment 159218 [details] inprogress
Created attachment 159228 [details] inprogress
Created attachment 159235 [details] update
Fixture now passing.
Thanks Rob. Can you summarize what was causing the failures? Have the concerns that I raised in comment 22 been addressed?
The 3.5 test run failed again: org.eclipse.core.runtime.CoreException: An unknown repository error has occurred: ada [...] at org.eclipse.mylyn.internal.bugzilla.core.BugzillaClient.parseRepositoryResponse(BugzillaClient.java:1673) at org.eclipse.mylyn.internal.bugzilla.core.BugzillaClient.parseHtmlError(BugzillaClient.java:1515) at org.eclipse.mylyn.internal.bugzilla.core.BugzillaClient.getTaskData(BugzillaClient.java:1804) at org.eclipse.mylyn.bugzilla.tests.support.BugzillaFixture.getTask(BugzillaFixture.java:233) at org.eclipse.mylyn.bugzilla.tests.BugzillaAttachmentHandlerTest.testAttachmentToken(BugzillaAttachmentHandlerTest.java:320
(In reply to comment #33) > The 3.5 test run failed again: > > org.eclipse.core.runtime.CoreException: An unknown repository error has > occurred: ada Sorry I can not reproduce this. Test creates the http://mylyn.eclipse.org/bugshead/show_bug.cgi?id=15 without an error.
Looks like it's all good now. Rob ran the tests a couple more times and the all seem to have been passed. Rob, it would be great if you could still summarize the cause of failures and clarify if it's feasible to backport the fix to the 3.3.x maintenance stream?
(In reply to comment #32) > Thanks Rob. Can you summarize what was causing the failures? Have the concerns > that I raised in comment 22 been addressed? Yes thanks for that summary of actions Steffen, they should all be addressed now. (In reply to comment #35) > Looks like it's all good now. Rob ran the tests a couple more times and the all > seem to have been passed. Rob, it would be great if you could still summarize > the cause of failures and clarify if it's feasible to backport the fix to the > 3.3.x maintenance stream? To summarize the fix, there was a bug in how the html responses were parsed in the client. When parsing responses the title element is checked for success/failure. In a few places, the code looked for the title, then if it didn't find a successful indicator, the stream was reset and passed along to another function to be rescanned for error cases. Some of the response pages now appear to have more content in the header resulting in the marker being overrun and the reset subsequently failing. This was leading to the second parse missing the <title> element completely. The response parsing has now been consolidated and now only performs a single parse without the need of markers. So there was some refactoring involved but given some mileage backporting should be feasible.
Thanks Rob. Great that you applied that refactoring and fixed the bug. It sounds like the changes were significant so I think we are better off disabling the failing tests in 3.3.x branch. There is only one week to the release and backporting the amount of changes would add some overhead and introduce too high of a risk of regressions.
This failure occurred last night on Eclipse 3.6. Logging it here in case the test case needs improvement: java.lang.NullPointerException at org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.testMultiRetrievalFailure(BugzillaRepositoryConnectorTest.java:94) at org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127)
The failure reoccured on 3.5: BugzillaRepositoryConnectorTest : Multi retrieval failure@3.2.4 (testMultiRetrievalFailure@3.2.4) History java.lang.NullPointerException at org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.testMultiRetrievalFailure(BugzillaRepositoryConnectorTest.java Rob, can you take a look?
Failure on Bugzilla 3.5.2+/Eclipse 3.6: junit.framework.AssertionFailedError: null at org.eclipse.mylyn.bugzilla.tests.RepositoryReportFactoryTest.testInvalidCredentials222(RepositoryReportFactoryTest.java:59) at org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) The test needs to be improved to provide more meaningful output in case of a failure.
(In reply to comment #39) > The failure reoccured on 3.5: > > BugzillaRepositoryConnectorTest : Multi retrieval failure@3.2.4 > (testMultiRetrievalFailure@3.2.4) History > java.lang.NullPointerException > at > org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.testMultiRetrievalFailure(BugzillaRepositoryConnectorTest.java > > Rob, can you take a look? Yes, thanks Steffen, I'll take a look at these failures tomorrow.
Created attachment 160219 [details] commited patch add fail to make sure that we get the expected error
Created attachment 160220 [details] mylyn/context/zip
Created attachment 160258 [details] more changes
Good catch Frank. In addition it's important that we record the actual failure message in case it doesn't match the expected message (see patch).
Expected 6583, got: [summary] junit.framework.AssertionFailedError: Expected 6583, got: [summary] at org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.testSynchChangedReports(BugzillaRepositoryConnectorTest.java:895) at org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) I guess the error handling has to be improved a little further :)...
It looks like we have a problem with all bugzilla test repositories. Here the error: Can't connect to the database. Error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) Is your database installed and up and running? Do you have the correct username and password selected in localconfig?
I think the server was upgraded and has more memory now. I'll take a look why tests are failing now.
I have restarted the mysql server. Can you retry?
(In reply to comment #49) > I have restarted the mysql server. Can you retry? Now the tests are OK!
Great! Looking good at this end as well.
There are 2 new failures: junit.framework.AssertionFailedError: null at org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.testMultiRetrievalFailure(BugzillaRepositoryConnectorTest.java:91) at org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) Invalid id error should have resulted junit.framework.AssertionFailedError: Invalid id error should have resulted at org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.testSingleRetrievalFailure(BugzillaRepositoryConnectorTest.java:64) at org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127)
(In reply to comment #52) > There are 2 new failures: > > junit.framework.AssertionFailedError: null > at > org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.testMultiRetrievalFailure(BugzillaRepositoryConnectorTest.java:91) > at > org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) > > Invalid id error should have resulted > junit.framework.AssertionFailedError: Invalid id error should have resulted > at > org.eclipse.mylyn.bugzilla.tests.BugzillaRepositoryConnectorTest.testSingleRetrievalFailure(BugzillaRepositoryConnectorTest.java:64) > at > org.eclipse.mylyn.commons.tests.support.ManagedTestSuite.run(ManagedTestSuite.java:127) All good now.
Marking resolved. Lets create new bugs to address future failures.
