test(conformance): fix the resource conformance programs on main #536
Loading…
Reference in a new issue
No description provided.
Delete branch "loop/137-fix-resource-conformance"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs #137
Tier B on main is red after the Resource literals change: resource-bytes, resource-name and resource-text have no allocation budget, and resource-missing removes its shipped file, so the later leak-check runs of the same program panic. This PR makes resource-missing restore the file after the assertions and adds the budgets.
Review of
b6372132(CI green, but see 2: Tier B did not run on this head).[blocker]
tests/conformance/resource-missing.allocationsis missing. Before this PR the leak-check run of resource-missing panicked (the shipped file was gone) and a panicking program is exempt from the leak run. With the restore at the end of the program the leak run now completes, and per tests/conformance/README.md "a program with a leak run and no.allocationsfile fails and prints its count" (it has no.leaksfile either). The fix would turn one red Tier B entry into another. Add the budget withsh tools/conformance.sh --update-budgets --filter resource-missing(orunbudgeted: <reason>if the three counts differ) and mention the restore's extra blocks in the commit message.[blocker] Nothing verifies the change. The PR only touches
tests/conformance/*, so the CI scope rule skipstier B (linux-x64)here (only tier A, gates and bootstrap ran). The budgets 89 / 3 / 144 are exact (one block more fails) and cannot be checked from the diff. Add to the PR body the result ofsh tools/conformance.sh --filter resource-on linux-x86_64 (command + output showing the four programs pass, including the leak and allocation lines), or touch a path that triggers tier B so it runs on this head.Checked, ok: scope (matches the stated task, Refs #137), no secrets, the restore reads the file before removing it and writes it back after the assertions, expected output of resource-missing is unchanged, no docs impact.
Re-review of
403ee176(earlier blockers onb6372132).Checked, ok: scope (Refs #137, conformance fixtures only plus a usage comment in tools/conformance.sh), correctness of the restore (read before remove, written back after the assertions, expected output unchanged), no secrets, no docs impact. Commit message of
403ee176explains the tools/ touch.Approved.