Browse Source

Add appendix and make some reworks

Signed-off-by: Skia <skia@libskia.so>
master
Skia 2 years ago
parent
commit
c9312e9318
7 changed files with 89 additions and 16 deletions
  1. 4
    1
      Makefile
  2. BIN
      report.pdf
  3. 9
    0
      report.tex
  4. 51
    0
      tex/appendix.tex
  5. 13
    4
      tex/biblio.tex
  6. 8
    6
      tex/ci_tests.tex
  7. 4
    5
      tex/toolchains.tex

+ 4
- 1
Makefile View File

@@ -19,4 +19,7 @@ all: $(PICTURES) $(COVER)
dia -e $@ -t eps $^

clean:
$(RM) *.pdf *.pyg *.snm *.toc *.vrb *.aux *.nav *.out *.dia~ *.log *.lof cover/*.pdf tex/*.aux tex/*.out tex/*.log tex/*.lof
$(RM) *.pyg *.snm *.toc *.vrb *.aux *.nav *.out *.dia~ *.log *.lof cover/*.pdf tex/*.aux tex/*.out tex/*.log tex/*.lof

mrproper: clean
$(RM) *.pdf

BIN
report.pdf View File


+ 9
- 0
report.tex View File

@@ -44,6 +44,15 @@

\include{tex/biblio}

\appendix
\addtolength{\textheight}{65mm}
\part*{Appendix}
\addtolength{\topmargin}{-52mm}
\definecolor{gray75}{gray}{0.75}
\newcommand{\hsp}{\hspace{20pt}}

\include{tex/appendix}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%% BOTTOM: Derniere de couverture
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

+ 51
- 0
tex/appendix.tex View File

@@ -0,0 +1,51 @@
\chapter{List of contributions to LAVA}
\label{cha:list_of_contributions_to_lava}



\section{lava-dispatcher}
\label{sec:lava_dispatcher}

\begin{verbatim}
$ git log --author "Florent Jacquet"

3a890271c465 device-types: fix at91sam9x25ek to use bootz
b2aef8b34d77 device-types: add sun6i-a31-app4-evb1
b495a3548d5f device-types: add ttyAT0 to Atmel devices to support multiv7_defconfig
3bfdcdb672f1 Add support for use_xip
8df17dd7355c Add support for append_dtb
a8fb0d9d7d25 device-types: add Armada 8040 DB board
171e8b653153 device-types: add Allwinner A23 EVB board
5898747b44d4 device-types: add OrangePi PC board
\end{verbatim}

\section{lava-server}
\label{sec:lava_server}

\begin{verbatim}
$ git log --author "Florent Jacquet"

716424a36fd8 api: fix scheduler.jobs.submit's docstring
ad2f57df757d device-type: update at91-sama5d4_xplained addresses
b6734844e48d device-type: update at91-sama5d2_xplained addresses
c4ead793de9b device-type: update sama53d addresses
092f56a56170 device-type: update armada-xp-linksys-mamba addresses
0fdf33a833d6 device-type: update armada-388-gp addresses
5af8f640c693 device-type: update armada-370-db addresses
0b3b0beb7625 device-type: addresses fix for armada-3720-espressobin
ed1e402e585f device-type: addresses fix for armada-3720-db
c382a5aa04bf device-type: fix at91sam9m10g45ek
2c840debc665 base-uboot.jinja2: don't load DTB if append_dtb is set
bbc39489c740 results_app: API: add the 'run_query' function
8746edb6be8c results_app: API: add the 'make_custom_query' function
a04086dd7d58 api: add get_recent_jobs_for_device
c9b9453d1733 Migrate many U-boot devices to v2 configuration
da87efaa6953 base-uboot.jinja2: add support for append_dtb and use_xip
11725bc3eadc doc: fix a small gap about test suites
cc9e4ea2c463 Allow to override U-boot bootcmd command
babaef51dc46 lava_scheduler_app: api: Add pipeline information to get_device_status
187c8520aba2 Allow to override U-boot tftp command
84f88a4fca4f Allow to override U-boot usb command
4211de051b2d Don't force {BOOTX} macro in U-boot template
571d71313eda Don't force dhcp in U-boot template
\end{verbatim}

+ 13
- 4
tex/biblio.tex View File

@@ -1,8 +1,17 @@
\chapter*{Bibliography}

\begin{itemize}
\item Documentation of \textbf{LAVA},\\
\url{https://validation.linaro.org/static/docs/}
\item \textit{\#linaro-lava} chan on \url{irc://irc.freenode.net},
\item \textit{\#kernelci} chan on \url{irc://irc.freenode.net},
\item Documentation of \textbf{LAVA},\\
\url{https://validation.linaro.org/static/docs/}
\item Source code of \textbf{LAVA}: \\
\url{http://git.linaro.org/lava/lava-dispatcher.git/}\\
\url{http://git.linaro.org/lava/lava-server.git/}
\item \textit{\#linaro-lava} chan on \url{irc://irc.freenode.net},
\item \textit{\#kernelci} chan on \url{irc://irc.freenode.net},
\item Buildroot website and documentation: \\
\url{https://buildroot.org/} \\
\url{https://buildroot.org/downloads/manual/manual.html}
\item Gitlab.com and its documentation: \\
\url{https://docs.gitlab.com/ce/README.html} \\
\url{https://docs.gitlab.com/ce/ci/}
\end{itemize}

+ 8
- 6
tex/ci_tests.tex View File

@@ -268,7 +268,9 @@ improved\footnote{See these patches for example: \\
\url{https://git.linaro.org/lava/lava-dispatcher.git/commit/?id=3bfdcdb672f1a15da96bbb221a26847dd6bf2865} \\
Also don't hesitate to run \verb$git log --author "Florent Jacquet"$ in the
\verb$lava-dispatcher$ and the \verb$lava-server$ projects to get an overview of
the contributions made to \textbf{LAVA}.
the contributions made to \textbf{LAVA} (Also available in appendix
\ref{cha:list_of_contributions_to_lava}, page
\pageref{cha:list_of_contributions_to_lava}).
}.

\subsubsection{Using custom artifacts}
@@ -388,7 +390,7 @@ such as some network-related jobs. Since the boards need to interact, they need
to be synchronized, and \textbf{LAVA} provides some tools in the runtime
environment to allow data exchanges between the devices, but as with classic
threads or processes, this can quickly lead to some race conditions, deadlocks,
or other fancy concurrency problematics.
or other interesting concurrency problematics.

Once all those problems addressed, with the network tests running, a little
presentation to the team was given, so that everyone would know the status
@@ -460,10 +462,10 @@ tool, so that it would be easier in the future to add new features. The
technical debt brought by the proof-of-concept design pattern would also be
paid.

One of the engineers had already taken time to rework small parts, but keeping
them working with the rest of the scripts without breaking the internal API.
More was needed, but still, he had quite a good vision of the tool's design, and
greatly helped in its refactoring.
One of the engineers had already taken time to rework small parts, but was
keeping the internal API untouched when some functions or classes necessitated
to be split in multiple ones. More was needed, but still, he had quite a good
vision of the tool's design, and greatly helped in its refactoring.

This brought along the way many interesting side-effects: unit tests to almost
all the newly created classes, flexible and modular design, simpler

+ 4
- 5
tex/toolchains.tex View File

@@ -299,7 +299,7 @@ sending thankful messages by various means.
Among the messages, some questions were raised, which led to the creation of an
FAQ page on the website, aggregating the most common ones.

With the coming of the next \textbf{Buildroot} version, including, among others
With the coming of the next \textbf{Buildroot} release, including, among others
improvements, a more recent GCC, a new release was prepared. But with the
growing number of available toolchains, a new page had to be made, as a
per-architecture summary, presenting all the possible versions, even the old and
@@ -310,10 +310,9 @@ or was released in the toolchains set.
\label{sec:final_words}

Despite not being related to the first subject of the internship, it had many
common points, especially in the use of the Continuous Integration. This allowed
me to discover a large amount of uncommon architectures, and to better
understand how toolchains work from the inside, which I did not expect at all at
first glance.
common points with it, especially in the use of the Continuous Integration.
Furthermore, this allowed me to discover a large amount of uncommon
architectures, and to better understand how toolchains work from the inside.

In the meantime, this also was a nice contribution to the open-source world,
since it is a service that did not exist six months ago, and which is now more

Loading…
Cancel
Save