Test runner sometimes not reporting correct code for test pass fail

For example run pizza-pier with the stub code and the browser will show 4 pass and 9 fail. An example of a pass shows:

```
Test 5
Calculates if some number of pizzas can be evenly divided between friends (2/10)

CODE RUN

(is-true (fair-share-p 3 4))
(is-false (fair-share-p 2 3))
(is-false (fair-share-p 4 5))
(is-true (fair-share-p 4 8))
(is-true (fair-share-p 1 4))
(is-true (fair-share-p 21 7))
(is-false (fair-share-p 11 10))
(is-true (fair-share-p 0 5))
(is-false (fair-share-p 17 5))
(is-true (fair-share-p 16 64))
```

an example fo a failure:

```
Test 1
Calculate the grams of dough needed for given number and size of pizzas (1/1)

CODE RUN

(is (= (dough-calculator 4 30) 1648))
(is (= (dough-calculator 2 35) 895))
(is (= (dough-calculator 6 20) 2048))
(is (= (dough-calculator 1 15) 306))
(is (= (dough-calculator 5 10) 1353))
TEST ERROR

The value
NIL
is not of type
NUMBER
when binding SB-KERNEL::X
```

My guess is that this is happening when a fiveam test includes multiple assertions. Maybe the test runner is showing the entire test for the failure of a single assertion?