Checking out of memory

[mikhailnikolaev]

The global runner takes additional parameter that defines maximum RAM size that the runner can consume. If test takes more, then it will be killed. Also, guaranteed out of memory checking is performed the same way as guaranteed timeout checking.

This PR solves the issue #172.

[tomjaguarpaw]

Looks excellent

[awf]

/AzurePipelines help

[azure-pipelines]

Supported commands

• help:
• Get descriptions, examples and documentation about supported commands
• Example: help "command_name"
• list:
• List all pipelines for this repository using a comment.
• Example: "list"
• run:
• Run all pipelines or a specific pipeline for this repository using a comment. Use this command by itself to trigger all related pipelines, or specify a pipeline to run.
• Example: "run" or "run pipeline_name"
• where:
• Report back the Azure DevOps orgs that are related to this repository and org
• Example: "where"

See additional documentation.

[awf]

There is $null, which you would need to check using “$x -eq $null”. It’s a little tricky as PowerShell does so much null-conversion anyway, so there’s an argument for the sentinel too.

[msftclas]

All CLA requirements met.

[tomjaguarpaw]

I'm happy with this. It seems like squash merge might be most appropriate but I'll leave it up to you.