failures in "app-CatalogCheck"

Bug #1172273 reported by Sorin Marian Nasoi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zorba
Fix Committed
High
Sorin Marian Nasoi

Bug Description

There are 12 failures in "app-CatalogCheck" test set:
"Catalog001,Catalog002,Catalog003,Catalog004,Catalog005,Catalog006,Catalog007,Catalog008,Catalog009,Catalog010,Catalog011,Catalog012"

All of them seem to be related to a wrong base-uri setting for these test cases.

Related branches

Revision history for this message
Sorin Marian Nasoi (sorin.marian.nasoi) wrote :
Changed in zorba:
status: New → In Progress
Revision history for this message
Chris Hillery (ceejatec) wrote :

All but Catalog010 and Catalog011 are fixed by the fix for bug-1134008.

Revision history for this message
Chris Hillery (ceejatec) wrote :

Oh, forgot Catalog002 is also still failing.

Revision history for this message
Sorin Marian Nasoi (sorin.marian.nasoi) wrote :

In Zorba rev11432 there are currently 3 test-case failures:
"Catalog002,Catalog010,Catalog011"

Changed in zorba:
importance: Undecided → High
milestone: none → 3.0
Revision history for this message
Sorin Marian Nasoi (sorin.marian.nasoi) wrote :

All of the remaining failures are caused by errors in FOTS test-cases: here are the W3C bug numbers associated with every failure:

EXPECTED_FOTS_FAILURE (DISPUTED app-CatalogCheck Catalog002 22277)
EXPECTED_FOTS_FAILURE (DISPUTED app-CatalogCheck Catalog004 22278)
EXPECTED_FOTS_FAILURE (DISPUTED app-CatalogCheck Catalog010 22279)
EXPECTED_FOTS_FAILURE (DISPUTED app-CatalogCheck Catalog011 22279)
EXPECTED_FOTS_FAILURE (DISPUTED app-CatalogCheck Catalog013 22280)
EXPECTED_FOTS_FAILURE (DISPUTED app-CatalogCheck Catalog014 22281)

For example test-case 'Catalog002' is failing because of https://www.w3.org/Bugs/Public/show_bug.cgi?id=22277
and so on.

This can be marked as "Fix committed" once the linked branch is merged.
Please see lp:~zorba-coders/zorba/add_LP_bug_numbers_to_expected_failures

Changed in zorba:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.