15:00:15 #startmeeting CSIT weekly 2019-12-04 15:00:15 Meeting started Wed Dec 4 15:00:15 2019 UTC. The chair is vrpolak. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:15 The meeting name has been set to 'csit_weekly_2019_12_04' 15:01:02 #info Peter Mikus 15:02:00 #info Vratko Polak 15:02:13 #topic Agenda Bashing 15:02:24 #info Juraj Linkeš 15:03:12 #info Tibor Frank 15:06:25 #topic Physical labs, testbeds 15:08:25 #info Arm build server (1/3) power cycled, hard drive failure on one s5ci node, otherwise looks good. 15:08:45 #info Outage notice for Jenkins.plugins update. 15:10:56 #info Dave Wallace 15:11:03 #info Arm docker images need to be updated for Python 3 to work correctly, pull requests: 1 ready, 1 in progress. 15:14:13 #topic operations 15:15:07 #info There was a breakage after Python3 migration, due to "ply" package not available on virtualenv (even when installed on system). Fixed quicly, but root cause still under investigation. 15:15:55 #topic Inputs from projects 15:16:08 #info No news from VPP, TSC. 15:21:50 #topic Developments 15:22:50 #info Testbeds: Will need a way to limit jobs with Mellanox tests to run on testbeds that have them (one testbed does not yet). We will work on it after other Mellanox related changes are merged. 15:25:00 #info Performance trending and analytics: New graph organization is merged, results will be visible soon. 15:29:59 #info API functional test coverage: Next patches submitted, still under review. 15:35:07 #info Question about bidirectional traffic. Answer: use the same type as in the preformance test. If functional test fail, we can identify a Bug and fix it. 15:39:57 #info Gcov coverage: More a metric for VPP, but if they want we can create a weekly job for that. 15:43:08 #info Improvements to test teardown: Use gdb "script" to process and print information useful to developers. 15:49:02 #topic TRex 15:50:36 #info Vratko thinks there is a bug in TRex that occasionally increases the time Trex takes to send all the packets, effectively leading to MRR resylts bigger than the real performance. But Vratko also has trouble to gather enough data to compare two TRex versions, so the question is still open. 15:56:21 #info Question about triggering a specific performance test. The full answer will be on csit-dev mailing list. 15:56:58 #endmeeting