Debug cml runner idle detection logic on GitHub (#925)

* Fix `cml runner` idle detection logic on GitHub

* Simplify logic and cover edge case

What happens if job && idle or if !job && !idle? When in doubt, keep running.

* Remove stray whitespace

* Revert misled “fix” and clarify error messages

Author: 0x2b3bfa0

bin/cml/runner.js

@@ -278,15 +278,19 @@ const runLocal = async (opts) => {
 
           if (!job && !idle) {
             winston.error(
-              `Runner should be idle. Resetting jobs. Retrying in ${idleTimeout} secs`
+              `Runner is idle as per the GitHub API but busy as per CML internal state. Resetting jobs. Retrying in ${idleTimeout} seconds...`
+            );
+            winston.warn(`CML GitHub driver response: ${JSON.stringify(job)}`);
+            winston.warn(
+              `CML internal state: ${JSON.stringify(RUNNER_JOBS_RUNNING)}`
             );
 
             RUNNER_JOBS_RUNNING = [];
           }
 
           if (job && idle) {
             winston.error(
-              `Runner seems to be busy. Retrying in ${idleTimeout} secs`
+              `Runner is busy as per the GitHub API but idle as per CML internal state. Retrying in ${idleTimeout} seconds...`
             );
 
             idle = false;