We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Running this twice:
python3 tests/src/python/test_provider_postgres.py TestPyQgsPostgresProvider.testGeneratedColumns
Will pass the first time but fail the second time. I think tests should be idempotent instead
NOTE: the python3 call should be made after setting proper env variables as documented in tests/README
from the build tree:
export QGIS_PREFIX_PATH=output PYTHONPATH=output/python:$PYTHONPATH python3 tests/src/python/test_provider_postgres.py TestPyQgsPostgresProvider.testGeneratedColumns python3 tests/src/python/test_provider_postgres.py TestPyQgsPostgresProvider.testGeneratedColumns
current master
No response
The text was updated successfully, but these errors were encountered:
The error on second run is:
Provider errors: PostGIS error while adding features: ERROR: duplicate key value violates unique constraint "generated_columns_pkey" DETAIL: Key (pk)=(2) already exists. F ====================================================================== FAIL: testGeneratedColumns (__main__.TestPyQgsPostgresProvider) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/src/qgis/qgis/src/master/tests/src/python/providertestbase.py", line 1192, in testGeneratedColumns self.assertFalse(QgsVectorLayerUtils.fieldIsEditable(vl, 0, feature)) AssertionError: True is not false ----------------------------------------------------------------------
Sorry, something went wrong.
Make TestPyQgsPostgresProvider.testGeneratedColumns idempotent
76a20bf
Closes qgis#45414
989b651
Closes #45414
strk
Successfully merging a pull request may close this issue.
What is the bug or the crash?
Running this twice:
Will pass the first time but fail the second time.
I think tests should be idempotent instead
NOTE: the python3 call should be made after setting proper env variables as documented in tests/README
Steps to reproduce the issue
from the build tree:
Versions
current master
Supported QGIS version
New profile
Additional context
No response
The text was updated successfully, but these errors were encountered: