)]}'
{
  "commit": "0367d099261fc4abec8076ff3e9e0109cc0969ec",
  "tree": "7bc68e1f9daac675b8a85753e0e2dba91bb9b128",
  "parents": [
    "2b6bd7660bf85315cacc84254fb0096b83bfc2b2"
  ],
  "author": {
    "name": "Michael Brown",
    "email": "mcb30@ipxe.org",
    "time": "Tue Sep 22 10:18:51 2026 +0100"
  },
  "committer": {
    "name": "Michael Brown",
    "email": "mcb30@ipxe.org",
    "time": "Tue Sep 22 10:35:08 2026 +0100"
  },
  "message": "[test] Ensure that all TLS structure descriptor mappings are valid\n\nConstructing exhaustive standalone tests for all TLS structures is\ntime-consuming and of limited value, since there would be no guarantee\nthat the construction logic used in the test case matched the\nconstruction logic matched in the real TLS protocol engine.\n\nWe already exercise each failure path that can be triggered by genuine\nruntime errors (e.g. malformed received data, or transmit data that is\ntoo large to fit within the relevant length field).  This leaves\nuntested the other major class of errors: an invalid structure\ndescriptor mapping (e.g. a missing field description) that would\nrender the structure impossible to parse or build.\n\nExercise the parser and builder for every structure type by creating\nan all-zero descriptor (which is always permitted), sizing and\nbuilding the empty structure, and then parsing that structure.  This\nensures that the parser and builder are both satisfied that the\ndescriptor mapping is valid, since the validity of the mapping is\nindependent of the data being built or parsed.\n\nSigned-off-by: Michael Brown \u003cmcb30@ipxe.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d915071f7c3f1624f3b7e19fef332bbae3a96dfe",
      "old_mode": 33188,
      "old_path": "src/tests/tlsfmt_test.c",
      "new_id": "46088c5f77a316be4ca75a95f4c7b19869481ead",
      "new_mode": 33188,
      "new_path": "src/tests/tlsfmt_test.c"
    }
  ]
}