The GitHub Actions job "mainline-only" on tvm-ffi.git/main has failed. Run started by GitHub user tqchen (triggered by tqchen).
Head commit for run: 60e0614d6ca0ae3c15df60596131f9f8a3a2e6c2 / Tianqi Chen <[email protected]> [CORE] Staging Object Tying Feature (#696) ## Summary Object tying remains compiled but is deliberately staged dormant: canonical-wrapper detection returns false, while C++, Python-defined dataclasses, and Rust objects continue to use matching legacy allocation and deletion paths. This staging has three goals: - let downstream projects upgrade without making existing generated caches depend on the new allocator contract; - keep the compatibility change compact by changing only the activation/allocation boundary instead of removing the object-tying implementation; - preserve the custom allocator API and a clean path for a later coordinated object-tying activation. Legacy wrapper identity and reference-count expectations are restored, while activation-only tying tests remain as skipped coverage for the later rollout. ## Testing - C++: 465 enabled tests passed (2 disabled). - Python: 2,381 passed, 78 skipped, 2 expected failures. - Rust: 138 unit/integration tests and 3 doctests passed; formatting is clean. - Pre-commit: all changed-file checks passed, including ruff, ty, and clang-format. - Order-balanced microbenchmarks place the dormant path about 1.3-7.9% behind active tying and 4.7-12.5% ahead of a full revert. Report URL: https://github.com/apache/tvm-ffi/actions/runs/30679409507 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
