SRDynamicConf at 10 Apr 2019 00:46:44

<img src="https://jenkins.onosproject.org/view/QA/job/postjob-Fabric2/lastSuccessfulBuild/artifact/SRDynamicConf_onos-1.15_20-builds_graph.jpg", alt="SRDynamicConf", style="width:525px;height:350px;border:0">
commit 85801f2d4ccbcca154a7eb96d202b599fc34436a (HEAD -] onos-1.15, origin/onos-1.15)
Author: Jordan Halterman [jordan@opennetworking.org]
AuthorDate: Tue Mar 5 18:44:03 2019 -0800
Commit: pier [pier@opennetworking.org]
CommitDate: Tue Apr 9 20:47:14 2019 +0200

Modify OpenFlow provider to avoid stats collection when switch is under high load

Case 13: Changing port configuration from untagged 10 to tagged 10, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 23: Changing port configuration from untagged 10 to tagged 20 and native 10, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 33: Changing port configuration from untagged 10 to untagged 110, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 43: Changing port configuration from untagged 10 to tagged 20, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 53: Changing port configuration from untagged 10 to tagged 20 with native 10, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 63: Changing port configuration from untagged 10 to tagged 120 with native 110, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 73: Changing port configuration from tagged 10 to untagged 10, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 83: Changing port configuration from tagged 20 to tagged 20 and native 10, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 93: Changing port configuration from tagged 10 to tagged 120 with native 110, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 103: Changing port configuration from tagged 10 and native 20 to untagged 20, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 113: Changing port configuration from tagged 20 and native 10 to tagged 20, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 123: Changing port configuration from tagged 20 and native 10 to tagged 20 and native 110, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 133: Changing port configuration from tagged 20 and native 10 to tagged 120 and native 10, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 143: Changing port configuration from untagged 10 to tagged 20, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 153: Changing port configuration from untagged 10 to tagged 120, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 163: Changing port configuration from untagged 10 to tagged 20 and native 10, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 173: Changing port configuration from tagged 20 to tagged 120, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 183: Changing port configuration from tagged 20 to tagged 20 and native 10, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 193: Changing port configuration from tagged 20 and native 10 to untagged 20, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 203: Changing port configuration from tagged 20 and native 10 to tagged 20, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 213: Changing port configuration from tagged 20 and native 10 to tagged 20 and native 110, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 223: Changing port configuration from tagged 20 and native 10 to tagged 120 and native 10, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 233: Consecutive configuration changes, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 243: Changing port configuration from 10.0.2.254/24 to 10.0.6.254/24, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL