Windmill timeouts seem be too low

Bug #461906 reported by Björn Tillenius on 2009-10-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Undecided
Björn Tillenius

Bug Description

Some Windmill tests are failing while waiting for page loads or for an element. Making the timeout a bit higher should help this. Doing this will only affect failing tests, which might take longer to actually fail. It's unfortunate, but it's hard to look into why the tests are taking so long to load the pages.

Related branches

Francis J. Lacoste (flacoste) wrote :

In the past, one source of that problem was that the windmill tests run using the devel settings to on, which made the page load the splitted JS and CSS files taking more time than usual. We fixed that by turning the devel flag to off in the windmill app server config. Is it possible that this setting was lost during the migration to the unittest-based running?

Changed in launchpad-foundations:
status: In Progress → Fix Committed

On Tue, Oct 27, 2009 at 02:01:32PM -0000, Francis J. Lacoste wrote:
> In the past, one source of that problem was that the windmill tests run
> using the devel settings to on, which made the page load the splitted JS
> and CSS files taking more time than usual. We fixed that by turning the
> devel flag to off in the windmill app server config. Is it possible that
> this setting was lost during the migration to the unittest-based
> running?

Yes, that's very possible. I haven't looked into it yet, but it looks
like the splitted files are loaded.

Changed in launchpad-foundations:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers