From 62ebd9d465d3eba43cda02b4c63fd5718df0eaff Mon Sep 17 00:00:00 2001
From: "127.0.0.1" <127.0.0.1@web>
Date: Fri, 10 May 2019 19:31:00 +0000
Subject: [PATCH] This reverts commit 0e3209b2615de48c7542ff9cfecc0516def1008f
---
wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn b/wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn
index 74457d8165e..847e36d89b1 100644
--- a/wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn
+++ b/wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn
@@ -50,9 +50,7 @@ area:
a replica of our Jenkins setup, also using nested virtualization,
with a poor Internet connection but faster CPU cores
- 26 minutes (including 5 minutes for building the website) on bare metal,
- with a poor Internet connection but a fast (Intel E-2134) CPU;
- same in a VM on that machine, i.e. using nested virtualization
- (only 1 concurrent build).
+ with a poor Internet connection but a fast (Intel E-2134) CPU
* Waiting time in queue for ISO build and test jobs is acceptable
most of the time, but too high during peak load periods:
@@ -252,7 +250,7 @@ Cons:
- Left to benchmark:
- Higher density: run 2 Jenkins worker VMs on this node (neither our
build system nor test suite implementation allow running 2 jobs at
- a time on the same system) and make them busy at the same time.
+ a time on the same system)
## Run builds and/or tests in the cloud
--
GitLab