Problem
As per CI job report summary, we observed the software tests accompanying the CrateDB integration started failing. It doesn't necessarily need to be related to CrateDB, but we don't know yet.
Details
> assert response.status_code in [200, 404], response.json()
E AssertionError: {'msg': 'Subject must be a string'}
E assert 422 in [200, 404]
E + where 422 = <Response [422]>.status_codeERROR test.py::test_api - AssertionError: {'msg': 'Subject must be a string'}
assert 422 in [200, 404]
+ where 422 = <Response [422]>.status_code
ERROR test.py::test_ui - AssertionError: {'msg': 'Subject must be a string'}
assert 422 in [200, 404]
+ where 422 = <Response [422]>.status_code-- Test run #332
Version
In both cases, it is using Apache Superset 3.1.3.
Quick Evaluation
We had a package switchover in this context recently. However, this has been validated sucessfully on the CI run #329 two days earlier already, so we guess it is not the culprit.
References
-- Build Status
Problem
As per CI job report summary, we observed the software tests accompanying the CrateDB integration started failing. It doesn't necessarily need to be related to CrateDB, but we don't know yet.
Details
-- Test run #332
Version
In both cases, it is using Apache Superset 3.1.3.
Quick Evaluation
We had a package switchover in this context recently. However, this has been validated sucessfully on the CI run #329 two days earlier already, so we guess it is not the culprit.
sqlalchemy-cratedbcrate-python#620References
-- Build Status