Add testing against fips docker image #8
Triggered via pull request
February 3, 2025 16:33
xrmx
Status
Failure
Total duration
6h 6m 17s
Artifacts
–
Annotations
37 errors and 2 warnings
|
test-fips (python-3.12, django-3.2)
Process completed with exit code 2.
|
|
test-fips (python-3.12, none)
Process completed with exit code 2.
|
|
test-fips (python-3.12, psycopg2-newest)
Process completed with exit code 1.
|
|
test-fips (python-3.12, redis-newest)
Process completed with exit code 2.
|
|
test-fips (python-3.12, aioredis-newest)
Process completed with exit code 2.
|
|
test-fips (python-3.12, django-4.0)
Process completed with exit code 2.
|
|
test-fips (python-3.12, psycopg-newest)
Process completed with exit code 2.
|
|
test-fips (python-3.12, django-4.2)
Process completed with exit code 2.
|
|
test-fips (python-3.12, django-5.0)
Process completed with exit code 2.
|
|
test-fips (python-3.12, memcached-newest)
Process completed with exit code 2.
|
|
test-fips (python-3.12, pyodbc-newest)
Process completed with exit code 2.
|
|
test-fips (python-3.12, pylibmc-newest)
Process completed with exit code 1.
|
|
test-fips (python-3.12, mysqlclient-newest)
Process completed with exit code 1.
|
|
test-fips (python-3.12, aiopg-newest)
Process completed with exit code 1.
|
|
test-fips (python-3.12, asyncpg-newest)
Process completed with exit code 2.
|
|
test-fips (python-3.12, starlette-0.14)
Process completed with exit code 2.
|
|
test-fips (python-3.12, pymemcache-newest)
Process completed with exit code 2.
|
|
test-fips (python-3.12, pymongo-newest)
Process completed with exit code 2.
|
|
test-fips (python-3.12, grpc-newest)
Process completed with exit code 2.
|
|
test-fips (python-3.12, boto3-newest)
The job running on runner GitHub Actions 147 has exceeded the maximum execution time of 360 minutes.
|
|
test-fips (python-3.12, boto3-newest)
The operation was canceled.
|
|
test-fips (python-3.12, pymssql-newest)
The job running on runner GitHub Actions 419 has exceeded the maximum execution time of 360 minutes.
|
|
test-fips (python-3.12, pymssql-newest)
The operation was canceled.
|
|
test-fips (python-3.12, elasticsearch-2)
The job running on runner GitHub Actions 287 has exceeded the maximum execution time of 360 minutes.
|
|
test-fips (python-3.12, elasticsearch-2)
The operation was canceled.
|
|
test-fips (python-3.12, elasticsearch-7)
The job running on runner GitHub Actions 368 has exceeded the maximum execution time of 360 minutes.
|
|
test-fips (python-3.12, elasticsearch-7)
The operation was canceled.
|
|
test-fips (python-3.12, elasticsearch-8)
The job running on runner GitHub Actions 314 has exceeded the maximum execution time of 360 minutes.
|
|
test-fips (python-3.12, elasticsearch-8)
The operation was canceled.
|
|
test-fips (python-3.12, mysql_connector-newest)
The job running on runner GitHub Actions 323 has exceeded the maximum execution time of 360 minutes.
|
|
test-fips (python-3.12, mysql_connector-newest)
The operation was canceled.
|
|
test-fips (python-3.12, pymysql-newest)
The job running on runner GitHub Actions 13 has exceeded the maximum execution time of 360 minutes.
|
|
test-fips (python-3.12, pymysql-newest)
The operation was canceled.
|
|
test-fips (python-3.12, aiomysql-newest)
The job running on runner GitHub Actions 80 has exceeded the maximum execution time of 360 minutes.
|
|
test-fips (python-3.12, aiomysql-newest)
The operation was canceled.
|
|
test-fips (python-3.12, aiobotocore-newest)
The job running on runner GitHub Actions 137 has exceeded the maximum execution time of 360 minutes.
|
|
test-fips (python-3.12, aiobotocore-newest)
The operation was canceled.
|
|
notify-on-failure
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.
|
|
notify-on-failure
Additionally, the attachment-level `fallback` argument is missing in the request payload for a chat.postMessage call - To avoid this warning, it is recommended to always provide a top-level `text` argument when posting a message. Alternatively, you can provide an attachment-level `fallback` argument, though this is now considered a legacy field (see https://api.slack.com/reference/messaging/attachments#legacy_fields for more details).
|