Tests

Sliding Sync: Speed up incremental sync by avoiding extra work #3043

Sign in to view logs

You are viewing an older attempt in the history of this workflow run. View latest attempt.

Triggered via pull request September 4, 2024 22:33

synchronize #17665

madlittlemods/sliding-sync-do-less-on-incremental-sync

Status Failure

Total duration 39m 15s

Artifacts –

tests.yml

on: pull_request

check-sampleconfig

check-schema-delta

lint-clippy-nightly

Matrix: portdb

calculate-test-jobs

Matrix: complement

Matrix: trial-pypy

Matrix: sytest

Matrix: trial

Annotations

12 errors and 13 warnings

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

Process completed with exit code 1.

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

FAILURE: #149: New room members see their own join event

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

FAILURE: #150: New room members see existing members' presence in room initialSync

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

FAILURE: #153: New room members see first user's profile information in global initialSync

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

FAILURE: #154: New room members see first user's profile information in per-room initialSync

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

FAILURE: #156: Local room members see posted message events

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

FAILURE: #158: Local non-members don't see posted message events

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

FAILURE: #159: Local room members can get room messages

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

FAILURE: #161: Remote room members can get room messages

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

FAILURE: #163: Message history can be paginated over federation

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

FAILURE: #181: Invited user can reject invite over federation

Job sytest returned failure

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

check-sampleconfig

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

lint-pydantic

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Typechecking

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

portdb (3.11, 15)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

portdb (3.8, 11)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

trial (3.8, sqlite)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

export-data

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

trial (3.8, sqlite, all)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

complement (monolith, SQLite)

Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

trial (3.8, postgres, 11, all)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

complement (monolith, Postgres)

Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

complement (workers, Postgres)

Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Artifacts

Produced during runtime

Name	Size
Sytest Logs - failure - (focal, multi-postgres, workers, asyncio) Expired	2.18 MB
Sytest Logs - success - (focal) Expired	826 KB
Sytest Logs - success - (focal, multi-postgres, workers) Expired	2.1 MB
Sytest Logs - success - (focal, postgres) Expired	841 KB