Skip to content
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

Do not run excluded tags in integration tests #8715

Merged
merged 1 commit into from
Dec 11, 2021

Conversation

cgardens
Copy link
Contributor

What

  • The build was failing (example), because 2 newly added tests (S3DocumentStoreClientTest and GcsDocumentStoreClientTest) that was supposed to be run only as part of tools/bin/cloud_storage_logging_test.sh were getting run when airbyte-workers:integrationTest was run. This was happening because airbyte-integration-test-java.gradle overrides the exclude tags set in build.gradle. This did not affect the other tests run in this script, because the gradle sub modules that those tests were in did not have integration tests. airbyte-workers does have integration tests so it was affected.

How

explicitly add the exclusions in airbyte-integration-test-java.gradle. this isn't very pretty, but i couldn't find a more elegant way of doing it, so going with this for now to fix the build.

@cgardens cgardens temporarily deployed to more-secrets December 11, 2021 00:05 Inactive
@jrhizor jrhizor merged commit e9f414d into master Dec 11, 2021
@jrhizor jrhizor deleted the cgardens/fix-k8s-acceptance-tests branch December 11, 2021 00:20
@@ -25,7 +25,11 @@ class AirbyteIntegrationTestJavaPlugin implements Plugin<Project> {
testClassesDirs += project.sourceSets.integrationTestJava.output.classesDirs
classpath += project.sourceSets.integrationTestJava.runtimeClasspath

useJUnitPlatform()
useJUnitPlatform {
// todo (cgardens) - figure out how to de-dupe this exclusion with the one in build.gradle.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One solution would be to make an include list instead and properly annotate the integration test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants