Comment 2 for bug 2065754

ppa-dev-tools looks for the '@@@@@@@@@' separator to identify the header for the test log, however when the testbed setup fails, there is no separator to detect. That's why the blank trigger occurs; ppa-dev-tools didn't recognize a header so didn't try to parse out the trigger.

A second problem is that when reviewing the subtest status it did not recognize BAD as a broken state, so lists the overall test result as passed.

With these issues fixed, the output looks more like you'd expect:

* Results:
  - rabbitmq-server/3.8.3-0ubuntu0.1~focal5
    + ⛔ rabbitmq-server on focal for arm64 @ 12.05.24 03:07:20 Log️ 🗒️
      • testbed BAD ⛔
    + ⛔ rabbitmq-server on focal for armhf @ 11.05.24 08:01:13 Log️ 🗒️
      • testbed BAD ⛔
    + ✅ rabbitmq-server on focal for i386 @ 11.05.24 13:35:11 Log️ 🗒️
    + ✅ rabbitmq-server on focal for ppc64el @ 14.05.24 23:10:14 Log️ 🗒️
    + ✅ rabbitmq-server on focal for s390x @ 14.05.24 03:20:42 Log️ 🗒️
  - rabbitmq-server/3.9.27-0ubuntu0.1~jammy4
    + ✅ rabbitmq-server on jammy for amd64 @ 06.05.24 23:39:20 Log️ 🗒️
    + ✅ rabbitmq-server on jammy for arm64 @ 06.05.24 23:21:35 Log️ 🗒️
    + ✅ rabbitmq-server on jammy for armhf @ 06.05.24 23:22:57 Log️ 🗒️
    + ✅ rabbitmq-server on jammy for i386 @ 06.05.24 23:39:34 Log️ 🗒️
    + ✅ rabbitmq-server on jammy for ppc64el @ 06.05.24 23:23:10 Log️ 🗒️
    + ✅ rabbitmq-server on jammy for s390x @ 06.05.24 23:23:28 Log️ 🗒️
  - rabbitmq-server/3.9.27-0ubuntu0.1~jammy8
    + ✅ rabbitmq-server on jammy for arm64 @ 13.05.24 19:10:51 Log️ 🗒️
    + ⛔ rabbitmq-server on jammy for armhf @ 13.05.24 12:50:51 Log️ 🗒️
      • testbed BAD ⛔
    + ✅ rabbitmq-server on jammy for i386 @ 13.05.24 19:16:38 Log️ 🗒️
    + ✅ rabbitmq-server on jammy for s390x @ 15.05.24 01:04:39 Log️ 🗒️