search

microsoft / ADBench

Benchmarking various AD tools.
MIT License
107 stars 40 forks source link

Checking out of memory #177

Closed mikhailnikolaev closed 4 years ago

mikhailnikolaev commented 4 years ago

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.

awf commented 4 years ago

/AzurePipelines help

azure-pipelines[bot] commented 4 years ago
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 commented 4 years ago

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 commented 4 years ago

CLA assistant check
All CLA requirements met.