Internal error messages when validating Land Cover data

[JohannaOtt]

When validating a Land Cover dataset, there are two internal errors in the testsuite:

1. Conformance Class: Data consistency, Land Cover is displayed blue in the result and is not executed with "The Test Suite was not executed because the Test Driver returned an error."
2. Conformance Class: Application schema, Land Cover nomenclature, test lc-as.a.1 description is failing with "The Test Suite was not executed because the Test Driver returned an error."

To help us investigate the issue, you may want to include:

• validate the dataset attached against the LandCover test on the production instance
  he_inspire_lcv_alkis_25832-10_25th.zip
• Firefox 96.0.3 on Windows 10
• 
• 
• Test run on 08 48 - 01.02.2022 with test suite Annex II - Land Cover (LC).html.zip
• tests EIDf67a480e-616b-4cd5-b94b-8b729dfaae27 and EID47308633-6a75-4d9b-a159-8e08c3dd74ef

All the best

Johanna

[dperezBM]

Dear @JohannaOtt,

Thank you for your message. We are going to analyze the issue, we will come back to you once we have a response.

Best regards

[arantzaetxebarria]

Dear @JohannaOtt

We have developed a solution for your issue and it is in staging environment. Could you please verify that all is working correctly? Thanks in advance.

Regards,

Arantza

[JohannaOtt]

@arantzaetxebarria I can confirm that the issue is solved for one of the reported cases (Conformance Class: Application schema, Land Cover nomenclature, EID47308633-6a75-4d9b-a159-8e08c3dd74ef)
But not for the other one (Conformance Class: Data consistency, Land Cover, EIDf67a480e-616b-4cd5-b94b-8b729dfaae27)

Test run on 10 25 - 02.03.2022 with test suite Annex II - Land Cover (LC).html.zip

[arantzaetxebarria]

Dear @JohannaOtt

Thank you for your testing and feedback. We will analyze this second issue deeper. As soon as we have a solution we will keep you informed.

Regards

[arantzaetxebarria]

Dear @JohannaOtt

It seems that this other issue (Conformance Class: Data consistency, Land Cover) is solved, see the report in the staging environment http://staging-inspire-validator.eu-west-1.elasticbeanstalk.com/etf-webapp/test-run/details.html?id=EID02bdd1ff-2633-4fd4-91ff-1ed698ce1a3c. Could you please confirm us? If all is correct, we will add the fix (Conformance Class: Application schema, Land Cover nomenclature) to the release that will take place in the next few days. Thanks

Regards

[JohannaOtt]

@arantzaetxebarria Sorry to say but the "Conformance Class: Data consistency, Land Cover" issue is back - both on productive and staging:

This is the error message:
"de.interactive_instruments.exceptions.StorageException: javax.xml.bind.MarshalException
with linked exception:
[javax.xml.bind.MarshalException
with linked exception:
[Exception [EclipseLink-25003] (Eclipse Persistence Services - 2.7.0.v20170811-d680af5): org.eclipse.persistence.exceptions.XMLMarshalException
Exception Description: An error occurred marshalling the object
Internal Exception: org.eclipse.persistence.oxm.record.ValidatingMarshalRecord$MarshalSAXParseException; cvc-complex-type.2.4.a: Invalid content was found starting with element '{"http://www.interactive-instruments.de/etf/2.0":startTimestamp}'. One of '{"http://www.interactive-instruments.de/etf/2.0":resultedFrom}' is expected.]]"

Unfortunately, I do not seem to habe the rights to re-open the issue. Maybe you or @fabiovinci could do so.

[arantzaetxebarria]

Dear @JohannaOtt

I have tested your example in production and now it seems that is working.

Test run on 09_26 - 09.06.2022 with test suite Annex II - Land Cover (LC).zip

Could you please verify? thanks
Regards

[JohannaOtt]

@arantzaetxebarria For me, it is still occurring on both instances

[fabiovinci]

Dear all,

it is very strange, I tryed right now and I don't have the reported error: https://inspire.ec.europa.eu/validator/test-run/details.html?id=EID34645a06-32f2-4002-a6aa-abd8be54dab6.

@JohannaOtt, do you confirm you are re-testing the same dataset provided in the first comment?

[JohannaOtt]

@fabiovinci Yes, I can confirm that.
When I tried again today, the test was executed and the data validated for it. Same browser etc., so I would not have expected that.
I would propose to close this issue for now and if I run into the issue again, I will open it again.

[fabiovinci]

Dear @JohannaOtt,

thank you for your feedback.
We will close this issue, please open a new one if the problem persists, since with this issue we fixed one of the two errors you reported and the solution was included in the previous release.
Thank you.