Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workflow "OGC tests for QGIS Server" is failing since Dez 19, 2023 #55683

Closed
pathmapper opened this issue Dec 21, 2023 · 4 comments · Fixed by #55699
Closed

Workflow "OGC tests for QGIS Server" is failing since Dez 19, 2023 #55683

pathmapper opened this issue Dec 21, 2023 · 4 comments · Fixed by #55699
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!

Comments

@pathmapper
Copy link
Contributor

pathmapper commented Dec 21, 2023

What is the bug or the crash?

https://github.com/qgis/QGIS/actions/workflows/ogc.yml

e.g.

grafik

@pathmapper pathmapper added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Dec 21, 2023
@pathmapper pathmapper changed the title Workflow "OGC tests for QGIS Server" is failing for two days Workflow "OGC tests for QGIS Server" is failing since Dez 19, 2023 Dec 22, 2023
@pathmapper
Copy link
Contributor Author

Running pyogctest on http://qgis4.qgis.org:8080/certification_qgisserver_master (which seems to be not available currently) gives the same error:

sudo -E ./pyogctest.py -s wms130 -u http://qgis4.qgis.org:8080/certification_qgisserver_master
============================================== OGC test session starts ===============================================
testsuite: WMS 1.3.0
Traceback (most recent call last):
  File "/home/user/dev/pyogctest/./pyogctest.py", line 182, in <module>
    r.dump_prompt(args.verbose, args.regex)
  File "/home/user/dev/pyogctest/pyogctest/report/report.py", line 23, in dump_prompt
    self.parser.dump_prompt(verbose, regex)
  File "/home/user/dev/pyogctest/pyogctest/report/wms130/wms130.py", line 91, in dump_prompt
    self._parse()
  File "/home/user/dev/pyogctest/pyogctest/report/wms130/wms130.py", line 234, in _parse
    root = ET.fromstring(self.xml)
  File "/usr/lib/python3.10/xml/etree/ElementTree.py", line 1343, in XML
    return parser.close()
xml.etree.ElementTree.ParseError: no element found: line 1, column 0

So for the CI failure it looks like the QGIS Server is not available for some reason:

source venv/bin/activate && ./pyogctest/pyogctest.py -n ogc_qgis -s wms130 -v -u http://$(docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' qgis_server_nginx)/qgisserver_wms130

@pathmapper
Copy link
Contributor Author

Seems related to upstream changes with teamengine.

With the latest docker image ogccite/ets-wms13



which is used by https://github.com/pblottiere/pyogctest/

https://github.com/pblottiere/pyogctest/blob/fd332aef680c0130b841c1a1abeb5eb1627723e9/pyogctest/teamengine.py#L14

the following request returns a 401

https://github.com/pblottiere/pyogctest/blob/fd332aef680c0130b841c1a1abeb5eb1627723e9/pyogctest/teamengine.py#L94

According to the response headers an authentication is required.

{'Server': 'Apache-Coyote/1.1', 'WWW-Authenticate': 'Basic realm="Insert credentials"', 'Content-Length': '0', 'Date': 'Sat, 23 Dec 2023 16:27:07 GMT'}

Authentication is not required for an older docker image like ogccite/ets-wms13:1.30-teamengine-5.4.1 where the request returns a 200 and the response headers for the same request are:

{'Server': 'Apache-Coyote/1.1', 'Content-Type': "application/xml; qs=0.5;charset='utf-8'", 'Transfer-Encoding': 'chunked', 'Date': 'Sat, 23 Dec 2023 16:40:20 GMT'}

@pblottiere
Copy link
Member

Hello @pathmapper,

Thanks for creating this issue, I didn't noticed that the OGC tests workflow was failing lastly.

I'm going to take a look.

@pblottiere
Copy link
Member

Running pyogctest on http://qgis4.qgis.org:8080/certification_qgisserver_master (which seems to be not available currently) gives the same error:

(BTW, the endpoint on qgis4 is available only during formal OGC certification process)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants