matrix-org / matrix-org/complement

Test failures when v12 rooms are the default

Abierto
#799 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Lenguaje dominante
Go
Estrellas
99
Forks
72
Merge medio
4 d 1 h
PR fusionados (30 d)
8

Descripción

Failing tests on v12

tests/csapi

Most of these tests directly do something with PLs causing them to break. Some weird quirks with sync though need investigation.

--- FAIL: TestRoomDeleteAlias (8.40s)
    --- FAIL: TestRoomDeleteAlias/Parallel (0.00s)
        --- FAIL: TestRoomDeleteAlias/Parallel/Users_with_sufficient_power-level_can_delete_other's_aliases (0.70s)
        --- FAIL: TestRoomDeleteAlias/Parallel/Regular_users_can_add_and_delete_aliases_when_m.room.aliases_is_restricted (0.88s)

--- FAIL: TestRoomMembers (8.35s)
    --- FAIL: TestRoomMembers/Parallel (0.00s)
        --- FAIL: TestRoomMembers/Parallel/Test_that_we_can_be_reinvited_to_a_room_we_created (0.52s)

--- FAIL: TestDemotingUsersViaUsersDefault (7.36s)

--- FAIL: TestPowerLevels (7.51s)
    --- FAIL: TestPowerLevels/GET_/rooms/:room_id/state/m.room.power_levels_can_fetch_levels (0.01s)
    --- FAIL: TestPowerLevels/PUT_/rooms/:room_id/state/m.room.power_levels_can_set_levels (0.02s)
    --- FAIL: TestPowerLevels/PUT_power_levels_should_not_explode_if_the_old_power_levels_were_empty (0.01s)

--- FAIL: TestRoomCreationReportsEventsToMyself (12.77s)
    --- FAIL: TestRoomCreationReportsEventsToMyself/parallel (0.00s)
        --- FAIL: TestRoomCreationReportsEventsToMyself/parallel/Room_creation_reports_m.room.create_to_myself (0.12s)

--- FAIL: TestSync (20.19s)
    --- FAIL: TestSync/parallel (2.87s)
        --- FAIL: TestSync/parallel/sync_should_succeed_even_if_the_sync_token_points_to_a_redaction_of_an_unknown_event (10.18s)

--- FAIL: TestSyncTimelineGap (18.62s)
    --- FAIL: TestSyncTimelineGap/incremental (5.12s)
    --- FAIL: TestSyncTimelineGap/full (5.16s)
tests

Basically any test that uses the complement federation server is likely to be affected by this.

--- FAIL: TestIsDirectFlagFederation (7.66s)
--- FAIL: TestEventAuth (7.88s)
--- FAIL: TestFederationRedactSendsWithoutEvent (10.49s)
--- FAIL: TestInboundFederationRejectsEventsWithRejectedAuthEvents (13.96s)
--- FAIL: TestGetMissingEventsGapFilling (13.77s)
--- FAIL: TestOutboundFederationIgnoresMissingEventWithBadJSONForRoomVersion6 (8.16s)
--- FAIL: TestOutboundFederationEventSizeGetMissingEvents (8.14s)
--- FAIL: TestJoinViaRoomIDAndServerName (8.97s)
--- FAIL: TestJoinFederatedRoomWithUnverifiableEvents (7.96s)
    --- FAIL: TestJoinFederatedRoomWithUnverifiableEvents//send_join_response_missing_signatures_shouldn't_block_room_join (0.00s)
    --- FAIL: TestJoinFederatedRoomWithUnverifiableEvents//send_join_response_with_bad_signatures_shouldn't_block_room_join (0.00s)
    --- FAIL: TestJoinFederatedRoomWithUnverifiableEvents//send_join_response_with_unobtainable_keys_shouldn't_block_room_join (0.00s)
    --- FAIL: TestJoinFederatedRoomWithUnverifiableEvents//send_join_response_with_state_with_unverifiable_auth_events_shouldn't_block_room_join (0.00s)
--- FAIL: TestOutboundFederationSend (7.61s)
--- FAIL: TestNetworkPartitionOrdering (7.85s)
--- FAIL: TestSyncOmitsStateChangeOnFilteredEvents (8.16s)
--- FAIL: TestUnrejectRejectedEvents (7.92s)

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Comienza ejecutando las pruebas fallidas indicadas en tests/csapi y tests, centrándote en los casos relacionados con los niveles de poder, la sincronización, la creación de salas y la federación. Compara los fallos usando salas v12 como valor predeterminado y rastrea las interacciones con el servidor de federación Complement. La tarea estará terminada cuando los fallos indicados pasen con v12 como versión de sala predeterminada.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
go
Área
testing-qa
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Tranquilo
Claridad
Necesita aclaración
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.