Add parser_dc_full stf test

[ChrisDodd]

Adding a test; experimenting with cross-repo pull requests

[mihaibudiu]

When trying to repro I get this:
*** Packet different at position 76 : expected 0 , received F
*** Packet 0 on port 10 differs
How did you diagnose the problem as being in current?

[ChrisDodd]

I looked at the bmv2 output trace and determined the problem was that is
was failing to parse the first mpls header (which is what happens to be at
position 76 in the packet, so no suprise there). I then looked at the
generated .json file and looked at the parser state that should have been
parsing this (parse_mpls) and noticed that its key was "lookahead" with [0,
24](24 bits starting at offset 0) when it should be [23, 1](1 bit
starting at offset 23). Manually editing the json and then running
bmv2stf.py parser_dc_full.json parser_dc_full.stf works, so that would
appear to be the problem.

On Fri, Oct 14, 2016 at 2:28 PM, mbudiu-vmw notifications@github.com
wrote:

@mbudiu-vmw commented on this pull request.

In backends/bmv2/Makefile.am
#104 (review):

@@ -57,3 +57,7 @@ XFAIL_TESTS +=
bmv2/testdata/p4_14_samples/truncate.p4.test
bmv2/testdata/p4_16_samples/clone-bmv2.p4.test
bmv2/testdata/p4_16_samples/drop-bmv2.p4.test
+
+# backend bug handling current(23,1) in parser
+XFAIL_TESTS += bmv2/testdata/p4_14_samples/parser_dc_full.p4.test

When trying to repro I get this:
*** Packet different at position 76 : expected 0 , received F
*** Packet 0 on port 10 differs
How did you diagnose the problem as being in current?

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#104 (review), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AD4c8SoT4zBq0eQLK70dCuzImtje8vT2ks5qz_QTgaJpZM4KXURP
.