Browse Source

Some small slides fixes

Signed-off-by: Florent Jacquet <florent.jacquet@free-electrons.com>
master
Skia 2 years ago
parent
commit
a721b5bbba
2 changed files with 12 additions and 9 deletions
  1. BIN
      slides.pdf
  2. +12
    -9
      slides.tex

BIN
slides.pdf View File


+ 12
- 9
slides.tex View File

@@ -6,10 +6,11 @@
\usepackage[utf8]{ inputenc }
\usepackage{ lmodern }
\usepackage{ color }
\usepackage{ graphicx }
\usepackage{graphicx}
\graphicspath{ {./pix/} }

\usepackage{ drawstack }
\usepackage{soul}

\usetheme{metropolis}

@@ -64,7 +65,7 @@
\item Used to make only rootfs.
\item Is configured to provided the needed tools such as iperf,
bonnie++, etc...
\item Builds fresh rootfs every night for all the needed architectures:
\item Builds fresh rootfs \st{every night} for all the needed architectures:
ARMv4, ARMv5, ARMv7, ARMv8.
\item Stores them in a LAVA-accessible folder in the farm.
\item Small overlay over vanilla buildroot:
@@ -84,7 +85,7 @@
\item Has job templates and knows how to send them.
\item Has a list of devices in the \verb$boards.py$ file containing the
non-changing data
\item Can fetch latest builds URLs from KernelCI.
\item Can fetch latest builds URLs from KernelCI through its API.
\item Can upload custom artifacts useable for tests.
\item Can ask LAVA to notify given emails addresses when the job ends.
\item Needs an access to the LAVA API, an SSH access to the LAVA server
@@ -101,6 +102,8 @@
\item Also needs YAML files to interface with LAVA. \\
This file basically describes a list of commands to be run, and
usually, it only calls the script.
\item In practice, generic YAML files were made for the test suite, but
there may be a need for specific ones in the futur.
\end{itemize}
\begin{scriptsize}
Example:
@@ -130,7 +133,7 @@ run:
\begin{itemize}
\item A cron job runs at 23:23 to:
\begin{itemize}
\item Build fresh rootfs.
\item \st{Build fresh rootfs.}
\item Launch custom tests on every boards with there
default configuration.
\end{itemize}
@@ -144,22 +147,22 @@ run:
\begin{frame}[fragile]{Workflow (2)}
On demand jobs:
\begin{itemize}
\item \verb$./ctt.py -b all --send$ \\
\item \verb$./ctt.py -b all$ \\
\small{sends jobs to all boards with their default tests (it's what
the daily cron job does)}
\item \verb$./ctt.py -b beaglebone-black -m network --send$ \\
\item \verb$./ctt.py -b beaglebone-black -m network$ \\
\small{sends only the network test using the multinode job
template (\alert{-m}) to the beaglebone black}
\item \verb$./ctt.py -b armada-7040-db armada-8040-db $ \\
\verb$-t first_test --kernelci-tree next$ \\
\small{stores the jobs (no \alert{$--$send}) for the 7040 and 8040
\verb$-t first_test --kernelci-tree next --no-send$ \\
\small{stores the jobs (\alert{$--$no-send}) for the 7040 and 8040
devices, to run only the \alert{first\_test} test on the latest
KernelCI build of the next tree}

\end{itemize}
\end{frame}

\section{How do tests works?}
\section{How do tests work?}

\begin{frame}[fragile]{LAVA v2 jobs}
\begin{itemize}

Loading…
Cancel
Save