p4factory子目录下的run_all_tests

安装好p4factory之后,打算跑一下样例来测试是否正确。

但是,跑了targets目录内的basic_routing,make又报错了,但之前成功过,我想可能是长时间放置导致一些虚拟接口的问题,于是cd回上级目录,跑下全部的样例,看看是什么结果。

半个小时过去了,终于跑完了,可能是因为有其它进程的原因,导致某些样例没有通过。

**************************************
TESTS PASSED: 10/13
sudo killall -q behavioral-model
sudo killall -q drivers-switchapi
sudo killall -q drivers
sudo killall -q l2_switch_bmv2
sudo killall -q switch_bmv2
sudo killall -q basic_routing_bmv2
sudo killall -q drivers-switchsai
3 TESTS FAILED!
If some tests fail because extra packets are received, you may want to try disabling IPv6 with:
sudo sysctl -w net.ipv6.conf.eth0.disable_ipv6=1

于是在没有其它终端执行命令的情况下又跑了一遍,还是这个结果,于是打算按它提示的试一试。

basic_routing

终端A,执行./behavior-model

终端B,执行sudo python run_tests.py --test-dir tests/ptf-tests/

A的结果:

Resetting buffer
Resetting buffer
Cleaning all state (resetting all tables)
In ipv4_fib_set_default_action_on_miss
ipv4_fib: setting default action
In ipv4_fib_lpm_set_default_action_on_miss
ipv4_fib_lpm: setting default action
In rewrite_mac_set_default_action_on_miss
rewrite_mac: setting default action
In port_mapping_table_add_with_set_bd
port_mapping: adding entry
empty index: 0 **********
entry at index 0:
key:
standard_metadata_ingress_port: 0x00000001 (0 0 0 1),
action:
set_bd
action data:
bd: 0x0000000a (0 0 0 10),
********** In port_mapping_table_add_with_set_bd
port_mapping: adding entry
empty index: 1 **********
entry at index 1:
key:
standard_metadata_ingress_port: 0x00000002 (0 0 0 2),
action:
set_bd
action data:
bd: 0x0000000a (0 0 0 10),
********** In port_mapping_table_add_with_set_bd
port_mapping: adding entry
empty index: 2 **********
entry at index 2:
key:
standard_metadata_ingress_port: 0x00000003 (0 0 0 3),
action:
set_bd
action data:
bd: 0x00000014 (0 0 0 20),
********** In port_mapping_table_add_with_set_bd
port_mapping: adding entry
empty index: 3 **********
entry at index 3:
key:
standard_metadata_ingress_port: 0x00000004 (0 0 0 4),
action:
set_bd
action data:
bd: 0x00000014 (0 0 0 20),
********** In bd_table_add_with_set_vrf
bd: adding entry
empty index: 0 **********
entry at index 0:
key:
ingress_metadata_bd: 0x0000000a (0 0 0 10),
action:
set_vrf
action data:
vrf: 0x0000001e (0 0 0 30),
********** In bd_table_add_with_set_vrf
bd: adding entry
empty index: 1 **********
entry at index 1:
key:
ingress_metadata_bd: 0x00000014 (0 0 0 20),
action:
set_vrf
action data:
vrf: 0x0000001e (0 0 0 30),
********** In ipv4_fib_lpm_table_add_with_fib_hit_nexthop
ipv4_fib_lpm: adding entry
empty index: 0 **********
entry at index 0:
key:
ingress_metadata_vrf: 0x0000001e (0 0 0 30), ipv4_dstAddr: 0xc0a80000 (192 168 0 0),
prefix_length:
48
action:
fib_hit_nexthop
action data:
nexthop_index: 0x00000001 (0 0 0 1),
********** In ipv4_fib_lpm_table_add_with_fib_hit_nexthop
ipv4_fib_lpm: adding entry
empty index: 1 **********
entry at index 1:
key:
ingress_metadata_vrf: 0x0000001e (0 0 0 30), ipv4_dstAddr: 0x0a000000 (10 0 0 0),
prefix_length:
40
action:
fib_hit_nexthop
action data:
nexthop_index: 0x00000003 (0 0 0 3),
********** In nexthop_table_add_with_set_egress_details
nexthop: adding entry
empty index: 0 **********
entry at index 0:
key:
ingress_metadata_nexthop_index: 0x00000001 (0 0 0 1),
action:
set_egress_details
action data:
egress_spec: 0x00000001 (0 0 0 1),
********** In rewrite_mac_table_add_with_rewrite_src_dst_mac
rewrite_mac: adding entry
empty index: 0 **********
entry at index 0:
key:
ingress_metadata_nexthop_index: 0x00000001 (0 0 0 1),
action:
rewrite_src_dst_mac
action data:
smac: 0x010101010101, dmac: 0x000101010101,
********** In nexthop_table_add_with_set_egress_details
nexthop: adding entry
empty index: 1 **********
entry at index 1:
key:
ingress_metadata_nexthop_index: 0x00000002 (0 0 0 2),
action:
set_egress_details
action data:
egress_spec: 0x00000002 (0 0 0 2),
********** In rewrite_mac_table_add_with_rewrite_src_dst_mac
rewrite_mac: adding entry
empty index: 1 **********
entry at index 1:
key:
ingress_metadata_nexthop_index: 0x00000002 (0 0 0 2),
action:
rewrite_src_dst_mac
action data:
smac: 0x010202020202, dmac: 0x000202020202,
********** In nexthop_table_add_with_set_egress_details
nexthop: adding entry
empty index: 2 **********
entry at index 2:
key:
ingress_metadata_nexthop_index: 0x00000003 (0 0 0 3),
action:
set_egress_details
action data:
egress_spec: 0x00000003 (0 0 0 3),
********** In rewrite_mac_table_add_with_rewrite_src_dst_mac
rewrite_mac: adding entry
empty index: 2 **********
entry at index 2:
key:
ingress_metadata_nexthop_index: 0x00000003 (0 0 0 3),
action:
rewrite_src_dst_mac
action data:
smac: 0x010303030303, dmac: 0x000303030303,
********** In nexthop_table_add_with_set_egress_details
nexthop: adding entry
empty index: 3 **********
entry at index 3:
key:
ingress_metadata_nexthop_index: 0x00000004 (0 0 0 4),
action:
set_egress_details
action data:
egress_spec: 0x00000004 (0 0 0 4),
********** In rewrite_mac_table_add_with_rewrite_src_dst_mac
rewrite_mac: adding entry
empty index: 3 **********
entry at index 3:
key:
ingress_metadata_nexthop_index: 0x00000004 (0 0 0 4),
action:
rewrite_src_dst_mac
action data:
smac: 0x010404040404, dmac: 0x000404040404,
********** Packet in on port 2 length 100; first bytes:
00010203 04050006 0708090a 08004500
new packet, len : 100, ingress : 2
rmt proc returns 0
ingress_pipeline: packet dequeued
parsing start
parsing parse_ethernet
parsing parse_ipv4
payload length: 66
all checksums are correct
Applying table port_mapping
Lookup key for port_mapping:
standard_metadata_ingress_port: 0x00000002,
table hit **********
entry at index 1:
key:
standard_metadata_ingress_port: 0x00000002 (0 0 0 2),
action:
set_bd
action data:
bd: 0x0000000a (0 0 0 10),
********** action set_bd
action data:
bd: 0x0000000a (0 0 0 10),
executing next table for action
Applying table bd
Lookup key for bd:
ingress_metadata_bd: 0x0000000a,
table hit **********
entry at index 0:
key:
ingress_metadata_bd: 0x0000000a (0 0 0 10),
action:
set_vrf
action data:
vrf: 0x0000001e (0 0 0 30),
********** action set_vrf
action data:
vrf: 0x0000001e (0 0 0 30),
executing next table for action
Applying table ipv4_fib
Lookup key for ipv4_fib:
ingress_metadata_vrf: 0x0000001e, ipv4_dstAddr: 0x0a000002,
table miss, applying default action
action on_miss
executing next table for action
Applying table ipv4_fib_lpm
Lookup key for ipv4_fib_lpm:
ingress_metadata_vrf: 0x0000001e, ipv4_dstAddr: 0x0a000002,
table hit **********
entry at index 1:
key:
ingress_metadata_vrf: 0x0000001e (0 0 0 30), ipv4_dstAddr: 0x0a000000 (10 0 0 0),
prefix_length:
40
action:
fib_hit_nexthop
action data:
nexthop_index: 0x00000003 (0 0 0 3),
********** action fib_hit_nexthop
action data:
nexthop_index: 0x00000003 (0 0 0 3),
executing next table for action
Applying table nexthop
Lookup key for nexthop:
ingress_metadata_nexthop_index: 0x00000003,
table hit **********
entry at index 2:
key:
ingress_metadata_nexthop_index: 0x00000003 (0 0 0 3),
action:
set_egress_details
action data:
egress_spec: 0x00000003 (0 0 0 3),
********** action set_egress_details
action data:
egress_spec: 0x00000003 (0 0 0 3),
executing next table for action
total length for outgoing pkt: 100
deparsing ethernet
deparsing ipv4
total length for outgoing meta: 26
copying metadata
deparsing standard_metadata
deparsing ingress_metadata
queuing system: packet dequeued
egress port set to 3
instance type set to 0
egress_pipeline: packet dequeued
parsing start
parsing parse_ethernet
parsing parse_ipv4
payload length: 66
extracting metadata
extracting all metadata for 0x7f1974000930
Applying table rewrite_mac
Lookup key for rewrite_mac:
ingress_metadata_nexthop_index: 0x00000003,
table hit **********
entry at index 2:
key:
ingress_metadata_nexthop_index: 0x00000003 (0 0 0 3),
action:
rewrite_src_dst_mac
action data:
smac: 0x010303030303, dmac: 0x000303030303,
********** action rewrite_src_dst_mac
action data:
smac: 0x010303030303, dmac: 0x000303030303,
executing next table for action
total length for outgoing pkt: 100
deparsing ethernet
deparsing ipv4
outgoing thread: packet dequeued
outgoing thread: sending pkt: Size[100]: Port[3]
Packet in on port 4 length 100; first bytes:
00010203 04050006 0708090a 08004500
new packet, len : 100, ingress : 4
rmt proc returns 0
ingress_pipeline: packet dequeued
parsing start
parsing parse_ethernet
parsing parse_ipv4
payload length: 66
all checksums are correct
Applying table port_mapping
Lookup key for port_mapping:
standard_metadata_ingress_port: 0x00000004,
table hit **********
entry at index 3:
key:
standard_metadata_ingress_port: 0x00000004 (0 0 0 4),
action:
set_bd
action data:
bd: 0x00000014 (0 0 0 20),
********** action set_bd
action data:
bd: 0x00000014 (0 0 0 20),
executing next table for action
Applying table bd
Lookup key for bd:
ingress_metadata_bd: 0x00000014,
table hit **********
entry at index 1:
key:
ingress_metadata_bd: 0x00000014 (0 0 0 20),
action:
set_vrf
action data:
vrf: 0x0000001e (0 0 0 30),
********** action set_vrf
action data:
vrf: 0x0000001e (0 0 0 30),
executing next table for action
Applying table ipv4_fib
Lookup key for ipv4_fib:
ingress_metadata_vrf: 0x0000001e, ipv4_dstAddr: 0xc0a80102,
table miss, applying default action
action on_miss
executing next table for action
Applying table ipv4_fib_lpm
Lookup key for ipv4_fib_lpm:
ingress_metadata_vrf: 0x0000001e, ipv4_dstAddr: 0xc0a80102,
table hit **********
entry at index 0:
key:
ingress_metadata_vrf: 0x0000001e (0 0 0 30), ipv4_dstAddr: 0xc0a80000 (192 168 0 0),
prefix_length:
48
action:
fib_hit_nexthop
action data:
nexthop_index: 0x00000001 (0 0 0 1),
********** action fib_hit_nexthop
action data:
nexthop_index: 0x00000001 (0 0 0 1),
executing next table for action
Applying table nexthop
Lookup key for nexthop:
ingress_metadata_nexthop_index: 0x00000001,
table hit **********
entry at index 0:
key:
ingress_metadata_nexthop_index: 0x00000001 (0 0 0 1),
action:
set_egress_details
action data:
egress_spec: 0x00000001 (0 0 0 1),
********** action set_egress_details
action data:
egress_spec: 0x00000001 (0 0 0 1),
executing next table for action
total length for outgoing pkt: 100
deparsing ethernet
deparsing ipv4
total length for outgoing meta: 26
copying metadata
deparsing standard_metadata
deparsing ingress_metadata
queuing system: packet dequeued
egress port set to 1
instance type set to 0
egress_pipeline: packet dequeued
parsing start
parsing parse_ethernet
parsing parse_ipv4
payload length: 66
extracting metadata
extracting all metadata for 0x7f1970000930
Applying table rewrite_mac
Lookup key for rewrite_mac:
ingress_metadata_nexthop_index: 0x00000001,
table hit **********
entry at index 0:
key:
ingress_metadata_nexthop_index: 0x00000001 (0 0 0 1),
action:
rewrite_src_dst_mac
action data:
smac: 0x010101010101, dmac: 0x000101010101,
********** action rewrite_src_dst_mac
action data:
smac: 0x010101010101, dmac: 0x000101010101,
executing next table for action
total length for outgoing pkt: 100
deparsing ethernet
deparsing ipv4
outgoing thread: packet dequeued
outgoing thread: sending pkt: Size[100]: Port[1]

B的结果:

WARNING: No route found for IPv6 destination :: (no default route?)
routing.TwoBdLpmTest ... ok ----------------------------------------------------------------------
Ran 1 test in 1.829s OK

2016/10/14

P4factory 运行结果展示 basic_routing 以及 ./run_all_tests 的运行结果的更多相关文章

  1. C# 获取当前服务器运行程序的根目录,获取当前运行程序物理路径

    C# 获取当前服务器运行程序的根目录,获取当前运行程序物理路径 string tmpRootDir = AppDomain.CurrentDomain.BaseDirectory;//获得当前服务器程 ...

  2. 未能加载文件或程序集“BLL”或它的某一个依赖项。生成此程序集的运行时比当前加载的运行时新,无法加载此程序集。

    今天使用VS2012创建项目的时候,考虑到项目中代码的重用性以及清晰简洁性,搭建了一个三层架构,但是在项目运行的时候,总是报错: “未能加载文件或程序集“BLL”或它的某一个依赖项.生成此程序集的运行 ...

  3. Docker在Linux上运行NetCore系列(一)配置运行DotNetCore控制台

    转发请注明此文章作者与路径,请尊重原著,违者必究. 系列文章:https://www.cnblogs.com/alunchen/p/10121379.html 本篇文章操作系统信息 Linux:ubu ...

  4. Ubuntu上运行Blender,在控制台上查看运行结果

    1.首先在控制台打开Blender. 具体操作:找到Blender的安装路径,我的是:/home/lcx/下载/blender-2.78c-linux-glibc219-x86_64 $cd /hom ...

  5. Singer 学习七 运行&&开发taps、targets (二 targets 运行说明)

    接上文: Singer 学习六 运行&&开发taps.targets (一 taps 运行说明) 说明target 需要tap 进行配合运行,所以需要了解tap 的使用 运行targe ...

  6. Java线程面试题:子线程先运行 2 次,然后主线程运行 4 次,如此反复运行 3 次

    package thread; /** * 需求:线程编程:子线程先运行 2 次,然后主线程运行 4 次,如此反复运行 3 次. * @author zhongfg * @date 2015-06-1 ...

  7. bat 判断 bat 是否是以管理员权限运行,和自动以管理员权限运行

    bat 判断 bat 是否是以管理员权限运行,和自动以管理员权限运行 判断 @echo off net.exe session 1>NUL 2>NUL && ( goto ...

  8. C#.Net集成Bartender条码打印,VS调试运行可以打印,发布到IIS运行打印报错

    C#.Net集成Bartender条码打印,VS调试运行可以打印,发布到IIS运行打印报错 问题原因: 问题出现在iis账户权限. 解决方法: iis默认是用network service这个账户去执 ...

  9. bat代码中判断 bat是否是以管理员权限运行,以及自动以管理员权限运行CMD BAT

    · bat 代码中判断bat是否是以管理员权限运行,以及自动以管理员权限运行CMD BAT 一.判断bat是否是以管理员权限运行 @echo off net.exe session >NUL & ...

随机推荐

  1. 线段覆盖4(codevs 3012)

    题目描述 Description 数轴上有n条线段,线段的两端都是整数坐标,坐标范围在0~1000000,每条线段有一个价值,请从n条线段中挑出若干条线段,使得这些线段两两不覆盖(端点可以重合)且线段 ...

  2. 多源最短路(codevs 1077)

    题目描述 Description 已知n个点(n<=100),给你n*n的方阵,a[i,j]表示从第i个点到第j个点的直接距离. 现在有Q个询问,每个询问两个正整数,a和b,让你求a到b之间的最 ...

  3. 安装及升级node

    一.mac下安装 1. 可直接在官网下载(http://nodejs.cn/),可使用命令查看版本: node -v node --version 同样npm同时也安装下来,可使用下面命令查看: np ...

  4. CodeIgniter - 数据库的增删改查

    数据库操作无非是CRUD,用非装逼的语言来说就是增删改查.也许这一节会讲的很泛泛,或者很多人看不懂,没关系,大致的看看,知道是这么回事就好,继续往后看,后面会讲实例,这些枯燥而又抽象的东西可以先跳过, ...

  5. Source Insight 多标签插件

    Source Insight不仅仅是一个强大的程序编辑器,它还能显示reference trees,class inheritance diagrams和call trees.Source Insig ...

  6. 烟大 Contest1024 - 《挑战编程》第一章:入门 Problem E: Graphical Editor(模拟控制台命令形式修改图形)

    Problem E: Graphical Editor Time Limit: 1 Sec  Memory Limit: 64 MBSubmit: 2  Solved: 2[Submit][Statu ...

  7. chromium浏览器开发系列第四篇:如何调试最新chromium源码

    转自:http://blog.itpub.net/20687969/viewspace-1586513/ 附上上几篇文章地址,方便大家查看: 下载源码 编译源码 目录结构 接二连三的事情,时间比较紧张 ...

  8. 【现代程序设计】homework-05

    本次作业要求设计服务器和客户端,由于之前对网络编程是一窍不通,上上节课听宗学长讲述Tcp的时候心里想这个东西还真是高大上啊一点儿都听不懂,但是上个周末看了看C#网络编程的博客和书之后,发现这个东西入门 ...

  9. Android系统自带样式(@android:style/) (转)

    摘自:http://blog.csdn.net/hongya1109110121/article/details/11985545 在AndroidManifest.xml文件的activity中配置 ...

  10. 循环多少次?[HDU1799]

    循环多少次? Time Limit: 3000/1000 MS (Java/Others)    Memory Limit: 65536/32768 K (Java/Others)Total Subm ...