Total Statistics | Total | Pass | Fail | Skip | Elapsed | Pass / Fail / Skip |
---|---|---|---|---|---|---|
All Tests | 1 | 0 | 1 | 0 | 00:00:01 |
Statistics by Tag | Total | Pass | Fail | Skip | Elapsed | Pass / Fail / Skip |
---|---|---|---|---|---|---|
critical | 1 | 0 | 1 | 0 | 00:00:01 |
Statistics by Suite | Total | Pass | Fail | Skip | Elapsed | Pass / Fail / Skip |
---|---|---|---|---|---|---|
1 | 0 | 1 | 0 | 00:00:06 |
Full Name: | controller-drb-precedence-longevity.txt |
---|---|
Documentation: | DOMRpcBroker testing: RPC Provider Precedence Copyright (c) 2017 Cisco Systems, Inc. and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html The aim is to establish that remote RPC implementations have lower priority than local ones, which is to say that any movement of RPCs on remote nodes does not affect routing as long as a local implementation is available. |
Source: | /w/workspace/controller-csit-3node-drb-precedence-longevity-only-calcium/test/csit/suites/controller/dom_rpc_broker/rpc_provider_precedence_longevity.robot |
Start / End / Elapsed: | 20250315 23:29:39.171 / 20250315 23:29:45.400 / 00:00:06.229 |
Status: | 1 test total, 0 passed, 1 failed, 0 skipped |
Documentation: | Create a list of possible constant responses on the node with unregistered rpc. |
---|---|
Start / End / Elapsed: | 20250315 23:29:39.701 / 20250315 23:29:44.788 / 00:00:05.087 |
Documentation: | Closes all open connections. |
---|---|
Start / End / Elapsed: | 20250315 23:29:45.399 / 20250315 23:29:45.399 / 00:00:00.000 |
Full Name: | controller-drb-precedence-longevity.txt.Rpc_Provider_Precedence_Longevity |
---|---|
Documentation: | Repeat the tested scenario for 24h. |
Tags: | critical |
Start / End / Elapsed: | 20250315 23:29:44.788 / 20250315 23:29:45.399 / 00:00:00.611 |
Status: | FAIL |
Message: |
Documentation: | Test case setup which explicitly ignores previous failure and logs test case name to Karaf log. Needed if the recommended default is to be overriden. |
---|---|
Start / End / Elapsed: | 20250315 23:29:44.789 / 20250315 23:29:45.168 / 00:00:00.379 |
Documentation: | Register global rpc on given nodes of the cluster. |
---|---|
Start / End / Elapsed: | 20250315 23:29:45.168 / 20250315 23:29:45.382 / 00:00:00.214 |
Documentation: | Some positive checks report false success for a short time. This keyword verifies no failure does happen within timeout period. This implementation needs more complicated logic than, Verify_Keyword_Never_Passes_Within_Timeout, so use that keyword in case you have a negative check handy. |
---|---|
Start / End / Elapsed: | 20250315 23:29:45.382 / 20250315 23:29:45.382 / 00:00:00.000 |
Documentation: | Unregister global rpc on given nodes of the cluster. |
---|---|
Start / End / Elapsed: | 20250315 23:29:45.383 / 20250315 23:29:45.383 / 00:00:00.000 |