Windmill timeouts seem be too low
Bug #461906 reported by
Björn Tillenius
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
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
lp:~bjornt/launchpad/windmill-problems
- Deryck Hodge (community): Approve (code)
-
Diff: 164 lines4 files modifiedlib/canonical/launchpad/windmill/testing/constants.py (+2/-2)
lib/canonical/launchpad/windmill/testing/lpuser.py (+28/-19)
lib/canonical/testing/layers.py (+8/-0)
lib/lp/bugs/windmill/tests/test_bug_tags_entry.py (+10/-9)
Revision history for this message
| Francis J. Lacoste (flacoste) wrote | #1 |
Revision history for this message
| Diogo Matsubara (matsubara) wrote Bug fixed by a commit | #2 |
| Changed in launchpad-foundations: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Björn Tillenius (bjornt) wrote Re: [Bug 461906] Re: Windmill timeouts seem be too low | #3 |
| Changed in launchpad-foundations: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
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?