aboutsummaryrefslogtreecommitdiffstats
path: root/resources/tools/presentation
diff options
context:
space:
mode:
authorViliam Luc <vluc@cisco.com>2022-05-02 09:27:56 +0200
committerViliam Luc <vluc@cisco.com>2022-05-02 09:34:18 +0200
commit2948af03c8240706b54c8f059423779f3de0877c (patch)
tree403f1a7bfdd946f87ed0fa9c59c505f1d2428bb0 /resources/tools/presentation
parent373375dbbc35bbcb5c5a3d4ab3342efc4870bb51 (diff)
trending: fix failing trending job
3n-aws job was recently removed which caused trending jobs to fail. For historical reason we keep 3n-aws in trending until 180 days period pass. Signed-off-by: Viliam Luc <vluc@cisco.com> Change-Id: I7b59fc4b6f1b46bf910bc540cf37dd042df9c64a
Diffstat (limited to 'resources/tools/presentation')
-rw-r--r--resources/tools/presentation/specifications/trending/data_sets.yaml5
-rw-r--r--resources/tools/presentation/specifications/trending/elements.yaml13
-rw-r--r--resources/tools/presentation/specifications/trending/environment.yaml2
3 files changed, 1 insertions, 19 deletions
diff --git a/resources/tools/presentation/specifications/trending/data_sets.yaml b/resources/tools/presentation/specifications/trending/data_sets.yaml
index 115edf78bd..a828f6d7f3 100644
--- a/resources/tools/presentation/specifications/trending/data_sets.yaml
+++ b/resources/tools/presentation/specifications/trending/data_sets.yaml
@@ -38,9 +38,6 @@
table-last-failed-tests-2n-dnv:
csit-vpp-perf-mrr-daily-master-2n-dnv:
- "lastCompletedBuild"
- table-last-failed-tests-3n-aws:
- csit-vpp-perf-mrr-weekly-master-3n-aws:
- - "lastCompletedBuild"
table-last-failed-tests-2n-aws:
csit-vpp-perf-mrr-weekly-master-2n-aws:
- "lastCompletedBuild"
@@ -257,7 +254,7 @@
plot-performance-trending-vpp-3n-aws:
csit-vpp-perf-mrr-weekly-master-3n-aws:
start: 5
- end: "lastCompletedBuild"
+ end: 45
max-builds: 26
# 2n-aws
diff --git a/resources/tools/presentation/specifications/trending/elements.yaml b/resources/tools/presentation/specifications/trending/elements.yaml
index 34f55fa77d..25369e3495 100644
--- a/resources/tools/presentation/specifications/trending/elements.yaml
+++ b/resources/tools/presentation/specifications/trending/elements.yaml
@@ -505,19 +505,6 @@
- "msg"
- type: "table"
- title: "Last failed tests (last builds) VPP 3n-aws"
- algorithm: "table_last_failed_tests"
- output-file-ext: ".txt"
- output-file: "{DIR[STATIC,VPP]}/last-failed-tests-vpp-3n-aws-mrr"
- data: "table-last-failed-tests-3n-aws"
- filter: "'MRR'"
- parameters:
- - "name"
- - "parent"
- - "status"
- - "msg"
-
-- type: "table"
title: "Last failed tests (last builds) VPP 2n-aws"
algorithm: "table_last_failed_tests"
output-file-ext: ".txt"
diff --git a/resources/tools/presentation/specifications/trending/environment.yaml b/resources/tools/presentation/specifications/trending/environment.yaml
index 805ee087d2..1f28660319 100644
--- a/resources/tools/presentation/specifications/trending/environment.yaml
+++ b/resources/tools/presentation/specifications/trending/environment.yaml
@@ -172,7 +172,6 @@
- "last-failed-tests-vpp-2n-dnv-mrr"
- "last-failed-tests-vpp-3n-dnv-mrr"
- "last-failed-tests-vpp-2n-aws-mrr"
- - "last-failed-tests-vpp-3n-aws-mrr"
- "last-failed-tests-dpdk-2n-skx-mrr"
- "last-failed-tests-dpdk-3n-skx-mrr"
- "last-failed-tests-dpdk-2n-clx-mrr"
@@ -195,7 +194,6 @@
- "https://jenkins.fd.io/view/csit/job/csit-vpp-perf-mrr-daily-master-2n-dnv"
- "https://jenkins.fd.io/view/csit/job/csit-vpp-perf-mrr-daily-master-3n-dnv"
- "https://jenkins.fd.io/view/csit/job/csit-vpp-perf-mrr-weekly-master-2n-aws"
- - "https://jenkins.fd.io/view/csit/job/csit-vpp-perf-mrr-weekly-master-3n-aws"
- "https://jenkins.fd.io/view/csit/job/csit-dpdk-perf-mrr-weekly-master-2n-skx"
- "https://jenkins.fd.io/view/csit/job/csit-dpdk-perf-mrr-weekly-master-3n-skx"
- "https://jenkins.fd.io/view/csit/job/csit-dpdk-perf-mrr-weekly-master-2n-clx"
lass="cm"> event_type = vlib_process_get_events (vm, &event_data); switch (event_type) { case ~0: // no events => timeout break; case EVENT1: for (i = 0; i < vec_len (event_data); i++) handle_event1 (mm, event_data[i]); break; case EVENT2: for (i = 0; i < vec_len (event_data); i++) handle_event2 (vm, event_data[i]); break; // ... and so forth for each event type default: // This should never happen... clib_warning ("BUG: unhandled event type %d", event_type); break; } vec_reset_length (event_data); // Timer expired, call periodic function if (vlib_process_suspend_time_is_zero (poll_time_remaining)) { example_periodic (vm); poll_time_remaining = EXAMPLE_POLL_PERIOD; } } // NOTREACHED return 0; } static VLIB_REGISTER_NODE (example_node) = { .function = example_process, .type = VLIB_NODE_TYPE_PROCESS, .name = "example-process", }; </pre></code> In this example, the VLIB process node waits for an event to occur, or for 10 seconds to elapse. The code demuxes on the event type, calling the appropriate handler function. Each call to vlib_process_get_events returns a vector of per-event-type data passed to successive vlib_process_signal_event calls; vec_len (event_data) >= 1. It is an error to process only event_data[0]. Resetting the event_data vector-length to 0 by calling vec_reset_length (event_data) - instead of calling vec_free (...) - means that the event scheme doesn t burn cycles continuously allocating and freeing the event data vector. This is a common coding pattern, well worth using when appropriate. */ /* * fd.io coding-style-patch-verification: ON * * Local Variables: * eval: (c-set-style "gnu") * End: */