ppa tests without release won't show any triggers

Makes sense, I've run into the same thing (and a similar thought occurred to me).

The problem is that if unspecified, it's defaulting to the current -devel release (i.e. 'lunar'), for which the package has no test results. I think instead I'll try defaulting to "all currently supported releases". I think that should present the behavior you describe, without needing to do a double-lookup of the ppa contents.

Here's what this looks like with this fix:

$ ./scripts/ppa tests ppa:paelzer/lp-2002404-mre-q1-2023
* Triggers:
  - Source dpdk/21.11.3-0ubuntu0.22.10.1~kineticppa1: Published
    + Trigger basic @amd64♻️ Trigger all-proposed @amd64💍
    + Trigger basic @arm64♻️ Trigger all-proposed @arm64💍
    + Trigger basic @armhf♻️ Trigger all-proposed @armhf💍
    + Trigger basic @i386♻️ Trigger all-proposed @i386💍
    + Trigger basic @ppc64el♻️ Trigger all-proposed @ppc64el💍
    + Trigger basic @s390x♻️ Trigger all-proposed @s390x💍
  - Source dpdk/21.11.3-0ubuntu0.22.04.1~jammyppa1: Published
    + Trigger basic @amd64♻️ Trigger all-proposed @amd64💍
    + Trigger basic @arm64♻️ Trigger all-proposed @arm64💍
    + Trigger basic @armhf♻️ Trigger all-proposed @armhf💍
    + Trigger basic @i386♻️ Trigger all-proposed @i386💍
    + Trigger basic @ppc64el♻️ Trigger all-proposed @ppc64el💍
    + Trigger basic @s390x♻️ Trigger all-proposed @s390x💍
  - Source dpdk/19.11.14-0ubuntu0.20.04.1~focalppa1: Published
    + Trigger basic @amd64♻️ Trigger all-proposed @amd64💍
    + Trigger basic @arm64♻️ Trigger all-proposed @arm64💍
    + Trigger basic @armhf♻️ Trigger all-proposed @armhf💍
    + Trigger basic @i386♻️ Trigger all-proposed @i386💍
    + Trigger basic @ppc64el♻️ Trigger all-proposed @ppc64el💍
    + Trigger basic @s390x♻️ Trigger all-proposed @s390x💍

* Results:
  - dpdk/19.11.14-0ubuntu0.20.04.1~focalppa1
    + ✅ dpdk on focal for amd64 @ 17.01.23 15:57:04 Log️ 🗒️
    + ✅ dpdk on focal for arm64 @ 17.01.23 15:45:05 Log️ 🗒️
    + ✅ dpdk on focal for armhf @ 17.01.23 15:53:20 Log️ 🗒️
    + ✅ dpdk on focal for ppc64el @ 17.01.23 15:42:35 Log️ 🗒️

  - dpdk/21.11.3-0ubuntu0.22.04.1~jammyppa1
    + ✅ dpdk on jammy for amd64 @ 17.01.23 20:59:30 Log️ 🗒️
    + ❌ dpdk on jammy for arm64 @ 17.01.23 16:22:57 Log️ 🗒️
      • test-initscripts PASS 🟩
      • test-linkage PASS 🟩
      • test-autotest SKIP 🟧
      • test-fastsuite FAIL 🟥
    + ❌ dpdk on jammy for arm64 @ 20.01.23 08:22:48 Log️ 🗒️
      • test-initscripts PASS 🟩
      • test-linkage PASS 🟩
      • test-autotest SKIP 🟧
      • test-fastsuite FAIL 🟥
    + ✅ dpdk on jammy for arm64 @ 24.01.23 08:55:44 Log️ 🗒️
    + ✅ dpdk on jammy for arm64 @ 24.01.23 10:27:57 Log️ 🗒️
    + ❌ dpdk on jammy for armhf @ 17.01.23 15:26:23 Log️ 🗒️
      • test-initscripts SKIP 🟧
      • test-autotest SKIP 🟧
      • test-linkage FAIL 🟥
      • test-fastsuite FAIL 🟥
    + ✅ dpdk on jammy for ppc64el @ 17.01.23 15:55:28 Log️ 🗒️

  - dpdk/21.11.3-0ubuntu0.22.10.1~kineticppa1
    + ❌ dpdk on kinetic for amd64 @ 18.01.23 02:09:03 Log️ 🗒️
      • test-initscripts ...

I implemented a fix for this in 0.4.0, however I'm just noticing the fix added a regression such that it works as expected now when --release is omitted, but misbehaves when it is included.

I've implemented a more correct fix that should be available in 0.4.1 or 0.5.0