graphql-engine

hasura/graphql-engine

Fork 0

mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-14 17:02:49 +03:00

Commit Graph

Author	SHA1	Message	Date
Samir Talwar	710a33bf45	CI: Run the Python tests in the "new" mode, one HGE per test class. Part of [NDAT-257](https://hasurahq.atlassian.net/browse/NDAT-257). This runs the Python tests in parallel, all at once, with each test class spinning up HGE and configuring it appropriately. Once we are confident this works, we can remove most of the old jobs, drastically reducing the number of machines we need to run the Python tests. For now we are only running on PostgreSQL 15. Once this is merged, we can expand to all supported PostgreSQL versions, and then Citus, MS SQL Server, and BigQuery. [NDAT-257]: https://hasurahq.atlassian.net/browse/NDAT-257?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ PR-URL: https://github.com/hasura/graphql-engine-mono/pull/7780 GitOrigin-RevId: 174511fc3e3bcd4ea968e3ade6c867c3aa84096a	2023-02-03 14:09:29 +00:00
Samir Talwar	8d7c089273	server/tests-py: Start some node.js test services on random ports. Where possible, we start the services on random ports, to avoid port conflicts when parallelizing tests in the future. When this isn't possible, we explicitly state the port, and wait for the service to start. This is typically because the GraphQL Engine has already started with knowledge of the relevant service passed in through an environment variable. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5542 GitOrigin-RevId: b51a095b8710e3ff20d1edb13aa576c5272a5565	2022-09-07 16:26:10 +00:00
Karthikeyan Chinnakonda	d6de3592ed	actions: fix behaviour when using remote relationship in mutation action's relationship (#4982 ) * resolve the remote server when a remote join query used in action mutation	2020-06-05 17:33:18 +05:30

Author

SHA1

Message

Date

Samir Talwar

710a33bf45

CI: Run the Python tests in the "new" mode, one HGE per test class.

Part of [NDAT-257](https://hasurahq.atlassian.net/browse/NDAT-257).

This runs the Python tests in parallel, all at once, with each test class spinning up HGE and configuring it appropriately. Once we are confident this works, we can remove most of the old jobs, drastically reducing the number of machines we need to run the Python tests.

For now we are only running on PostgreSQL 15. Once this is merged, we can expand to all supported PostgreSQL versions, and then Citus, MS SQL Server, and BigQuery.

[NDAT-257]: https://hasurahq.atlassian.net/browse/NDAT-257?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/7780
GitOrigin-RevId: 174511fc3e3bcd4ea968e3ade6c867c3aa84096a

2023-02-03 14:09:29 +00:00

Samir Talwar

8d7c089273

server/tests-py: Start some node.js test services on random ports.

Where possible, we start the services on random ports, to avoid
port conflicts when parallelizing tests in the future.

When this isn't possible, we explicitly state the port, and wait for the
service to start. This is typically because the GraphQL Engine has already
started with knowledge of the relevant service passed in through an
environment variable.

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5542
GitOrigin-RevId: b51a095b8710e3ff20d1edb13aa576c5272a5565

2022-09-07 16:26:10 +00:00

Karthikeyan Chinnakonda

d6de3592ed

actions: fix behaviour when using remote relationship in mutation action's relationship (#4982 )

* resolve the remote server when a remote join query used in action mutation

2020-06-05 17:33:18 +05:30

3 Commits