Skip to content

Add RFC for testing CRCR L4 behavior against production PyTorch - #112

Open
can-gaa-hou wants to merge 2 commits into
pytorch:masterfrom
can-gaa-hou:crcr_l4
Open

can-gaa-hou wants to merge 2 commits into
pytorch:masterfrom
can-gaa-hou:crcr_l4

Conversation

@can-gaa-hou

Copy link
Copy Markdown

No description provided.

@albanD albanD left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good to me.

This RFC proposes how to do that with the existing canary repo [`pytorch/crcr-test`](https://github.com/pytorch/crcr-test):

1. Promote `pytorch/crcr-test` from allowlist level **L3 → L4** in the production CRCR relay.
2. Use a new, purpose-built workflow (`crcr-l4-ci.yml`), gated by a PR **label** (`ciflow/crcr/crcr-test-L4`), to validate that at L4 a Check Run is created on the upstream PR and can block merge, with effectively zero blast radius on other people's PRs.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would be curious what are the next steps after that.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @albanD, sorry for the late reply.

There are several steps after we have completed the test for L4:

  1. Start drafting the criteria for L4 (both promotion and demotion).
  2. Optimize the check-run behaviour and HUD from L1 to L4 as a whole.
  3. Since L4 could block the PR from merging, we need to consider a way to make it safer and more stable for unrelated failures (maybe with AI integration). But it is not a high-priority task for now since we won't have a real L4 repo within a short period of time.

L4 is attractive and could be an ultra-purpose for the downstream repos to engage with the CRCR system, so would be a lot of work to do :)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's add these details here! And Yes that sounds good.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the review! Added below. Please take a look when you have time @albanD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CRCR][L4] Define how to test the L4 system — document design / propose RFC

2 participants