mirror of
https://github.com/neondatabase/neon.git
synced 2025-12-26 07:39:58 +00:00
b8d47b5acf
## Problem We currently don't run end-to-end tests for PostgreSQL extensions on our cloud infrastructure, which means we might miss problems that only occur in a real cloud environment. ## Summary of changes - Added a workflow to run extension tests against a cloud staging instance - Set up proper project configuration for extension testing - Implemented test execution with appropriate environment settings - Added error handling and reporting for test failures --------- Co-authored-by: Alexander Bayandin <alexander@neon.tech> Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
11 lines
530 B
Bash
Executable File
11 lines
530 B
Bash
Executable File
#!/bin/sh
|
|
set -ex
|
|
cd "$(dirname ${0})"
|
|
make installcheck || true
|
|
dropdb --if-exist contrib_regression
|
|
createdb contrib_regression
|
|
PG_REGRESS=$(dirname "$(pg_config --pgxs)")/../test/regress/pg_regress
|
|
sed -i '/hastap/d' test/build/run.sch
|
|
sed -Ei 's/\b(aretap|enumtap|ownership|privs|usergroup)\b//g' test/build/run.sch
|
|
${PG_REGRESS} --use-existing --dbname=contrib_regression --inputdir=./ --bindir='/usr/local/pgsql/bin' --inputdir=test --max-connections=879 --schedule test/schedule/main.sch --schedule test/build/run.sch
|