[
https://issues.apache.org/jira/browse/TAPESTRY-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-1291.
------------------------------------------
Resolution: Fixed
This seems to be gone; I believe it was a combination of factors, including
adding some extra synchronization to ClassLoader calls, and giving the
integration test suite a chance to "warm up". Also, I defused a kind of race
condition by providing an actual favicon.ico.
> Flaw in application startup causes continuous integration failures
> ------------------------------------------------------------------
>
> Key: TAPESTRY-1291
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1291
> Project: Tapestry
> Issue Type: Bug
> Components: Core, IoC Container
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Assigned To: Howard M. Lewis Ship
> Priority: Critical
> Fix For: 5.0.3
>
>
> Even on my Mac, I occasionally get spurious failures of the integration tests.
> Seems to be some kind of race condition at application startup, where
> construction of some key service fails, claiming (spuriously) to be dependent
> on itself.
> The CI server, tapestry.formos.com, seems very succeptible to this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
