Repository navigation
test(codegen): eight mapped integration assertions are red on current main #8264
Description
The ci_e2e_scope classifier previously stopped before running mapped perry-codegen integration suites. After PR #8208 classified release_boxes_lowering, the runner exposed the remaining baseline reds: six native_proof_buffer_views assertions (artifact_records_buffer_read_double_as_f64; artifact_records_buffer_read_float_as_f32_and_float_extend_materialization; artifact_records_buffer_read_u32_and_unsigned_materialization; artifact_records_width_aware_buffer_numeric_read_facts; explicit_width_guard_proves_wide_buffer_read; proven_buffer_and_typed_array_reads_are_numeric_operands), shadow_slot_hygiene::canonical_str_local_keeps_shadow_binding_and_tag_dispatched_ops, and typed_feedback::typed_feedback_guards_direct_class_field_specialization. The other mapped suites pass. Reconcile these assertions with current codegen. Until fixed, self-invalidating per-test SUITE_EXCLUSIONS entries should keep the inherited failures from blocking unrelated PRs and will turn red when a listed test starts passing.
Activity
test(ci): run native_proof_buffer_views per PR again after #8302 (#8321)
docs(changelog): add the fragment for the #8264 closeout
test(ci): close out #8264 — no suite exclusions remain (#8335)
proggeramlug commentedon Aug 17, 2026
All eight assertions are green and
SUITE_EXCLUSIONSis empty: the sixnative_proof_buffer_viewsones via #8302 (un-excluded in #8321), andshadow_slot_hygiene::canonical_str_local_keeps_shadow_binding_and_tag_dispatched_ops+typed_feedback::typed_feedback_guards_direct_class_field_specializationvia #8333 (un-excluded in #8335). Verified 45/45, 13/13, 17/17 on main.