Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://jenkins.onosproject.org/job/FUNC-pipeline-master/1698/

...

HTML
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/FUNCintentRest_master_20-builds_graph.jpg", alt="FUNCintentRest", style="width:525px;height:350px;border:0">

commit bb93b6e7ff2ec8b25df274994d511eb5809ee937 4330078de16d4fdbe716c3947d16fa24472fb3b5 (HEAD -] master, origin/master, origin/HEAD)
Author: Yi Tseng Jordan Halterman [yi@opennetworkingjordan@opennetworking.org]
AuthorDate: Wed Feb 12 14:46:07 2020 -0800Tue May 21 11:27:50 2019 -0700
Commit: Yi Tseng pier [yi@opennetworkingpier@opennetworking.org]
CommitDate: Wed Mon Feb 12 17 09:2242:13 2020 -0800
Add missing route to Roadm UI
+0100

Support user-provided timeouts in intra-cluster communication service

Case 1: Pull onos branch and build onos on Teststation. - PASS

...

  • 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS (tick)
  • 2000.2 IPV4: Add point intents between h1 and h9 - PASS (tick)
  • 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State PassedFailed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State PassedFailed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents Passed
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)FAIL (error)
    • Assertion Result for Dualstack1 IPV4 with mac address point intents
    • Install Intent State Passed
    • Flow duration check failed
  • 2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)FAIL (error)
    • Assertion Result for VLAN IPV4 with mac address point intents
    • Install Intent State Passed
    • Flow duration check failed
  • 2000.8 1HOP: Add point intents between h1 and h3 - PASS (tick)FAIL (error)
    • Assertion Result for 1HOP IPV4 with no mac address point intents
    • Install Intent State Passed
    • Flow duration check failed

Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL

...

  • 3000.1 NOOPTION: Install and test single point to multi point intents - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with no options set
    • Initial Intent State Passed
    • Intial Flow State Failed
    • Initial Ping Failed
    • Bad Sender Ping Passed
    • Bad Recipient Ping Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Failed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Failed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents Passed
  • 3000.2 IPV4: Install and test single point to multi point intents - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
  • 3000.3 IPV4_2: Add single point to multi point intents - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addresses
  • 3000.4 VLAN: Add single point to multi point intents - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLAN
  • 3000.5 VLAN: Add single point to multi point intents - FAIL (error)
    • Assertion results for single to multi point intent with VLAN treatment

...