summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/files/961757
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
commitd0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
treef8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/files/961757
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloadqemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/files/961757')
-rw-r--r--results/classifier/gemma3:12b/files/96175720
1 files changed, 20 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/files/961757 b/results/classifier/gemma3:12b/files/961757
new file mode 100644
index 000000000..5f694a4bc
--- /dev/null
+++ b/results/classifier/gemma3:12b/files/961757
@@ -0,0 +1,20 @@
+
+wrong error for blockdev-snapshot-sync
+
+From Laszlo Ersek:
+
+>> +    proto_drv = bdrv_find_protocol(snapshot_file);
+>>      if (!proto_drv) {
+>> -        qerror_report(QERR_INVALID_BLOCK_FORMAT, format);
+>> -        ret = -1;
+>> -        goto out;
+>> +        error_set(errp, QERR_INVALID_BLOCK_FORMAT, format);
+>> +        return;
+>>      }
+> 
+> I don't understand the logic here (based on the error message). We
+> specified "format" for the case when a completely new snapshot file has
+> to be created. If the file exists already, then bdrv_find_protocol()
+> tries to find the driver for it. If that fails, then we must report an
+> error indeed, but instead of referring to "format", we'd have to report
+> the "scheme" from the beginning of "snapshot_file".
\ No newline at end of file