You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Auto-Minimized Fuzzing Input That Triggers the Bug: Click this line.Note: If the input is multi-line then the end-of-line characters '\n' (0x0A) and '\r' (0x0D)
may affect the reproducibility of the bug. If you fail to repro the bug with the input shown below
then you may want to go to the workflow that reported this GitHub bug,
download the artifact, and extract the file with the exact minimized input.
ctrl(π/0s)@a
Fuzzing stderr Log (last 62kB), includes the stack trace: Click.
The fragment of interest starts with "panicked at".
The branch/commit the bug has been found in: Click.
If the developers fail to repro the bug in the latest main then the branch/commit info below can help them to make sure
that they are using the correct way to repro. If the bug is reproducible in the branch/commit below, but not in latest main,
then the bug is likely fixed already or is not in the main branch.
Branch: * iadavis/qasm-fuzz
commit bc48998d73a3d669f38b879c303520883bbf31c0
Author: Ian Davis <ian.f.davis@microsoft.com>
Date: Thu Apr 17 17:24:54 2025 -0700
Adding more compilation and samples for fuzzing
Workflow Agent System Info:ubuntu-latest: Linux fv-az1695-627 6.8.0-1021-azure #25-Ubuntu SMP Wed Jan 15 20:45:09 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux.
Bug Reporting Timestamp: 2025.04.18 01:34 UTC (UTC - 8:00 = PST. UTC - 7:00 = PDT).
The text was updated successfully, but these errors were encountered:
Fixes#2313. The issue was caused by an assertion in the const
evaluator. The fix is surfacing the error to the user instead of
panicking. I also made sure the check is exhaustive, since it was
missing some cases.
The fuzz-testing workflow has detected a bug.
Auto-Minimized Fuzzing Input That Triggers the Bug: Click this line.
Note: If the input is multi-line then the end-of-line characters '\n' (0x0A) and '\r' (0x0D) may affect the reproducibility of the bug. If you fail to repro the bug with the input shown below then you may want to go to the workflow that reported this GitHub bug, download the artifact, and extract the file with the exact minimized input.Fuzzing
The fragment of interest starts with "panicked at".stderr
Log (last 62kB), includes the stack trace: Click.The branch/commit the bug has been found in: Click.
If the developers fail to repro the bug in the latestmain
then the branch/commit info below can help them to make sure that they are using the correct way to repro. If the bug is reproducible in the branch/commit below, but not in latestmain
, then the bug is likely fixed already or is not in themain
branch.Other Info
ubuntu-latest: Linux fv-az1695-627 6.8.0-1021-azure #25-Ubuntu SMP Wed Jan 15 20:45:09 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
.The text was updated successfully, but these errors were encountered: