Locking problems

[cgay]

I'm using the master branch of logging...

T 2025-10-09T17:54:15.000-0400 [conn 1] Sent response line: "IHTTP/1.1 200 OK"
2025-10-09T17:54:15.000-0400Dconn 0] close-connection({ [conn 1] Sent header Content-Length: 0
<tcp-connection>  1})
2025-10-09T17:54:15.000-0400 [conn 1] Sent header Date: Thu, 09 Oct 2025 17:54:15 -0400

I'm seeing the above in the log file for redirected *standard-error* in Testworks, for an http test. There's clearly some kind of interleaving of log messages. I would've thought that this locking would do the trick but apparently it's not working.

[cgay]

Testworks redirects *standard-error* to a <string-stream>, so check if those have appropriate locks. Maybe it's as simple as providing stream-lock: make(<recursive-lock>) when creating the <string-stream>?

[cgay]

If my guesses above are correct, then this is a Testworks problem, but it might be worth making a note in the logging docs about the perils of rebinding *standard-error* for logging purposes.