[CI] execute all piecewise compilation tests together

[ZJY0516]

Purpose

execute all compilation tests together
Link #24376 for visibility

Test Plan

pytest tests/compile/piecewise/

Test Result

---

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• The test plan, such as providing test command.
• The test results, such as pasting the results comparison before and after, or e2e results
• (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
• (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

[gemini-code-assist]

Code Review

This pull request refactors compilation tests to use unique library names for custom PyTorch ops, preventing conflicts when tests are run together. The approach of using Path(__file__).stem is a good way to ensure uniqueness. However, it's not robust to filenames containing hyphens, which would lead to invalid library names. I've suggested a small fix to sanitize the filenames to prevent future test failures.

[ZJY0516]

@ProExpertProg comparing PR #23257 with this approach, which do you prefer?

My thinking is: since only one attention type needs the internal counter, applying it everywhere seems a little strange.

[ProExpertProg]

I think this is more complicated than necessary, I would just extract silly::attention into a common file and use it everywhere. #23257 does that roughly

[ProExpertProg]

@ZJY0516 just because others don't use the counter doesn't mean it has to be different. You can just think of the counter as always there and then some tests just don't use it. If there existed a silly::attention with a counter and you added a test that didn't need it, you wouldn't duplicate the op to create one without a counter, right?

[ZJY0516]

ok, I will implement it like #23257.

[ProExpertProg]

Nice work, good cleanup. I also like calling the file silly_attention.py better than testing_ops.py in my PR!!

[ProExpertProg]

Just comments