[SERVER-32087] Run test stage of sys-perf and mongo-perf failures should lead to red evergreen boxes Created: 11/Oct/17  Updated: 30/Oct/23  Resolved: 08/Dec/17

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 3.0.16, 3.2.19, 3.4.11, 3.6.1

Type: Task Priority: Major - P3
Reporter: David Daly Assignee: Vick Mena (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-30770 system_perf.yml: Use new DSI interfac... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6, v3.4, v3.2, v3.0
Sprint: Performance 2017-12-11
Participants:

 Description   

Currently only the analysis phase of our tests will turn an evergreen box red. Failures during the test themselves turn the evergreen box purple. Those purple boxes should be red. Failures during provisioning and mongo setup should remain purple.

https://github.com/mongodb/mongo/blob/master/etc/perf.yml



 Comments   
Comment by Githook User [ 08/Dec/17 ]

Author:

{'name': 'Vick Mena', 'email': 'vickmena@gmail.com', 'username': 'vmenajr'}

Message: SERVER-32087: Run test stage of sys-perf and mongo-perf failures should lead to red evergreen boxes
Branch: v3.0
https://github.com/mongodb/mongo/commit/b4172b971d6223ab22e070e738ca69530ff79277

Comment by Githook User [ 08/Dec/17 ]

Author:

{'name': 'Vick Mena', 'email': 'vickmena@gmail.com', 'username': 'vmenajr'}

Message: SERVER-32087: Run test stage of sys-perf and mongo-perf failures should lead to red evergreen boxes
Branch: v3.2
https://github.com/mongodb/mongo/commit/53adeef7dbf5170a94f3e6d25425e8524fb9d062

Comment by Githook User [ 08/Dec/17 ]

Author:

{'name': 'Vick Mena', 'email': 'vickmena@gmail.com', 'username': 'vmenajr'}

Message: SERVER-32087: Run test stage of sys-perf and mongo-perf failures should lead to red evergreen boxes
Branch: v3.4
https://github.com/mongodb/mongo/commit/d8e45a195c35d719ea2757bd92865937db952612

Comment by Githook User [ 08/Dec/17 ]

Author:

{'name': 'Vick Mena', 'email': 'vickmena@gmail.com', 'username': 'vmenajr'}

Message: SERVER-32087: Run test stage of sys-perf and mongo-perf failures should lead to red evergreen boxes
Branch: v3.6
https://github.com/mongodb/mongo/commit/835d8479c548811f2326d1ee2dd76b9a971ba464

Comment by Githook User [ 08/Dec/17 ]

Author:

{'name': 'Vick Mena', 'email': 'vickmena@gmail.com', 'username': 'vmenajr'}

Message: SERVER-32087: Run test stage of sys-perf and mongo-perf failures should lead to red evergreen boxes
Branch: master
https://github.com/mongodb/mongo/commit/7761221a9431ba354ac7505fde2a0d12b439b8a0

Comment by Henrik Ingo (Inactive) [ 27/Nov/17 ]

Btw, after doing this change for System Performance, we now have a case where a test times out, and this is also reported as red, rather than purple, but still no test results: https://evergreen.mongodb.com/task/sys_perf_linux_3_node_replSet_core_workloads_WT_611220640b0fd32fcf81f47cdae6882a26bbac0b_17_11_26_17_15_01

I'm not sure this was what we expected from Evergreen? I'll investigate further.

Comment by Henrik Ingo (Inactive) [ 27/Nov/17 ]

On second thought, SERVER-30770 was only concerned with system_perf.yml. This is still relevant for Microbenchmarks, but no longer in scope for PM-820. Possibly also lower priority?

Comment by Henrik Ingo (Inactive) [ 27/Nov/17 ]

This change was done as part of SERVER-30770

Comment by David Daly [ 13/Nov/17 ]

Adding this to PM-820 after discussion. It is relevant to the test control work.

Comment by Githook User [ 13/Nov/17 ]

Author:

{'name': 'Henrik Ingo', 'username': 'henrikingo', 'email': 'henrik.ingo@mongodb.com'}

Message: PERF-1152 Disable iperf3 (emergency fix)

Somehow iperf3 tests are failing, causing system failure. This makes tests
succeed again. We'll continue with figuring out why iperf3 is failing so
that we can re-enable it.

See also PERF-1115
Branch: master
https://github.com/10gen/dsi/commit/a4a6323a31b4dd716049e60f8105f1cf97a6eace

Generated at Thu Feb 08 04:29:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.