-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix jdbc tests fails locally with error " 'tds_fdw' extension does not exists". #2029
Merged
Deepesh125
merged 6 commits into
babelfish-for-postgresql:BABEL_3_X_DEV
from
amazon-aurora:babel-4540-dev
Nov 20, 2023
Merged
fix jdbc tests fails locally with error " 'tds_fdw' extension does not exists". #2029
Deepesh125
merged 6 commits into
babelfish-for-postgresql:BABEL_3_X_DEV
from
amazon-aurora:babel-4540-dev
Nov 20, 2023
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
Signed-off-by: Sandeep Kumawat <[email protected]>
Signed-off-by: Sandeep Kumawat <[email protected]>
Signed-off-by: Sandeep Kumawat <[email protected]>
Signed-off-by: Sandeep Kumawat <[email protected]>
Signed-off-by: Sandeep Kumawat <[email protected]>
skumawat2025
changed the title
[TEST] TDS_FDW EXTENSION NOT EXISTS
JDBC Tests fail with error " 'tds_fdw' extension does not exists locally.
Nov 17, 2023
skumawat2025
changed the title
JDBC Tests fail with error " 'tds_fdw' extension does not exists locally.
fix JDBC Tests fail with error " 'tds_fdw' extension does not exists locally.
Nov 17, 2023
skumawat2025
changed the title
fix JDBC Tests fail with error " 'tds_fdw' extension does not exists locally.
fix jdbc tests fail with error " 'tds_fdw' extension does not exists locally.
Nov 17, 2023
skumawat2025
changed the title
fix jdbc tests fail with error " 'tds_fdw' extension does not exists locally.
fix jdbc tests fails with error " 'tds_fdw' extension does not exists locally.
Nov 17, 2023
skumawat2025
changed the title
fix jdbc tests fails with error " 'tds_fdw' extension does not exists locally.
fix jdbc tests fails locally with error " 'tds_fdw' extension does not exists".
Nov 17, 2023
Deepesh125
approved these changes
Nov 20, 2023
Deepesh125
merged commit Nov 20, 2023
c44dcf7
into
babelfish-for-postgresql:BABEL_3_X_DEV
28 checks passed
Deepesh125
pushed a commit
to amazon-aurora/babelfish_extensions
that referenced
this pull request
Nov 20, 2023
…t exists". (babelfish-for-postgresql#2029) Some tests listed in issue BABEL-4540 failing with error " 'tds_fdw' extension does not exists". This is because of tds_fdw extension is not installed locally. However while running jdbc test check in GitHub we install 'tds_fdw' extension in GitHub check. These tests are running now as expected in parallel query mode. Removed these tests from ignore file. One of the test four-part-names-vu-verify still failing due to time-out. Included this test to appropriate group. Task: BABEL-4540 Signed-off-by: Sandeep Kumawat <[email protected]>
skumawat2025
added a commit
to amazon-aurora/babelfish_extensions
that referenced
this pull request
Nov 23, 2023
…t exists". (babelfish-for-postgresql#2029) Some tests listed in issue BABEL-4540 failing with error " 'tds_fdw' extension does not exists". This is because of tds_fdw extension is not installed locally. However while running jdbc test check in GitHub we install 'tds_fdw' extension in GitHub check. These tests are running now as expected in parallel query mode. Removed these tests from ignore file. One of the test four-part-names-vu-verify still failing due to time-out. Included this test to appropriate group. Task: BABEL-4540 Signed-off-by: Sandeep Kumawat <[email protected]>
Sairakan
pushed a commit
to amazon-aurora/babelfish_extensions
that referenced
this pull request
Dec 21, 2023
…t exists". (babelfish-for-postgresql#2029) Some tests listed in issue BABEL-4540 failing with error " 'tds_fdw' extension does not exists". This is because of tds_fdw extension is not installed locally. However while running jdbc test check in GitHub we install 'tds_fdw' extension in GitHub check. These tests are running now as expected in parallel query mode. Removed these tests from ignore file. One of the test four-part-names-vu-verify still failing due to time-out. Included this test to appropriate group. Task: BABEL-4540 Signed-off-by: Sandeep Kumawat <[email protected]>
Sairakan
pushed a commit
to amazon-aurora/babelfish_extensions
that referenced
this pull request
Dec 24, 2023
…t exists". (babelfish-for-postgresql#2029) Some tests listed in issue BABEL-4540 failing with error " 'tds_fdw' extension does not exists". This is because of tds_fdw extension is not installed locally. However while running jdbc test check in GitHub we install 'tds_fdw' extension in GitHub check. These tests are running now as expected in parallel query mode. Removed these tests from ignore file. One of the test four-part-names-vu-verify still failing due to time-out. Included this test to appropriate group. Task: BABEL-4540 Signed-off-by: Sandeep Kumawat <[email protected]>
Sairakan
pushed a commit
to amazon-aurora/babelfish_extensions
that referenced
this pull request
Dec 24, 2023
…t exists". (babelfish-for-postgresql#2029) Some tests listed in issue BABEL-4540 failing with error " 'tds_fdw' extension does not exists". This is because of tds_fdw extension is not installed locally. However while running jdbc test check in GitHub we install 'tds_fdw' extension in GitHub check. These tests are running now as expected in parallel query mode. Removed these tests from ignore file. One of the test four-part-names-vu-verify still failing due to time-out. Included this test to appropriate group. Task: BABEL-4540 Signed-off-by: Sandeep Kumawat <[email protected]>
Sairakan
pushed a commit
to amazon-aurora/babelfish_extensions
that referenced
this pull request
Dec 24, 2023
…t exists". (babelfish-for-postgresql#2029) Some tests listed in issue BABEL-4540 failing with error " 'tds_fdw' extension does not exists". This is because of tds_fdw extension is not installed locally. However while running jdbc test check in GitHub we install 'tds_fdw' extension in GitHub check. These tests are running now as expected in parallel query mode. Removed these tests from ignore file. One of the test four-part-names-vu-verify still failing due to time-out. Included this test to appropriate group. Task: BABEL-4540 Signed-off-by: Sandeep Kumawat <[email protected]>
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
Some tests listed in issue BABEL-4540 failing with error " 'tds_fdw' extension does not exists". This is because of tds_fdw extension is not installed locally. However while running jdbc test check in GitHub we install 'tds_fdw' extension in GitHub check. These tests are running now as expected in parallel query mode. Removed these tests from ignore file.
One of the test
four-part-names-vu-verify
still failing due to time-out. Included this test to appropriate group.Signed-off-by: Sandeep Kumawat [email protected]
Issues Resolved
BABEL-4540
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.