potiuk commented on pull request #18040: URL: https://github.com/apache/airflow/pull/18040#issuecomment-913404073
> @potiuk Could you add some context how 2.2.6 and 2.2.7 break the tests? This information would be useful in the future when we consider relaxing the version range. Srsly I do not know yet :). When we upgrade to 2.2.6, the sqs tests fail with https://github.com/apache/airflow/runs/3518155510?check_suite_focus=true#step:6:9582 ``` tests/providers/amazon/aws/operators/test_sqs.py::TestSQSPublishOperator::test_execute_success: botocore.exceptions.ClientError: An error occurred (InvalidAddress) when calling the SendMessage operation: The address test is not valid for this endpoint. tests/providers/amazon/aws/sensors/test_sqs.py::TestSQSSensor::test_poke_message_invalid_filtering: botocore.exceptions.ClientError: An error occurred (InvalidAddress) when calling the SendMessage operation: The address test is not valid for this endpoint. tests/providers/amazon/aws/sensors/test_sqs.py::TestSQSSensor::test_poke_no_message_failed: botocore.exceptions.ClientError: An error occurred (InvalidAddress) when calling the ReceiveMessage operation: The address test is not valid for this endpoint. tests/providers/amazon/aws/sensors/test_sqs.py::TestSQSSensor::test_poke_success: botocore.exceptions.ClientError: An error occurred (InvalidAddress) when calling the SendMessage operation: The address test is not valid for this endpoint. tests/providers/google/cloud/hooks/test_datacatalog.py::TestCloudDataCatalogWithDefaultProjectIdHook::test_create_tag_template: AssertionError: Expected call: create_tag_template(metadata=(), request=parent: "projects/example-project-1/locations/europe-west-3b" ``` Any help/suggestions/guesses are welcome. I would love to fix those tests rather than limit `moto` but if we can't find the reason quickly, limiting moto might be a faster way. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
