test: [TRTLLM-4334] Create 1.0 criteria scope from API stability references
/bot run
Thanks for preparing the MR, @syuoni !
June
I discussed it with @syuoni , and here is our plan:
- This MR partitions the LLM APIs into two sets,
references_committed_v1andreferencesreferences_committed_v1is for committed APIs; changes here will require stricter approval.referencescontains the remaining APIs and will have less strict approval, allowing for faster iteration.
- Some non-commited APIs could grow to be committed; just move them into the corresponding set
Once this MR is merged, we can start to align the committed API scope. The approval mechanism will be included later. cc @juney-nvidia @laikhtewari for viz.
/bot run
/bot run
PR_Github #523 [ run ] triggered by Bot
PR_Github #523 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #447 completed with status: 'SUCCESS'
/bot reuse-pipeline
PR_Github #562 [ reuse-pipeline ] triggered by Bot
PR_Github #562 [ reuse-pipeline ] completed with state SUCCESS
Reusing PR_Github #523 for commit 65e3545