Don't Merge! Regression PR perf testing *with* metadata validation

[OPSTestProduction]

No description provided.

[e2ebd7]

Docs Build status updates of commit 9d22351:

🕙 Full build: the average full build time is 7 min(s) 21 sec(s), this is based on the last 91 build(s) for this repository.

[e2ebd6]

Docs Build status updates of commit 9d22351:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
docs-ref-conceptual/TestingPullRequest.md	⚠️Warning	View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)	Details

docs-ref-conceptual/TestingPullRequest.md

• [Warning-InvalidMetadata] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
• [Warning-InvalidMetadata] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
• [Warning-InvalidMetadata] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
• [Warning-W.UndefinedValue] the value invalid_type is undefined for metadata content_type
• [Warning-W.UndefinedValue] the value invalid_type is undefined for metadata content_type
• [Warning-W.UndefinedValue] the value invalid_type is undefined for metadata content_type
• Line 7: [Warning-InvalidFileLink] Invalid file link:(~/nonexisted1.md).
• Line 7: [Warning-InvalidFileLink] Invalid file link:(~/nonexisted1.md).
• Line 7: [Warning-InvalidFileLink] Invalid file link:(~/nonexisted1.md).
• Line 8: [Warning-InvalidFileLink] Invalid file link:(~/nonexisted2.md).
• Line 8: [Warning-InvalidFileLink] Invalid file link:(~/nonexisted2.md).
• Line 8: [Warning-InvalidFileLink] Invalid file link:(~/nonexisted2.md).
• Line 9: [Warning-InvalidFileLink] Invalid file link:(~/nonexisted3.md).
• Line 9: [Warning-InvalidFileLink] Invalid file link:(~/nonexisted3.md).
• Line 9: [Warning-InvalidFileLink] Invalid file link:(~/nonexisted3.md).

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel