Enable Inductor CPU UT on windows

[LifengWang]

No description provided.

[Copilot]

Pull Request Overview

This PR adds infrastructure to enable and run PyTorch Inductor CPU unit tests on Windows, including automated reporting of test results.

• Adds a Python script to parse test logs and generate HTML failure reports
• Provides PowerShell scripts for installing nightly PyTorch builds and running CPU unit tests
• Implements a Jenkins/Groovy pipeline to orchestrate the testing workflow and email results

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File	Description
scripts/windows_inductor/report_ut_win.py	Parses test log files for failures and generates HTML reports with PyTorch nightly version tracking
scripts/windows_inductor/install_nightly_pytorch.ps1	Manages conda environment creation and installs nightly PyTorch CPU builds with test dependencies
scripts/windows_inductor/cpu_ut.ps1	Executes Inductor CPU unit tests with and without C++ wrapper, logging results to versioned directories
groovy/inductor_ut_windows.groovy	Defines Jenkins pipeline stages for environment setup, test execution, report generation, and email notifications

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Filename comment 'parse_test_logs.py' does not match actual filename 'report_ut_win.py'.

Suggested change

	# parse_test_logs.py
	# report_ut_win.py

[Copilot]

Usage message references incorrect filename 'parse_test_logs.py' instead of 'report_ut_win.py'.

[Copilot]

Pull Request Overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The regex pattern does not allow test methods or class names to start with digits (e.g., test_2d_conv or Test123). The pattern [A-Za-z_][A-Za-z0-9_]* requires the first character to be a letter or underscore. Consider using [A-Za-z0-9_]+ to allow digits anywhere in the name, or verify that the naming convention strictly prohibits leading digits.

Suggested change

	pattern = r"FAILED \[([0-9.]+)s\] (.*?\.py)::([A-Za-z_][A-Za-z0-9_]*)::([A-Za-z_][A-Za-z0-9_]*)"
	pattern = r"FAILED \[([0-9.]+)s\] (.*?\.py)::([A-Za-z0-9_]+)::([A-Za-z0-9_]+)"

[Copilot]

The docstring is missing the nightly_version parameter which is required by the function signature.

Suggested change

	all_failed_tests (list): The list of all failed tests extracted from log files.
	all_failed_tests (list): The list of all failed tests extracted from log files.
	nightly_version (str): The version string for the nightly build.

[Copilot]

If pip list doesn't find 'torch' or the version format doesn't match the regex pattern, $pt_nightly will be empty, causing issues when creating the log directory path. Add error handling to verify the torch package exists and the version was successfully extracted before proceeding.

Suggested change

	$line = (pip list | Select-String "torch ").Line
	$pt_nightly = [regex]::Match($line, "dev(\d+)").Groups[1].Value
	$line = (pip list | Select-String "torch ").Line
	if (-not $line) {
	Write-Error "Could not find 'torch' in pip list. Please ensure PyTorch is installed in the environment."
	exit 1
	}
	$pt_nightly = [regex]::Match($line, "dev(\d+)").Groups[1].Value
	if (-not $pt_nightly) {
	Write-Error "Could not extract nightly build number from torch version. Version string: $line"
	exit 1
	}

[Copilot]

Using /K keeps the command prompt window open after execution, which may cause the pipeline to hang waiting for manual closure. Use /C instead to execute the command and close automatically: cmd.exe \"/C\".

Suggested change

	cmd.exe "/K" (
	cmd.exe "/C" (