Hi JamO, We are working on fixing this failures at the moment. Most of the failures are due to a 404 error returned when a delete is executed on a nonexistent resource. They are under control and a fix will be submitted shortly today. There are also some minor exceptional cases where we see a 404 when a put operation is executed (failing intermittent and in just a few test cases). This is also under investigation.
Best Regards, Miguel Ángel. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jamo Luhrsen Sent: miércoles, 31 de agosto de 2016 7:07 To: [email protected] Cc: An Ho <[email protected]>; Colin Dixon <[email protected]>; [email protected] Subject: [integration-dev] SFC CSIT analysis for release Boron review (8/31) For the SFC release review Wednesday morning, I have the following analysis of their upstream CSIT for boron, using the most recent boron job result. please note that I do not know if all delivered features have system test or not, so only reporting on what exists. NOT-OK sfc-csit-3node-docker-full-deploy-all-boron (unexpected failures) NOT-OK sfc-csit-3node-rest-basic-all-boron (unexpected failures) NOT-OK sfc-csit-3node-rest-basic-only-boron (unexpected failures) OK sfc-csit-3node-clustering-all-boron OK sfc-csit-3node-clustering-only-boron With these results, I think probably all SFC features should be labeled as experimental. The two clustering jobs are always passing, but the functionality covered there is more of a config store test across a cluster. Thanks, JamO _______________________________________________ integration-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/integration-dev _______________________________________________ sfc-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/sfc-dev
