From: Ian Jackson <ijackson@chiark.greenend.org.uk>
Date: Mon, 19 Jul 2021 02:22:53 +0000 (+0100)
Subject: jst-lower: Trap add_log_message to print to somewhere we can see
X-Git-Tag: otter-0.7.2~27
X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=commitdiff_plain;h=2a70bd905903883df14291ce7e117a22777c182f;p=otter.git

jst-lower: Trap add_log_message to print to somewhere we can see

Otherwise, we just get an exception printed by nodejs which doesn't
actually include the message.

What we do here is print it to console.log where it will end up in
stderr, and *also* print a version to the machine-readable output
parsed by jst-lower.rs.

Currently jst-lower.rs bails on seeing it, which means these kind of
log messages are still fatal errors.  This is what we want - we don't
have any test cases that expect them.

Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
---

diff --git a/jstest/lower.nodejs b/jstest/lower.nodejs
index 8a297389..701a1f1c 100644
--- a/jstest/lower.nodejs
+++ b/jstest/lower.nodejs
@@ -19,7 +19,10 @@ function api_piece(op, piece, p, args) {
   let s = op + ' ' + piece + ' ' + args.z + '\n';
   fs.writeSync(jstest_did, s);
 }
-
+function add_log_message(m) {
+  console.log('PLAYER LOG - ', m);
+  fs.writeSync(jstest_did, 'add_log_message ' + m);
+}
 
 /*
 console.log('-------------------- byhand --------------------');