[jira] [Created] (IGNITE-10633) CacheEntryProcessorExternalizableFailedTest fails on Teamcity when executed under JUnit 4

[Anton Vinogradov (Jira)]

Oleg Ignatenko created IGNITE-10633:
---------------------------------------

             Summary: CacheEntryProcessorExternalizableFailedTest fails on Teamcity when executed under JUnit 4
                 Key: IGNITE-10633
                 URL: https://issues.apache.org/jira/browse/IGNITE-10633
             Project: Ignite
          Issue Type: Bug
    Affects Versions: 2.8
            Reporter: Oleg Ignatenko


{{CacheEntryProcessorExternalizableFailedTest}} fails on Teamcity when executed under JUnit 4 (I couldn't reproduce that locally.

Link to example failures at TC: [here|https://ci.ignite.apache.org/viewLog.html?buildId=2516404&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Cache1]

Example snippet from error log: {noformat}
org.apache.ignite.IgniteIllegalStateException: Ignite instance with provided name doesn't exist. Did you call Ignition.start(..) to start an Ignite instance? [name=continuous.CacheEntryProcessorExternalizableFailedTest3]
    at org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorExternalizableFailedTest.doTestInvokeTest(CacheEntryProcessorExternalizableFailedTest.java:625)
    at org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorExternalizableFailedTest.testOptimistic(CacheEntryProcessorExternalizableFailedTest.java:155)
------- Stdout: -------
[2018-12-11 00:46:36,826][INFO ][test-runner-#4280%continuous.CacheEntryProcessorExternalizableFailedTest%][root] >>> Starting test: CacheEntryProcessorExternalizableFailedTest#testOptimistic <<<
[2018-12-11 00:46:36,826][INFO ][test-runner-#4280%continuous.CacheEntryProcessorExternalizableFailedTest%][root] >>> Stopping test: CacheEntryProcessorExternalizableFailedTest#testOptimistic in 0 ms <<<
------- Stderr: -------
[2018-12-11 00:46:36,827][ERROR][main][root] Test failed.
class org.apache.ignite.IgniteIllegalStateException: Ignite instance with provided name doesn't exist. Did you call Ignition.start(..) to start an Ignite instance? [name=continuous.CacheEntryProcessorExternalizableFailedTest3]
    at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1392)
    at org.apache.ignite.Ignition.ignite(Ignition.java:529)
    at org.apache.ignite.testframework.junits.GridAbstractTest.grid(GridAbstractTest.java:1285)
    at org.apache.ignite.testframework.junits.GridAbstractTest.grid(GridAbstractTest.java:1301)
    at org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorExternalizableFailedTest.doTestInvokeTest(CacheEntryProcessorExternalizableFailedTest.java:625)
    at org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorExternalizableFailedTest.testOptimistic(CacheEntryProcessorExternalizableFailedTest.java:155)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
    at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
    at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
    at org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
    at java.lang.Thread.run(Thread.java:748)
{noformat}

-----

Possible reason for failure is that some code is missing in {{beforeTest}} because it is placed in {{beforeTestsStarted}} instead. I think so because per prior experience of migrating tests from Junit 3 to 4 we discovered that handling of these methods noticeably differs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)