)]}'
{
  "commit": "d0dd1f538ab8ca0085e388824fd5ad3f0fb5a855",
  "tree": "506144866693ea0ea80f8aa73a17a65d381dad19",
  "parents": [
    "5c717dd5a7dfecc7a0c629abf5b0b9af7583fe95"
  ],
  "author": {
    "name": "Tim Windelschmidt",
    "email": "tim@monogon.tech",
    "time": "Thu Jan 09 04:42:19 2025 +0100"
  },
  "committer": {
    "name": "Tim Windelschmidt",
    "email": "tim@monogon.tech",
    "time": "Thu Jan 09 16:58:17 2025 +0000"
  },
  "message": "osbase/bringup/test: unflake test\n\nThis is a fun one and sadly semi-expected/wanted behavior. Because we\nhave the exception tracing of the kernel enabled, it captures all\nunhandled signals and prints them into dmesg. This is then written to\nserial, which then is read by our test. Because this is all serial and\nthere is no locking, the kernel and our test can race each other and\nthe tests can\u0027t identify the string which identifies a PASS. It\u0027s simple\nto fix, as we can just disable the exception trace before provoking a\nsegfault.\n\nCloses monogon-dev/monogon#366\n\nChange-Id: I8766a28bf339e9e2d5b0aec415c3affe0db82f50\nReviewed-on: https://review.monogon.dev/c/monogon/+/3758\nTested-by: Jenkins CI\nReviewed-by: Lorenz Brun \u003clorenz@monogon.tech\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4ed8a173d56bd1a473cb541d563fd9c7c7ab2c73",
      "old_mode": 33188,
      "old_path": "osbase/bringup/test/main_failed.go",
      "new_id": "739f16e196fddc9784b509c138e42b464424740b",
      "new_mode": 33188,
      "new_path": "osbase/bringup/test/main_failed.go"
    }
  ]
}