Add aten/src/ATen/native/quantized/cpu/ path to CPU quantization merge rule

[atalman]

Observing following PR: #115329
Comment from author: #115329 (comment)

pytorchbot merge failed.
Reason is this logic, we expect all files in PR to match one merge rule:

pytorch/.github/scripts/trymerge.py

Lines 1310 to 1324 in 110339a

	for fname in changed_files:
	if not patterns_re.match(fname):
	non_matching_files.append(fname)
	if len(non_matching_files) > 0:
	num_matching_files = len(changed_files) - len(non_matching_files)
	if num_matching_files > reject_reason_score:
	reject_reason_score = num_matching_files
	reject_reason = "\n".join(
	(
	f"Not all files match rule `{rule_name}`.",
	f"{num_matching_files} files matched, but there are still non-matching files:",
	f"{','.join(non_matching_files[:5])}{', ...' if len(non_matching_files) > 5 else ''}",
	)
	)
	continue

This should mitigate the issue, followup will post a PR to refactor this code to allow cross rule matching of approvers

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/116145

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (4 Unrelated Failures)

As of commit 559074f with merge base f88c9af ():

UNSTABLE - The following jobs failed but were likely due to flakiness present on trunk and has been marked as unstable:

• pull / linux-focal-py3.11-clang10 / test (dynamo, 3, 7, linux.2xlarge, unstable) (gh)
  test_unary_ufuncs.py::TestUnaryUfuncsCPU::test_reference_numerics_large__refs_special_multigammaln_mvlgamma_p_3_cpu_int64
• pull / linux-focal-py3.11-clang10 / test (dynamo, 6, 7, linux.2xlarge, unstable) (gh)
  test_unary_ufuncs.py::TestUnaryUfuncsCPU::test_reference_numerics_large__refs_special_multigammaln_mvlgamma_p_5_cpu_int32
• pull / linux-focal-py3.8-clang10 / test (dynamo, 3, 7, linux.2xlarge, unstable) (gh)
  test_unary_ufuncs.py::TestUnaryUfuncsCPU::test_reference_numerics_large__refs_special_multigammaln_mvlgamma_p_5_cpu_int32
• pull / linux-focal-py3.8-clang10 / test (dynamo, 6, 7, linux.2xlarge, unstable) (gh)
  test_unary_ufuncs.py::TestUnaryUfuncsCPU::test_reference_numerics_large__refs_special_multigammaln_mvlgamma_p_3_cpu_int64

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[malfet]

Q: Why do we need 3 different rules? For x86 CPU quantization as well as for CPU frontend reviewers are the same, should those two rules be folded together?

[jgong5]

Q: Why do we need 3 different rules? For x86 CPU quantization as well as for CPU frontend reviewers are the same, should those two rules be folded together?

This is because the rules are organized by the modules and the reviewers happen to be the same.

[atalman]

@pytorchmergebot merge -f "All required jobs are passing"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here