Skip to content

Fix/using custom protocol multiple times causes wrong invitation codes being stored #1847 #1888

Fix/using custom protocol multiple times causes wrong invitation codes being stored #1847

Fix/using custom protocol multiple times causes wrong invitation codes being stored #1847 #1888

Triggered via pull request November 14, 2023 15:07
@sieprasiepra
synchronize #2068
fix/1847
Status Failure
Total duration 2h 21m 10s
Artifacts 1

e2e-crossplatform.yml

on: pull_request
Matrix: linux / linux
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
windows / windows
Final attempt failed. Timeout of 1500000ms hit
windows / windows
Attempt 1 failed. Reason: Timeout of 1500000ms hit
windows / windows
Attempt 2 failed. Reason: Timeout of 1500000ms hit
windows / windows
Attempt 1 failed. Reason: Child_process exited with error code 1
windows / windows
Attempt 2 failed. Reason: Child_process exited with error code 1
windows / windows
Attempt 1 failed. Reason: Child_process exited with error code 1

Artifacts

Produced during runtime
Name Size
quiet-windows Expired
83.2 MB