Update trycmd test files

necessist/tests/necessist_db_absent/cfg.stdout

@@ -1,11 +1,107 @@
 4 candidates in 4 tests in 1 source file
 fixtures/cfg/src/lib.rs: dry running
 fixtures/cfg/src/lib.rs: mutilating
-fixtures/cfg/src/lib.rs:5:5-5:12: Warning: Failed to run test `passed`
+fixtures/cfg/src/lib.rs:5:5-5:12: Warning: Failed to run test `passed`: code=0
+stdout=```
+
+running 0 tests
+
+test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in [..]s
+
+```
+
+stderr=```
+...
+warning: function `noop` is never used
+ --> [..]:9:4
+  |
+9 | fn noop() {}
+  |    ^^^^
+  |
+  = note: `#[warn(dead_code)]` on by default
+
+warning: `cfg` (lib test) generated 1 warning
+    Finished `test` profile [unoptimized + debuginfo] target(s) in [..]s
+     Running unittests [..] ([..])
+```
+
+
 
 This may indicate a bug in Necessist. Consider opening an issue at: https://github.com/trailofbits/necessist/issues
 
 Silence this warning with: --allow run-test-failed
-fixtures/cfg/src/lib.rs:16:9-16:16: Warning: Failed to run test `timed_out`
-fixtures/cfg/src/lib.rs:24:5-24:12: Warning: Failed to run test `failed`
-fixtures/cfg/src/lib.rs:32:18-32:27: Warning: Failed to run test `nonbuildable`
+fixtures/cfg/src/lib.rs:16:9-16:16: Warning: Failed to run test `timed_out`: code=0
+stdout=```
+
+running 0 tests
+
+test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in [..]s
+
+```
+
+stderr=```
+...
+warning: function `noop` is never used
+ --> [..]:9:4
+  |
+9 | fn noop() {}
+  |    ^^^^
+  |
+  = note: `#[warn(dead_code)]` on by default
+
+warning: `cfg` (lib test) generated 1 warning
+    Finished `test` profile [unoptimized + debuginfo] target(s) in [..]s
+     Running unittests [..] ([..])
+```
+
+
+fixtures/cfg/src/lib.rs:24:5-24:12: Warning: Failed to run test `failed`: code=0
+stdout=```
+
+running 0 tests
+
+test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in [..]s
+
+```
+
+stderr=```
+...
+warning: function `noop` is never used
+ --> [..]:9:4
+  |
+9 | fn noop() {}
+  |    ^^^^
+  |
+  = note: `#[warn(dead_code)]` on by default
+
+warning: `cfg` (lib test) generated 1 warning
+    Finished `test` profile [unoptimized + debuginfo] target(s) in [..]s
+     Running unittests [..] ([..])
+```
+
+
+fixtures/cfg/src/lib.rs:32:18-32:27: Warning: Failed to run test `nonbuildable`: code=0
+stdout=```
+
+running 0 tests
+
+test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in [..]s
+
+```
+
+stderr=```
+...
+warning: function `noop` is never used
+ --> [..]:9:4
+  |
+9 | fn noop() {}
+  |    ^^^^
+  |
+  = note: `#[warn(dead_code)]` on by default
+
+warning: `cfg` (lib test) generated 1 warning
+    Finished `test` profile [unoptimized + debuginfo] target(s) in [..]s
+     Running unittests [..] ([..])
+```
+
+

necessist/tests/necessist_db_absent/cfg_deny_run_test_failed.stderr

@@ -1,4 +1,27 @@
-Error: Failed to run test `passed`
+Error: Failed to run test `passed`: code=0
+stdout=```
+
+running 0 tests
+
+test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in [..]s
+
+```
+
+stderr=```
+warning: function `noop` is never used
+ --> [..]:9:4
+  |
+9 | fn noop() {}
+  |    ^^^^
+  |
+  = note: `#[warn(dead_code)]` on by default
+
+warning: `cfg` (lib test) generated 1 warning
+    Finished `test` profile [unoptimized + debuginfo] target(s) in [..]s
+     Running unittests [..] ([..])
+```
+
+
 
 This may indicate a bug in Necessist. Consider opening an issue at: https://github.com/trailofbits/necessist/issues