This run in sandbox will finish before: https://jenkins.opendaylight.org/sandbox/job/openflowplugin-csit-1node-config-performance-only-carbon/1/ <https://jenkins.opendaylight.org/sandbox/job/openflowplugin-csit-1node-config-performance-only-carbon/1/>
> On Nov 21, 2016, at 9:22 AM, Jamo Luhrsen <[email protected]> wrote: > > > > On 11/21/2016 09:08 AM, Robert Varga wrote: >> On 11/21/2016 06:06 PM, Luis Gomez wrote: >>> >>> Thanks for the quick turnaround, it seems it is fixed now: >>> >>> https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-config-performance-only-boron/plot/Flow%20Config%20Performance/ >>> <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-config-performance-only-boron/plot/Flow >>> Config Performance/> >> >> Is there a way to trigger that against a patch? >> (https://git.opendaylight.org/gerrit/48532 in this case). > > Yeah, I took the distro built in your patch's distro-check [0] and triggered > that flog config perf job [1]. Let's see... > > JamO > > [0] > https://jenkins.opendaylight.org/releng/job/yangtools-distribution-check-carbon/620/artifact/distribution-karaf-0.6.0-SNAPSHOT.zip > [1] > https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-config-performance-only-boron/829/ > >> >> Thanks, >> Robert >> >> >> >> _______________________________________________ >> openflowplugin-dev mailing list >> [email protected] >> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev >>
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
