-
Notifications
You must be signed in to change notification settings - Fork 35
[CI] Run tests on AltLinux 10 #219
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
Merged
dmitry-lipetsk
merged 23 commits into
postgrespro:master
from
dmitry-lipetsk:D20250316_001--altlinux_10
Mar 24, 2025
Merged
[CI] Run tests on AltLinux 10 #219
dmitry-lipetsk
merged 23 commits into
postgrespro:master
from
dmitry-lipetsk:D20250316_001--altlinux_10
Mar 24, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changes: - VIRTUALENV: virtualenv is explicitly executed through ${PYTHON} The current problems 1) testgres/operations/helpers.py # Prepared pointer on function to get a name of system codepage _get_default_encoding_func = _make_get_default_encoding_func() must be # Prepared pointer on function to get a name of system codepage _get_default_encoding_func = _make_get_default_encoding_func.__func__() It is a problem of Python 3.9 2) These tests fail: FAILED tests/test_simple.py::TestgresTests::test_logical_replication - psycopg2.errors.ProtocolViolation: could not create replication slot "mysub": ERROR: could not access file "pgoutput": No such file or directory FAILED tests/test_simple.py::TestgresTests::test_logical_catchup - psycopg2.errors.ProtocolViolation: could not create replication slot "mysub": ERROR: could not access file "pgoutput": No such file or directory FAILED tests/test_simple_remote.py::TestgresRemoteTests::test_logical_replication - psycopg2.errors.ProtocolViolation: could not create replication slot "mysub": ERROR: could not access file "pgoutput": No such file or directory FAILED tests/test_simple_remote.py::TestgresRemoteTests::test_logical_catchup - psycopg2.errors.ProtocolViolation: could not create replication slot "mysub": ERROR: could not access file "pgoutput": No such file or directory I suggest to fix these problems in the separated commits.
…3.9] Python 3.9 does not undestand the following code: _get_default_encoding_func = _make_get_default_encoding_func() ERROR - TypeError: 'staticmethod' object is not callable https://app.travis-ci.com/github/postgrespro/testgres/jobs/631402370 The code: _get_default_encoding_func = _make_get_default_encoding_func.__func__() is processed without problems.
…20250316_001--altlinux_10
This patch fixes a problem with run the following commands: "time <set env> converage run ..." This command does not work (on altlinux-10 with custom build of PG). I do not know why it happened and do not know why it was working early. "<set env> time converage run ..." works without any problems.
We manually compile and "install" PG: - create a symlink /usr/local/bin/pg_config - create a symlink /usr/lib64/libpq.so.5 Manual bild fixes the following problem: psycopg2.errors.ProtocolViolation: could not create replication slot "mysub": ERROR: could not access file "pgoutput": No such file or directory Failed tests: - TestTestgresCommon::test_logical_replication[remote_ops] - TestTestgresCommon::test_logical_catchup[local_ops] - TestTestgresCommon::test_logical_replication[local_ops] - TestTestgresCommon::test_logical_catchup[remote_ops]
time is installed manually. It fixes the following problem: ++ pg_config --bindir + PG_BIN=/usr/lib/postgresql/17/bin + time coverage run -a -m pytest -l -v -n 4 -k '' ./run_tests.sh: line 49: time: command not found
Alplinux does in creates /usr/bin/virtualenv but creates /usr/bin/virtualenv3. Let's create the symlink /usr/bin/virtualenv -> /usr/bin/virtualenv3 and restore an usage of virtualenv in run_tests.sh.
Python environment initialization has been simplified.
AltLinux 10 does not support the sequential "time <set_env> coverage run ...". Because this OS does not has a builtin command 'time' in bash. https://forum.altlinux.org/index.php?topic=48342.0 We will install 'time' manually and use another command "<set_env> time coverage run ..." that works without problems but it requires to install 'time' on Ubuntu 2024.04, too. AlpineLinux processes a new command line without any problems.
Let's avoid creating useless environment variables.
…0250316_001--altlinux_10
Merged
I don't understand why, but a simple "ssh localhost" command on AltLinux (10, 11) works 6 times slower than the same command on Ubuntu or Alpine. This is the cause of the problems. |
We exclude "remote" tests until a problem with slow SSH connection has been resolved.
Installation of mc is deleted.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes:
The current problems
must be
It is a problem of Python 3.9
I suggest to fix these problems in the separated commits.