Run main-based mobench fixtures on low-end devices#2
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c5caecc0cb
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| let r_point = Secp256r1::evaluate_linear_expression([gen, public], [s_g, s_p], []); | ||
|
|
||
| assert(!r_point.is_infinity); | ||
| assert(r_point.x == r_x); |
There was a problem hiding this comment.
Reinstate full p256 verification constraints in benchmark circuit
This change weakens the p256 fixture circuit by dropping the prior r_point validity assertions and leaving only assert(r_point.x == r_x). Because the benchmark artifact is compiled from this program, mobench now measures a less-constrained circuit than before, so reported prove times are no longer comparable to the previous “full-check” fixture and can understate real verification workload.
Useful? React with 👍 / 👎.
| 2>/dev/null | head -1) | ||
| comments_json="$(mktemp)" | ||
| if gh api "repos/${REPO}/issues/${PR_NUMBER}/comments" > "${comments_json}"; then | ||
| EXISTING_COMMENT_ID=$(jq -r --arg marker "${MARKER}" '.[] | select(.body | contains($marker)) | .id' "${comments_json}" | head -1) |
There was a problem hiding this comment.
Replace jq|head pipeline in strict mode comment lookup
With set -euo pipefail enabled in this step, jq ... | head -1 can fail the script when head exits after the first match and jq receives SIGPIPE while still writing, which aborts sticky-comment handling instead of falling back to the warning paths. This is most likely when multiple marker-matching comments exist or the response is large; selecting the first ID inside jq avoids the pipeline failure mode.
Useful? React with 👍 / 👎.
Mobench BrowserStack smokeRun: 25119169378 Configuration: Requested fixtures/functions:
No benchmark timings were produced by this CI run. Both platform jobs failed before writing mobench summary JSON, so the workflow summary job skipped the automatic sticky comment.
Measured: none. |
|
Superseded by #3 to use the required dcbuild3r/ branch naming convention. |
Summary
Validation
Not measured yet