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
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) FOTS_FAILURE (DISPUTED app-CatalogCheck Catalog004 22278) FOTS_FAILURE (DISPUTED app-CatalogCheck Catalog010 22279) FOTS_FAILURE (DISPUTED app-CatalogCheck Catalog011 22279) FOTS_FAILURE (DISPUTED app-CatalogCheck Catalog013 22280) FOTS_FAILURE (DISPUTED app-CatalogCheck Catalog014 22281)
EXPECTED_
EXPECTED_
EXPECTED_
EXPECTED_
EXPECTED_
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