fix: Improve failure telemetry #171
Triggered via pull request
February 21, 2025 00:31
filipecabaco
Status
Failure
Total duration
10m 52s
Artifacts
–
Annotations
6 errors and 2 warnings
|
Tests:
test/realtime_web/channels/realtime_channel/presence_handler_test.exs#L106
test handle/2 only checks write policies once on private channels (RealtimeWeb.RealtimeChannel.PresenceHandlerTest)
|
|
Tests:
test/realtime_web/channels/realtime_channel/presence_handler_test.exs#L85
test handle/2 user can untrack when they want (RealtimeWeb.RealtimeChannel.PresenceHandlerTest)
|
|
Tests:
test/realtime_web/channels/realtime_channel/presence_handler_test.exs#L25
test handle/2 with true policy and is private, user can track their presence and changes (RealtimeWeb.RealtimeChannel.PresenceHandlerTest)
|
|
Tests:
test/realtime_web/channels/realtime_channel/presence_handler_test.exs#L62
test handle/2 with false policy and is public, user can track their presence and changes (RealtimeWeb.RealtimeChannel.PresenceHandlerTest)
|
|
Tests:
test/realtime/monitoring/prom_ex_test.exs#L7
test get_metrics/0 builds metrics in prometheus format which includes host region and id (Realtime.PromExTest)
|
|
Tests
Process completed with exit code 2.
|
|
Tests
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
Tests
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|