Change BytesAllocatedPerOperation to long? #4553
Build #20241030.10 had test failures
Details
- Failed: 31 (13.08%)
- Passed: 206 (86.92%)
- Other: 0 (0.00%)
- Total: 237
Annotations
Check failure on line 50 in Build log
azure-pipelines / performance-ci
Build log #L50
Bash exited with code '1'.
Check failure on line 136 in Build log
azure-pipelines / performance-ci
Build log #L136
Bash exited with code '1'.
Check failure on line 66 in Build log
azure-pipelines / performance-ci
Build log #L66
Bash exited with code '1'.
Check failure on line 66 in Build log
azure-pipelines / performance-ci
Build log #L66
Bash exited with code '1'.
Check failure on line 1 in x64_main_micro.Partition12.WorkItemExecution
azure-pipelines / performance-ci
x64_main_micro.Partition12.WorkItemExecution
The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.
Check failure on line 1 in x64_main_micro.Partition4.WorkItemExecution
azure-pipelines / performance-ci
x64_main_micro.Partition4.WorkItemExecution
The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.
Check failure on line 1 in x64_main_micro.Partition5.WorkItemExecution
azure-pipelines / performance-ci
x64_main_micro.Partition5.WorkItemExecution
The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.
Check failure on line 1 in x64_main_micro.Partition6.WorkItemExecution
azure-pipelines / performance-ci
x64_main_micro.Partition6.WorkItemExecution
The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.