Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via hadoop-yarn-dev by Apache Jenkins Server, 2 years ago
expected:<<memory:[8192, vCores:8]>> but was:<<memory:[4096, vCores:4]>>
via hadoop-yarn-dev by Apache Jenkins Server, 2 years ago
expected:<<memory:[8192, vCores:8]>> but was:<<memory:[4096, vCores:4]>>
via hadoop-yarn-dev by Apache Jenkins Server, 2 years ago
expected:<<memory:[8192, vCores:8]>> but was:<<memory:[4096, vCores:4]>>
via hadoop-yarn-dev by Apache Jenkins Server, 2 years ago
expected:<<memory:[8192, vCores:8]>> but was:<<memory:[4096, vCores:4]>>
via hadoop-yarn-dev by Apache Jenkins Server, 2 years ago
expected:<<memory:[8192, vCores:8]>> but was:<<memory:[4096, vCores:4]>>
via hadoop-yarn-dev by Kuhu Shukla (JIRA), 2 years ago
org.junit.ComparisonFailure: expected:<[]\path\to\the\pom\src...> but was:<[C:]\path\to\the\pom\src...> at org.junit.Assert.assertEquals(Assert.java:125) at org.junit.Assert.assertEquals(Assert.java:147) at org.springframework.roo.project.MavenPathResolvingStrategyTest.assertIdentifier(MavenPathResolvingStrategyTest.java:76) at org.springframework.roo.project.MavenPathResolvingStrategyTest.testGetIdentifierForRootModuleWithEmptyRelativePath(MavenPathResolvingStrategyTest.java:82)