Add workflow to run JDBC tests in parallel query mode for BABEL_2_X_DEV #1932
Conversation
This file contains 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
…allel query mode (babelfish-for-postgresql#1898) This pull request introduces a new GitHub workflow check designed to execute JDBC tests in parallel query mode. The primary objective of this GitHub check is to verify the execution of JDBC tests with parallel query mode enabled. Presently, certain JDBC tests are encountering issues, such as crashes, failures, or timeouts when executed with parallel query mode enabled. These problematic tests have been excluded from this workflow check. As we work towards resolving these issues in the future, we will gradually remove these excluded tests from the scheduling file. Task: BABEL-4451 Signed-off-by: Sandeep Kumawat <[email protected]> add workflow for running jdbc-tests with enabled parallel query Handle exception gracefully inside JDBC test framework if remote server is crashed (babelfish-for-postgresql#1681) Handle exception gracefully if remote server is crashed Current behaviour of test framework in event of remote server crash is that framework will get stuck without any error or anything. Recently we understood that it may also got stuck in infite loop of exception which would keep on getting buffered in corresponding test output file. This will keep on bloating output file if java process is not terminated which may in theory can cause out of disk space situation. This commit fixes that issue by identifying such exception and exitting the process. Task: None Signed-off-by: Dipesh Dhameliya <[email protected]> update ignore tests file Signed-off-by: Sandeep Kumawat <[email protected]> test1 test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> empty commit test Signed-off-by: Sandeep Kumawat <[email protected]> test test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test Signed-off-by: Sandeep Kumawat <[email protected]> test empty
skumawat2025
force-pushed
the
jira-4451-test
branch
from
c388b9d to
32f499a
Compare
added 2 commits
November 2, 2023 19:21
Signed-off-by: Sandeep Kumawat <[email protected]>
skumawat2025
changed the title
skumawat2025
changed the title
skumawat2025
changed the title
added 2 commits
November 2, 2023 20:34
Signed-off-by: Sandeep Kumawat <[email protected]>
Deepesh125
approved these changes
Nov 3, 2023
Deepesh125
merged commit ffe8aca
into
babelfish-for-postgresql:BABEL_2_X_DEV
23 checks passed
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 pull request introduces a new GitHub workflow check in BABEL_2_X_DEV branch designed to execute JDBC tests in parallel query mode. The primary objective of this GitHub check is to verify the execution of JDBC tests with parallel query mode enabled.
Presently, certain JDBC tests are encountering issues, such as crashes, failures, or timeouts when executed with parallel query mode enabled. These problematic tests have been excluded from this workflow check. As we work towards resolving these issues in the future, we will gradually remove these excluded tests from the scheduling file.
Note - In BABEL_2_X_DEV branch there are more specific problematic tests that crashes/fails in Github workflow and not reproducible locally. Added such tests in
parallel_query_jdbc_scheduleto ignore for now.Issues Resolved
BABEL-4451
Signed-off-by: Sandeep Kumawat [email protected]
Test Scenarios Covered ### - NA
Check List
By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.