CI: In upgrade+downgrade tests, run the current graphql_server.py.

There doesn't seem to be a good reason to run the release version, and if there's a problem, we can't fix it without making a new release.

This also means we should catch bugs much earlier.

Co-Authored-By: Abby Sassel <3883855+sassela@users.noreply.github.com>

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/6678
GitOrigin-RevId: 7b32cd721089dccabc634598b333b94a3933221a
This commit is contained in:
Samir Talwar 2022-11-03 13:01:27 +01:00 committed by hasura-bot
parent 5b2877bc8f
commit 82d897efda

View File

@ -290,11 +290,9 @@ run_server_upgrade_pytest() {
# In this case, Hasura metadata will have GraphQL servers defined as remote.
# We need to have remote GraphQL server running for the graphql-engine to avoid
# inconsistent metadata error
cd $RELEASE_PYTEST_DIR
python3 graphql_server.py &
python3 server/tests-py/graphql_server.py &
REMOTE_GQL_PID=$!
wait_for_port 5000
cd -
fi
log "start the current build"
@ -330,11 +328,9 @@ run_server_upgrade_pytest() {
############## Tests for latest release GraphQL engine once more after downgrade #########################
if [[ "$1" =~ "test_schema_stitching" ]]; then
cd $RELEASE_PYTEST_DIR
python3 graphql_server.py &
python3 server/tests-py/graphql_server.py &
REMOTE_GQL_PID=$!
wait_for_port 5000
cd -
fi
# Start the old (latest release) GraphQL Engine