Repository navigation
Conversation
xavipg003
force-pushed
the
dpe-11496-9
branch
2 times, most recently
from
November 17, 2026 10:43
60c6f39 to
55c63c8
Compare
xavipg003
force-pushed
the
dpe-11496-9
branch
from
November 18, 2026 08:16
9adebe3 to
e851531
Compare
xavipg003
force-pushed
the
dpe-11496-9
branch
from
November 18, 2026 12:34
e851531 to
8946e60
Compare
xavipg003
force-pushed
the
dpe-11496-9
branch
from
November 19, 2026 08:22
8946e60 to
75678e0
Compare
xavipg003
force-pushed
the
dpe-11496-9
branch
3 times, most recently
from
November 20, 2026 14:56
fc66355 to
c7f979f
Compare
xavipg003
force-pushed
the
dpe-11496-9
branch
from
November 20, 2026 15:18
c7f979f to
1ad20e3
Compare
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
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.
Description
This PR continues moving the PostgreSQL integration tests from the VM and K8s charm repos into the single kernel library. Builds on #431.
It migrates the HA tests that check continuous writes and scaling from pytest-operator to jubilant, and moves them to the jubilant HA folder.
What's included
test_replication(VM and K8s).test_scaling,test_scaling_three_units,test_scaling_three_units_async(VM only).test_restart(K8s only).charm/helpers.py: faithful copies of the HA helpers fromha_tests/helpers.pyandpytest_operator_helpers.py. They cover continuous writes (start_ha_continuous_writes,stop_continuous_writes,count_writes,are_writes_increasing,check_writes), the Patroni cluster (get_ha_cluster_roles,fetch_cluster_members,is_replica,is_secondary_up_to_date,is_cluster_updated,get_patroni_setting,change_ha_patroni_setting), unit selection and addresses (get_postgresql_app_name,get_primary_from_app,get_unit_ip,get_machine_from_unit, ...) and scaling (scale_ha_application).wait_for_idleinhelpers/juju.py: a jubilant version of libjuju'swait_for_idle, with the same per-unit idle period, status and error checks, exact unit count and timeouts.high_availability/conftest.py:juju_continuous_writesandjuju_primary_start_timeout, sync copies of the asynccontinuous_writesandprimary_start_timeout.ha_tests/tohigh_availability/, in a separate commit. Their Spread tasks point to the new path.How the migration was done
vm_only,k8s_only,abort_on_fail), parametrizations, retries, timeouts, waits and unit selection.jujufixture instead ofops_test.asyncio.gathercalls become sequential calls,block_untilbecomesjuju.wait, andrun_actionbecomesjuju.run.get_ha_cluster_roles,change_ha_patroni_setting,start_ha_continuous_writes,scale_ha_application). The existing helpers and the tests that use them don't change.ha_tests/stay, because the tests not migrated yet still use them.