-
Notifications
You must be signed in to change notification settings - Fork 162
Closed
Labels
build test failureUnit Test failures in builds - maynot be a regression caused by the previous changeUnit Test failures in builds - maynot be a regression caused by the previous changeregressionSomething was broken by a previous changeSomething was broken by a previous changetestWork on unit tests, no change of productive codeWork on unit tests, no change of productive code
Milestone
Description
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertTrue(Assert.java:31)
at junit.framework.TestCase.assertTrue(TestCase.java:200)
at org.eclipse.jdt.core.tests.compiler.regression.CharOperationTest.testReplaceImpl(CharOperationTest.java:193)
at org.eclipse.jdt.core.tests.compiler.regression.CharOperationTest.testReplacePerformance001(CharOperationTest.java:177)
regression from #3386
While performancetests are a good idea measuring the time on a server that randomly pauses doesn't work. Please remove or disable the test
@robstryker
Metadata
Metadata
Assignees
Labels
build test failureUnit Test failures in builds - maynot be a regression caused by the previous changeUnit Test failures in builds - maynot be a regression caused by the previous changeregressionSomething was broken by a previous changeSomething was broken by a previous changetestWork on unit tests, no change of productive codeWork on unit tests, no change of productive code