> and to let people know that simple "perftest" trigger > will stop working if the solution is merged as is.
It has been merged, around 85 minutes ago. Vratko. From: Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) Sent: Monday, 2019-February-18 17:26 To: [email protected] Cc: [email protected] Subject: more per-patch vpp performance jobs Current "perftest" job only runs on 2n-skx testbed. People were asking for a job running on other testbeds as well. So, I have prepared a solution. CSIT part: [1], ci-management part: [2]. It will take few hours for Sandbox runs to get a testbed and finish. The downside is that I have not figured out a way to keep the old "perftest" trigger in place. New triggers will be "perftest-2n-skx" (the previous perftest), "perftest-3n-skx" (useful for link bonding) and "perftest-3n-hsw" (useful for hardware crypto). The purpose of this e-mail is to ask people whether the proposed solution is okay, and to let people know that simple "perftest" trigger will stop working if the solution is merged as is. Vratko. [1] https://gerrit.fd.io/r/17655 [2] https://gerrit.fd.io/r/17620
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12313): https://lists.fd.io/g/vpp-dev/message/12313 Mute This Topic: https://lists.fd.io/mt/29900476/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
