[P4-dev] P4lang nightly packages builds

Frédéric LOUI frederic.loui at renater.fr
Thu Apr 18 05:27:32 EDT 2019


Hello,

Just to let you know that p4lang nightly builds are available from 2 distributions:

Xenial:
https://launchpad.net/~frederic-loui/+archive/ubuntu/p4lang-master-xenial-nightly <https://launchpad.net/~frederic-loui/+archive/ubuntu/p4lang-master-xenial-nightly>
Xenial builds are using PPA - p4lang-xenial.

Bionic:
https://launchpad.net/~frederic-loui/+archive/ubuntu/p4lang-master-bionic-nightly <https://launchpad.net/~frederic-loui/+archive/ubuntu/p4lang-master-bionic-nightly>
Bionic builds are using PPA - p4lang-3rd-party

The packages have « make check » step activated for all software (PI/bmv2/p4c) during the building process.

If you notice, some packages fail to build. This is because Launchpad refuse to create the corresponding .deb when "make check" fails.
You can observe the build logs here for example:  (click on the build log URL)
https://launchpad.net/~frederic-loui/+archive/ubuntu/p4lang-master-bionic-nightly/+build/16644953 <https://launchpad.net/~frederic-loui/+archive/ubuntu/p4lang-master-bionic-nightly/+build/16644953>

(Log visualisation in Launchpad is a bit tedious as the log is huge and you have to scroll down in order to find the build fail reason ... )

This is the case for:

* bmv2 only on i386 (amd64 deb is available): 
  Reported issue here: https://github.com/p4lang/behavioral-model/issues/756 <https://github.com/p4lang/behavioral-model/issues/756>
  If it make sense I can disable i386 arch build during building process and let only amd64 arch.

* p4c
  - xenial: 
99% tests passed, 2 tests failed out of 1303

Label Time Summary:
XFAIL        =  30.83 sec (25 tests)
bmv2         = 947.65 sec (374 tests)
cpplint      =  21.62 sec (1 test)
ebpf         =  12.80 sec (14 tests)
ebpf-bcc     =   2.87 sec (14 tests)
err          =  14.08 sec (166 tests)
gtest        =   2.91 sec (1 test)
p14_to_16    = 217.80 sec (205 tests)
p4           = 221.57 sec (528 tests)

Total Test time (real) = 1441.84 sec

The following tests FAILED:
	371 - bmv2/testdata/p4_16_samples/psa-multicast-basic-bmv2.p4 (Failed)
	372 - bmv2/testdata/p4_16_samples/psa-unicast-or-drop-bmv2.p4 (Failed)
Errors while running CTest

  - bionic:
99% tests passed, 3 tests failed out of 1303

Label Time Summary:
XFAIL        =  32.82 sec*proc (25 tests)
bmv2         = 995.22 sec*proc (374 tests)
cpplint      =  22.24 sec*proc (1 test)
ebpf         =  15.71 sec*proc (14 tests)
ebpf-bcc     =   4.66 sec*proc (14 tests)
err          =  15.63 sec*proc (166 tests)
gtest        =   2.88 sec*proc (1 test)
p14_to_16    = 206.37 sec*proc (205 tests)
p4           = 223.04 sec*proc (528 tests)

Total Test time (real) = 1486.32 sec

The following tests FAILED:
	373 - bmv2/testdata/p4_16_samples/psa-multicast-basic-bmv2.p4 (Failed)
	375 - bmv2/testdata/p4_16_samples/psa-unicast-or-drop-bmv2.p4 (Failed)
	1301 - p14_to_16/testdata/p4_14_errors/nasty_meta.p4 (Failed)
Errors while running CTest

p4c code is getting several recent commits on Github so the number of failing tests can be different day to day.
One difference to note though between Xenial and Bionic is the nasty_meta.p4 that is failing only on Bionic from the same code base.

Finally, If you need p4c installation you can still compile and install it manually.

We will use these builds to stage the environment in our project and also use them as material for potential training within our academic community.

All feedback is welcome.

Happy p4.

À bientôt,
--  Frederic




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p4.org/pipermail/p4-dev_lists.p4.org/attachments/20190418/fb7de340/attachment.html>


More information about the P4-dev mailing list