New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KEYCLOAK-4278 Testsuite failures with -Pauth-server-wildfly #3944
Conversation
mstruk
commented
Mar 13, 2017
- Fixed timeouts in tests involving sending of emails
- Excluded one test requiring auth-server-undertow from executing as part of auth-server-wildfly
@@ -199,5 +199,12 @@ | |||
</plugins> | |||
|
|||
</build> | |||
|
|||
<profiles> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a separate JIRA to fix this test. We should not exclude it like this, but rather the test needs fixing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stianst True, that part is a temporary solution. I can remove it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove it
It's been removed. |
Actually, I don't think this is the correct approach at all. Graphene has different waits depending of the type of request. The problem isn't the "page load" timeout. It's that the tests are using the wrong timeout. @pdrozd can you confirm? |
@mstruk The default page load timeout is set to 10s and I think this is sufficient for almost all the tests. Are these tests fail on your local machine? On jenkins the tests are passing. |
On my machine these tests actually take longer than 10 secs to complete when auth-server-wildfly is activated. I couldn't quite get to the bottom of it but I suspect some lazy init of some provider to do with sending secured emails might be to blame. I can try and explore some more to better understand where the time is getting lost. |
More specifically, waiting for validate email required action which renders and email, and sends it as part of processing of HTTP request takes longer than 10 seconds. Not sure why. |
Something truly weird must be happening on your machine @mstruk. I can't see how it should take 10+ seconds to send en email with a test server. |
Whatever it is, it only causes tests that send emails to fail. |
The problem is apparently incredibly long local hostname resolution on my system:
I found more info and a solution. I'm closing this issue. |