Add (failing) test data for BPF, URINGOP records

Numeric fields get mis-parsed as encoded strings

Author: hillu

src/test.rs

@@ -516,3 +516,27 @@ fn serde_message() {
         ],
     );
 }
+
+#[test]
+#[should_panic]
+fn parse_uringop() {
+    let msg = parse(include_bytes!("testdata/line-uringop.txt"), false).unwrap();
+    println!("{msg:?}");
+    let v = msg
+        .body
+        .get("uring_op")
+        .unwrap_or_else(|| panic!("{}: uring_op not found", msg.id));
+    assert_eq!(*v, Value::Number(Number::Dec(18)));
+}
+
+#[test]
+#[should_panic]
+fn parse_bpf() {
+    let msg = parse(include_bytes!("testdata/line-bpf.txt"), false).unwrap();
+    println!("{msg:?}");
+    let v = msg
+        .body
+        .get("prog-id")
+        .unwrap_or_else(|| panic!("{}: prog-id not found", msg.id));
+    assert_eq!(*v, Value::Number(Number::Dec(75)));
+}

src/testdata/line-bpf.txt

@@ -0,0 +1 @@
+type=BPF msg=audit(1737533267.765:12263987): prog-id=75 op=LOAD

src/testdata/line-uringop.txt

@@ -0,0 +1 @@
+type=URINGOP msg=audit(1737533617.373:12266329): uring_op=18 success=yes exit=0 items=0 ppid=140504 pid=3178806 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 subj=unconfined key=(null)