[
http://jira.amdatu.org/jira/browse/AMDATU-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10424#comment-10424
]
Ivo Ladage - van Doorn commented on AMDATU-189:
-----------------------------------------------
Hhmm, I noticed another strange thing in another oAuth integration test. I
forgot to deploy the filebasedconfiguration bundle but used the HttpService. If
you forget to deploy the filebasedconfiguration bundle, the HttpService comes
available but running on port 8080 instead (the default). So it seems that
starting the HttpService is independent from the availability of its config,
provided by the filebasedconfiguration bundle.
This seems like a timing issue to me, I can image that sometimes registration
of the configuration is just too late such hat the HttpService is actually
running on port 8080 instead of 3737. The test remembers that tests should be
executed on port 8080, but at that time the test runs the port has been changed
to 3737.
To trace if this is another possible cause of the issue I'll add a debug
statement to print the portnr against which the integration test is executed.
Angelo, can you have a look at this particular issue?
> Random failures for filter/jsp integration test
> -----------------------------------------------
>
> Key: AMDATU-189
> URL: http://jira.amdatu.org/jira/browse/AMDATU-189
> Project: Amdatu
> Issue Type: Bug
> Components: Testing
> Affects Versions: 0.0.6
> Reporter: Bram de Kruijff
> Assignee: Ivo Ladage - van Doorn
> Priority: Blocker
> Fix For: 0.0.6
>
>
> I got a buildfailure on the testFilter integration test after a commit that
> AFAIK totally unrelated. Looking at bamboo it seems this happens every now
> and then:
> http://bamboo.amdatu.org/bamboo/browse/AMDATU-TRUNK/test/case/2719767
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
