Don't crash if ct_log/2 is called when app not running #4

2026-06-07T00:56:50+09:00

uwiger commented

2026-06-07 00:56:50 +09:00

It may be good to be able to call gm_ctflow:ct_log(Fmt, Args) from helper code, which might also be called from test suites that don't run the gm_ctflow application. In this case, the call should simply fall back to calling ct:log/2.

If the gm_ctflow app is running, the log message will be logged in the history.

It may be good to be able to call `gm_ctflow:ct_log(Fmt, Args)` from helper code, which might also be called from test suites that don't run the `gm_ctflow` application. In this case, the call should simply fall back to calling `ct:log/2`. If the `gm_ctflow` app is running, the log message will be logged in the history.

uwiger added 1 commit 2026-06-07 00:56:51 +09:00

Don't crash if ct_log/2 is called when app not running 9ff7fcb02d

uwiger merged commit c32533dcb5 into master

2026-06-07 00:57:13 +09:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QPQ-AG/gm_ctflow#4