Does Keycloak have some sort of requirement (Docker, PhantonJs, and so on)
to run the unit/integration/functional tests?
On Wed, Oct 3, 2018 at 2:04 PM Rafael Weingärtner <
rafaelweingartner(a)gmail.com> wrote:
Any takers on this issue?
Some more information, I am using a Docker container to execute the build.
The 4.0.0.Final is built just fine, but the 4.4.0.Final is not. The
container has access to 15GiB of RAM and 4 vCPUs.
Also, I tried looking at the test that is failing
“org.keycloak.testsuite.adapter.javascript.JavascriptAdapterTest.fragmentInLoginFunction()”,
but I could not understand what it is doing there. Can somebody provide me
some clues here?
On Mon, Oct 1, 2018 at 9:50 PM Rafael Weingärtner <
rafaelweingartner(a)gmail.com> wrote:
> Hello Keycloakers,
>
> I have been having some problem to build Keycloak 4.4.0 and 4.5.0, and so
> far I have not been able to understand it. The error I am having is the
> following:
>
>> 20:12:00,549 INFO [org.keycloak.testsuite.ssl.TrustStoreEmailTest]
>> [TrustStoreEmailTest] verifyEmailWithSslEnabled() FINISHED
>> 20:12:00,554 INFO
>> [org.keycloak.testsuite.arquillian.AuthServerTestEnricher] removing test
>> realms after test class
>> 20:12:01,451 INFO
>> [org.keycloak.testsuite.arquillian.AuthServerTestEnricher] removed realms:
>> test,
>> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.545
>> sec - in org.keycloak.testsuite.ssl.TrustStoreEmailTest
>> 20:12:01,477 INFO
>> [org.keycloak.testsuite.arquillian.undertow.KeycloakOnUndertow] Stopping
>> auth server.
>> Results :
>> Failed tests:
>> JavascriptAdapterTest.fragmentInLoginFunction:564->assertOnTestAppUrl:102
>> URL expected to begin with:
>>
http://localhost:8180/auth/realms/test/testing/javascript/index.html;
>> actual URL:
>>
http://localhost:8180/auth/realms/test/login-actions/required-action?exec...
>> JavascriptAdapterTest.fragmentInURLTest:551->assertOnTestAppUrl:102 URL
>> expected to begin with:
>>
http://localhost:8180/auth/realms/test/testing/javascript/index.html;
>> actual URL:
>>
http://localhost:8180/auth/realms/test/login-actions/required-action?exec...
>> JavascriptAdapterTest.implicitFlowTest:229->assertOnTestAppUrl:102 URL
>> expected to begin with:
>>
http://localhost:8180/auth/realms/test/testing/javascript/index.html;
>> actual URL:
>>
http://localhost:8180/auth/realms/test/login-actions/required-action?exec...
>> JavascriptAdapterTest.loginRequiredAction:326->assertOnTestAppUrl:102
>> URL expected to begin with:
>>
http://localhost:8180/auth/realms/test/testing/javascript/index.html;
>> actual URL:
>>
http://localhost:8180/auth/realms/test/login-actions/required-action?exec...
>> JavascriptAdapterTest.testGetProfile:164->assertOnTestAppUrl:102 URL
>> expected to begin with:
>>
http://localhost:8180/auth/realms/test/testing/javascript/index.html;
>> actual URL:
>>
http://localhost:8180/auth/realms/test/login-actions/required-action?exec...
>> JavascriptAdapterTest.testLoginWithKCLocale:131->assertOnTestAppUrl:102
>> URL expected to begin with:
>>
http://localhost:8180/auth/realms/test/testing/javascript/index.html;
>> actual URL:
>>
http://localhost:8180/auth/realms/test/login-actions/required-action?exec...
>> JavascriptAdapterTest.testRefreshToken:143->assertOnTestAppUrl:102 URL
>> expected to begin with:
>>
http://localhost:8180/auth/realms/test/testing/javascript/index.html;
>> actual URL:
>>
http://localhost:8180/auth/realms/test/login-actions/required-action?exec...
>> JavascriptAdapterTest.testRefreshTokenIfUnder30s:152->assertOnTestAppUrl:102
>> URL expected to begin with:
>>
http://localhost:8180/auth/realms/test/testing/javascript/index.html;
>> actual URL:
>>
http://localhost:8180/auth/realms/test/login-actions/required-action?exec...
>> Tests in error:
>>
>>
JavascriptAdapterTest.grantBrowserBasedApp:206->lambda$grantBrowserBasedApp$99c597a6$2:206
>> ? Runtime
>> JavascriptAdapterTest.implicitFlowCertEndpoint:283 ? WebDriver
>> {"errorMessage"...
>> JavascriptAdapterTest.implicitFlowOnTokenExpireTest:270 ? WebDriver
>> {"errorMes...
>> JavascriptAdapterTest.implicitFlowRefreshTokenTest:258 ? WebDriver
>> {"errorMess...
>> JavascriptAdapterTest.initializeWithRefreshToken:515 ? WebDriver
>> {"errorMessag...
>> JavascriptAdapterTest.initializeWithTimeSkew:480 ? WebDriver
>> {"errorMessage":"...
>> JavascriptAdapterTest.initializeWithTokenTest:453 ? WebDriver
>> {"errorMessage":...
>> JavascriptAdapterTest.reentrancyCallbackTest:527 ? WebDriver
>> {"errorMessage":"...
>> JavascriptAdapterTest.testBearerRequest:310 ? WebDriver
>> {"errorMessage":"Can't...
>> JavascriptAdapterTest.testCertEndpoint:236 ? WebDriver
>> {"errorMessage":"Can't ...
>> Tests run: 2062, Failures: 8, Errors: 10, Skipped: 195
>>
>
> I have no clues on why this is happening. Does anybody here have any
> ideas on how to proceed debugging?
>
> The command I am using is the following:
>
>> mvn clean install –Pdistribution
>>
>
> My Maven and Java version are the following:
>
>> root@f48b9f8e1312:~/keycloak# mvn --version
>> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
>> 2018-06-17T18:33:14Z)
>> Maven home: /root/apache-maven-3.5.4
>> Java version: 1.8.0_181, vendor: Oracle Corporation, runtime:
>> /root/jdk1.8.0_181/jre
>> Default locale: en_US, platform encoding: ANSI_X3.4-1968
>> OS name: "linux", version: "4.4.0-130-generic", arch:
"amd64", family:
>> "unix"
>>
>
> The Phanton version is:
>
>> root@f48b9f8e1312:~/keycloak# phantomjs --version
>> 2.1.1
>>
>
> It is interesting that with the machine (Java, PhatonJS, and Maven) I am
> able to build the 4.0.0 version. However, I have not been able to build
> 4.4.0 at all.
>
> Any help is welcome here :)
>
> --
> Rafael Weingärtner
>
--
Rafael Weingärtner