Tests

Introduce `Accept` headers for sending federation transactions #163

Triggered via push May 12, 2025 18:06

jason-famedly

pushed dbb49db

jason/accept-headers-exp

Status Failure

Total duration 28m 7s

Artifacts 7

famedly-tests.yml

on: push

Matrix: complement

Matrix: sytest

Matrix: trial

tests-done

Annotations

35 errors and 25 warnings

sytest (bullseye, multi-postgres, workers)

Process completed with exit code 1.

sytest (bullseye, multi-postgres, workers)

FAILURE: #45: GET /device/{deviceId}

sytest (bullseye, multi-postgres, workers)

FAILURE: #48: PUT /device/{deviceId} updates device fields

sytest (bullseye, multi-postgres, workers)

FAILURE: #51: DELETE /device/{deviceId} requires UI auth user to match device owner

sytest (bullseye, multi-postgres, workers)

FAILURE: #55: The user must be consistent through an interactive authentication session with SSO

sytest (bullseye, multi-postgres, workers)

FAILURE: #56: The operation must be consistent through an interactive authentication session

sytest (bullseye, multi-postgres, workers)

FAILURE: #106: registration remembers parameters

sytest (bullseye, multi-postgres, workers)

FAILURE: #591: Shutdown room

sytest (bullseye, multi-postgres, workers)

Process completed with exit code 1.

sytest (bullseye, multi-postgres, workers, asyncio)

Process completed with exit code 1.

sytest (bullseye, multi-postgres, workers, asyncio)

FAILURE: #45: GET /device/{deviceId}

sytest (bullseye, multi-postgres, workers, asyncio)

FAILURE: #48: PUT /device/{deviceId} updates device fields

sytest (bullseye, multi-postgres, workers, asyncio)

FAILURE: #51: DELETE /device/{deviceId} requires UI auth user to match device owner

sytest (bullseye, multi-postgres, workers, asyncio)

FAILURE: #55: The user must be consistent through an interactive authentication session with SSO

sytest (bullseye, multi-postgres, workers, asyncio)

FAILURE: #56: The operation must be consistent through an interactive authentication session

sytest (bullseye, multi-postgres, workers, asyncio)

FAILURE: #106: registration remembers parameters

sytest (bullseye, multi-postgres, workers, asyncio)

FAILURE: #591: Shutdown room

sytest (bullseye, multi-postgres, workers, asyncio)

FAILURE: #592: After /purge_history users still get pushed for new messages

sytest (bullseye, multi-postgres, workers, asyncio)

FAILURE: #717: Users appear/disappear from directory when join_rules are changed

sytest (bullseye, multi-postgres, workers, asyncio)

FAILURE: #718: Users appear/disappear from directory when history_visibility are changed

trial (3.9, sqlite)

Process completed with exit code 1.

trial (3.11, sqlite, all)

The job was canceled because "_3_9_sqlite" failed.

trial (3.11, sqlite, all)

Process completed with exit code 1.

trial (3.12, sqlite, all)

The job was canceled because "_3_9_sqlite" failed.

trial (3.12, sqlite, all)

The operation was canceled.

trial (3.9, sqlite, all)

The job was canceled because "_3_9_sqlite" failed.

trial (3.9, sqlite, all)

The operation was canceled.

trial (3.10, sqlite, all)

The job was canceled because "_3_9_sqlite" failed.

trial (3.10, sqlite, all)

The operation was canceled.

trial (3.9, postgres, 13, all)

The job was canceled because "_3_9_sqlite" failed.

trial (3.9, postgres, 13, all)

The operation was canceled.

trial (3.13, sqlite, all)

The job was canceled because "_3_9_sqlite" failed.

trial (3.13, sqlite, all)

The operation was canceled.

trial (3.13, postgres, 17, all)

The job was canceled because "_3_9_sqlite" failed.

trial (3.13, postgres, 17, all)

The operation was canceled.

lint-pydantic