testdriver_mt and OptionalFeatureErrors
Bug #921624 reported by
Sorin Marian Nasoi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zorba |
Fix Released
|
Medium
|
Chris Hillery |
Bug Description
For some reason it takes a very long time to run the
OptionalFeature
with the testdriver_mt no matter if I use a Debug or a Release build.
It might be a performance issue or a testdriver_mt issue, in any case I think that Markos is the best person to take a look when he has some time.
Related branches
lp:~zorba-coders/zorba/fix-bug921624
- Chris Hillery: Approve
- Sorin Marian Nasoi: Approve
- Cezar Andrei: Pending requested
-
Diff: 4034 lines (+3964/-0)11 files modifiedChangeLog (+1/-0)
schemas/CMakeLists.txt (+24/-0)
schemas/xhtml/xhtml-lat1.ent (+196/-0)
schemas/xhtml/xhtml-special.ent (+80/-0)
schemas/xhtml/xhtml-symbol.ent (+237/-0)
schemas/xhtml/xhtml1-frameset.dtd (+1235/-0)
schemas/xhtml/xhtml1-strict.dtd (+978/-0)
schemas/xhtml/xhtml1-transitional.dtd (+1201/-0)
test/rbkt/Queries/CMakeLists.txt (+5/-0)
test/rbkt/Queries/zorba/schemas/local-xhtml.spec (+1/-0)
test/rbkt/Queries/zorba/schemas/local-xhtml.xq (+6/-0)
Changed in zorba: | |
status: | New → Fix Committed |
Changed in zorba: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
In fact, I believe this is a recurrence of the problem mentioned in bug 867026 - some of these tests load schemas from bogus URLs on example.com, and those URLs redirect to a very slow site which takes 30 seconds to time out. At some point, this stopped happening, but apparently it is happening again.
Previously there was a hack in Zorba's HTTP URL resolver which threw an error right away if you attempted to load anything from example.com; perhaps I need to re-instate that hack...
I'm assigning this to Cezar for this thoughts. Cezar, this bug originally seemed to disappear after you made the changes to resolve all URIs through static_context instead of letting Xerces do any resolving by itself. Do you have any idea why the problem might have come back? Can you think of anything to do about it? If not, assign it back to me and I'll hack something.