add deepseek and gemma results

1 files changed, 0 insertions, 27 deletions

diff --git a/results/classifier/deepseek-2-tmp/reasoning/hypervisor/196 b/results/classifier/deepseek-2-tmp/reasoning/hypervisor/196
deleted file mode 100644
index 601132132..000000000
--- a/results/classifier/deepseek-2-tmp/reasoning/hypervisor/196
+++ /dev/null
@@ -1,27 +0,0 @@
-<think>
-Okay, so I need to classify this bug report: "Improve UX for macOS when launching from a fullscreen app". The possible categories are things like mistranslation, assembly, other, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor.
-
-First, let's break down the bug report. It's about improving user experience (UX) on macOS when launching from a fullscreen app. So the issue is related to how QEMU behaves or feels when starting up within an application that's running in full-screen mode on macOS.
-
-Looking at the categories, I'm trying to see which one fits best. Let's go through them:
-
-- Mistranslation: This would be about incorrect mapping from source architecture to IR/target. Doesn't seem relevant here.
-- Assembly: Lowering assembly code. Not related to UX or fullscreen issues.
-- Other: A catch-all category, but maybe not the most specific.
-- Device: Could relate to hardware devices, but this is more about UI/UX.
-- Graphic: Maybe, since fullscreen mode involves graphics, but it's more about user interaction rather than rendering or display issues.
-- Socket/network: Not related.
-- KVM: Kernel-based virtual machine; maybe not directly relevant unless it's a hypervisor issue.
-- Boot: Possibly, as launching might relate to booting a VM, but the focus is on UX in macOS when starting from fullscreen.
-- VNC: Remote desktop, not directly related here.
-- Debug: Not about debugging features.
-- Files/permissions: No mention of files or access issues.
-- Performance: Maybe, if launching takes too long, but the report is about UX improvement, which could include performance but isn't solely that.
-- Kernel: Probably not unless it's a kernel module issue.
-- Peripherals: Devices connected to the VM; doesn't fit here.
-- Hypervisor: QEMU acts as a hypervisor, so this might be relevant because it's about how the hypervisor interacts with the host OS (macOS) in fullscreen mode.
-
-The bug is about user experience when launching an application within a fullscreen context on macOS. Since QEMU runs as a hypervisor, and this issue pertains to its behavior within that environment, the most appropriate category seems to be "hypervisor". It's not directly about performance or graphics but rather how the hypervisor handles fullscreen launches in macOS.
-</think>
-
-hypervisor
\ No newline at end of file