Timeout when testing OGC API Features

[fabiovinci]

It seems that there is a timeout issue with the Validator, specifically related to the OGC API - Features Test Suite.

The OGC validator fails to complete validation and the issue is impacting the INSPIRE Reference Validator which reuses the OGC test suite.

Related issue in the Validator-Helpdesk: Timeout when testing OGC API Features

Could you please check?

[cportele]

@fabiovinci - This repo is for the specification, not for the validator. I am, therefore, closing this issue here.

@ghobona @dstenger - Could you have a look and point @fabiovinci where he should record his issue, since it is related to the CITE deployment, not the OGC API Features ETS?

[fabiovinci]

Dear @cportele,

since the other Test Suites appear to be working fine, I thought the issue was specific to this particular test suite.

@ghobona @dstenger, please point me to the correct repository to open this issue if you can't move it yourself.

[cportele]

@fabiovinci - If it is specific to the ETS, the repo is here: https://github.com/opengeospatial/ets-ogcapi-features10

[ghobona]

I will transfer the Issue over to the https://github.com/opengeospatial/ets-ogcapi-features10 repository.

Please note that @mbrachman is now responsible for CITE/Compliance testing and certification.

[dstenger]

Thank you for reporting.

As documented here, the problem seems to only occur on Production and not Beta.
@fabiovinci Can you confirm that?

Revision 1.7.1 of the test suite is installed on Beta and revision 1.6 on Production. So, Beta uses a newer version of the test suite which contains, among other improvements, a fix about limiting tested data (#236).

Can you please check if the tested API contains large amounts of collections and/or items which might lead to a memory error in the validator?

We are planning to update Production, soon (this or next month). This means that the fix, currently just installed on Beta, will then be available on Production as well.

[fabiovinci]

Dear @dstenger,

I confirm that the issue is only on the Production.

Can you please check if the tested API contains large amounts of collections and/or items which might lead to a memory error in the validator?

The service under test seems to contain numerous collections, even though I limited them to 3 during validation with Production. The tested collections may include a large number of items!

[dstenger]

Thanks for confirming my assumptions.
The large number of items is most likely the root cause for the problem.

Then, the update of Production will solve the problem which is planned for this or next month. We will discuss this in the CITE team.