Commit c053133a authored by Neil Williams's avatar Neil Williams 💬

Merge branch 'staging' into release

parents 4063e2af f60a5328
......@@ -27,7 +27,7 @@ recursive-include doc/images *.gif *.png *.jpg *.jpeg *.bmp *.svg *.odg
recursive-include doc/v2/images *.gif *.png *.jpg *.jpeg *.bmp *.svg *.odg
recursive-include doc/v2/examples *.yaml *.txt *.py
recursive-include doc/v2/_templates *.html
include instance.template
include etc/instance.conf.template
include doc/*
include doc/deprecated/*
include doc/v2/*
......
......@@ -4,7 +4,7 @@ set -x
set -e
PEP8=1
ALL=0
ALL=1
while getopts ":pa" opt; do
case $opt in
......@@ -13,13 +13,13 @@ while getopts ":pa" opt; do
PEP8=2
;;
a)
# python3 and python2
# python3 - python2 support dropped
ALL=1
;;
\?)
echo "Usage:"
echo "-p - pep8 only"
echo "-a - run all tests: pep8, python2 and python3"
echo "-a - run all tests: pep8 and python3"
echo "Invalid option: -$OPTARG" >&2
exit 1
;;
......@@ -51,15 +51,6 @@ if [[ (-z "$1") || (("$1" == -v*) && ($# -eq 1)) ]]; then
VERBOSE=$1
fi
if [ -n "$NOINPUT" ] || [ -n "$VERBOSE" ]; then
./lava_server/manage.py test $NOINPUT $VERBOSE \
lava_scheduler_app \
linaro_django_xmlrpc.tests \
lava_results_app
else
./lava_server/manage.py test "$@"
fi
if [ ${ALL} = 1 ]; then
if [ -n "$NOINPUT" ] || [ -n "$VERBOSE" ]; then
python3 ./lava_server/manage.py test $NOINPUT $VERBOSE \
......
......@@ -111,7 +111,7 @@ class Migration(migrations.Migration):
name='ImageChartFilter',
fields=[
('id', models.AutoField(verbose_name='ID', serialize=False, auto_created=True, primary_key=True)),
('representation', models.CharField(default='lines', max_length=20, verbose_name='Representation', choices=[(b'lines', 'Lines'), (b'bars', 'Bars')])),
('representation', models.CharField(default='lines', max_length=20, verbose_name='Representation', choices=[('lines', 'Lines'), ('bars', 'Bars')])),
],
options={
},
......@@ -216,7 +216,7 @@ class Migration(migrations.Migration):
('id', models.AutoField(verbose_name='ID', serialize=False, auto_created=True, primary_key=True)),
('name', models.CharField(max_length=100)),
('description', models.TextField(null=True, blank=True)),
('chart_type', models.CharField(default='pass/fail', max_length=20, verbose_name='Chart type', choices=[(b'pass/fail', 'Pass/Fail'), (b'measurement', 'Measurement')])),
('chart_type', models.CharField(default='pass/fail', max_length=20, verbose_name='Chart type', choices=[('pass/fail', 'Pass/Fail'), ('measurement', 'Measurement')])),
('target_goal', models.DecimalField(null=True, verbose_name='Target goal', max_digits=10, decimal_places=5, blank=True)),
('is_interactive', models.BooleanField(default=False, verbose_name='Interactive')),
('is_data_table_visible', models.BooleanField(default=False, verbose_name='Data table visible')),
......@@ -350,7 +350,7 @@ class Migration(migrations.Migration):
('version', models.CharField(help_text='Maximum length: 256 characters', max_length=256, verbose_name='Version')),
('description', models.TextField(verbose_name='Description')),
('format', models.CharField(help_text='Maximum length: 128 characters', max_length=128, verbose_name='Format')),
('location', models.CharField(default='LOCAL', max_length=64, verbose_name='Location', choices=[(b'LOCAL', 'Local'), (b'URL', 'URL'), (b'GIT', 'GIT Repo'), (b'BZR', 'BZR Repo')])),
('location', models.CharField(default='LOCAL', max_length=64, verbose_name='Location', choices=[('LOCAL', 'Local'), ('URL', 'URL'), ('GIT', 'GIT Repo'), ('BZR', 'BZR Repo')])),
('url', models.CharField(help_text='Maximum length: 1024 characters', max_length=1024, verbose_name='URL')),
('environment', models.CharField(help_text='Maximum length: 256 characters', max_length=256, verbose_name='Environment')),
('target_os', models.CharField(help_text='Maximum length: 512 characters', max_length=512, verbose_name='Operating Systems')),
......
......@@ -541,7 +541,7 @@ context may be ignored.
The version of ``qemu`` installed on the dispatcher is a choice made by the
admin. Generally, this will be the same as the version of ``qemu`` available
from Debian in the same suite as the rest of the packages installed on the
dispatcher, e.g. ``jessie``. Information on the available versions of ``qemu``
dispatcher, e.g. ``stretch``. Information on the available versions of ``qemu``
in Debian is available at http://tracker.debian.org/qemu
.. seealso:: :ref:`essential_components` and :ref:`qemu-iso boot method
......@@ -580,7 +580,7 @@ option in the job context may be ignored.
The version of ``qemu`` installed on the dispatcher is a choice made by the
admin. Generally, this will be the same as the version of ``qemu`` available
from Debian in the same suite as the rest of the packages installed on the
dispatcher, e.g. ``jessie``. Information on the available versions of ``qemu``
dispatcher, e.g. ``stretch``. Information on the available versions of ``qemu``
in Debian is available at http://tracker.debian.org/qemu
QEMU can be used with an NFS using the ``qemu-nfs`` method and the ``nfs``
......@@ -628,7 +628,7 @@ modification using the :term:`job context`.
The version of ``qemu`` installed on the dispatcher is a choice made by the
admin. Generally, this will be the same as the version of ``qemu`` available
from Debian in the same suite as the rest of the packages installed on the
dispatcher, e.g. ``jessie``. Information on the available versions of ``qemu``
dispatcher, e.g. ``stretch``. Information on the available versions of ``qemu``
in Debian is available at http://tracker.debian.org/qemu
.. seealso:: :ref:`essential_components` and :ref:`boot method qemu
......
......@@ -344,7 +344,7 @@ colon. In the YAML, all values containing a colon **must** be quoted:
.. code-block:: yaml
persistent_nfs:
address: "127.0.0.1:/var/lib/lava/dispatcher/tmp/armhf/jessie"
address: "127.0.0.1:/var/lib/lava/dispatcher/tmp/armhf/stretch"
.. index:: deploy to tmpfs
......@@ -357,7 +357,7 @@ Used to support QEMU device types which run on a dispatcher. The file is
downloaded to a temporary directory and made available as one or more images,
appending specified arguments to a predetermined QEMU command line:
.. include:: examples/test-jobs/qemu-amd64-standard-jessie.yaml
.. include:: examples/test-jobs/qemu-amd64-standard-stretch.yaml
:code: yaml
:start-after: actions:
:end-before: # BOOT_BLOCK
......@@ -389,7 +389,7 @@ QEMU would include ``-drive format=raw,file=/tmp/tmp.rG542e/large-stable-6.img``
.. note:: Take note of the syntax. Single brace before and after the label and
**no whitespace**. This is test job syntax, not Jinja.
.. include:: examples/test-jobs/qemu-amd64-standard-jessie.yaml
.. include:: examples/test-jobs/qemu-amd64-standard-stretch.yaml
:code: yaml
:start-after: to: tmpfs
:end-before: url:
......@@ -475,7 +475,7 @@ potential problems such as misconfigured caching or corrupted downloads. If
compression is used, the checksum to specify is the checksum of the compressed
file, irrespective of whether that file is decompressed later.:
.. include:: examples/test-jobs/qemu-amd64-standard-jessie.yaml
.. include:: examples/test-jobs/qemu-amd64-standard-stretch.yaml
:code: yaml
:start-after: rootfs:
:end-before: os: debian
......
......@@ -224,6 +224,42 @@ container.
.. note:: To apply configurations system wide for all LXC devices attached to
the dispatcher use ``/etc/lxc/default.conf`` file.
.. index:: lxc on arm64 stretch
.. _lxc_arch_distro:
Architecture and distribution issues
************************************
If you are configuring a LAVA instance with a range of dispatchers, there can
be issues if those dispatchers are both ``amd64`` and ``arm64`` architectures.
On Debian Stretch, the ``lxc`` package does not support mapping the kernel
architecture name (``aarch64``) to the Debian release architecture name
(``arm64``). This mapping has been added to newer versions of LXC.
::
$ sudo lxc-create -t debian -n server-unittests -- --release stretch -a arm64
Once the cache exists, test jobs do not need to specify the arch again:
::
$ sudo lxc-create -t debian -n server-unittests -- --release stretch
However, the cache will invalidate from time to time, so this is an
administrative burden.
To avoid this burden, admins can choose to have two LXC device-types defined
with slightly different health checks and test jobs to specify the
architecture.
.. seealso:: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895432
If all dispatchers on a master are ``arm64``, simply change the ``lxc.jinja2``
template to specify the architecture for all test jobs as ``arm64``.
Other resources
***************
......
......@@ -86,7 +86,7 @@ First steps using LAVA
explain_first_job
lava-tool
standard-test-jobs
standard-qemu-jessie
standard-qemu-stretch
standard-qemu-kernel
standard-armmp-ramdisk-bbb
......
......@@ -14,8 +14,9 @@ Packages for LAVA are available for:
* Debian Sid (unstable)
Packages will remain available for Debian Jessie (oldstable) with backports
until June 2018 as security support for Jessie will end. Developers are
recommended to use Debian Stretch or Buster for development.
until June 2018 as security support for Jessie will end. The last production
release with Jessie support was 2018.2. Developers need to use Debian Stretch
or Buster for development.
When using the packages to develop LAVA, there is a change to the workflow
compared to the old lava-deployment-tool buildouts.
......@@ -65,13 +66,10 @@ Developer package build
.. seealso:: :ref:`developer_preparations` and
:ref:`development_pre_requisites`
.. note:: The recommended suite for LAVA development is now Stretch. The
developer package build now defaults to expecting Stretch and therefore
enables Python2 and Python3 support. If you are building on Jessie, use the
``-b backports`` branch option to only build for Python2. When support for
Python2 is removed, the ``master`` branch will change to only building
Python3 and building on Jessie will be disabled. To install lava-server,
lava-dispatcher must also be built and installed with Python3 support. See
.. note:: The supported suite for LAVA development is now Stretch. The
developer package build now defaults to expecting Stretch and therefore uses
Python3 exclusively. Support for building Python2 has been removed, the
``master`` branch only builds Python3. See
https://lists.linaro.org/pipermail/lava-announce/2018-January/000046.html
The ``lava-dev`` package includes a helper script which is also present in the
......@@ -86,12 +84,6 @@ from the directory containing the code for that package::
$ /usr/share/lava-server/debian-dev-build.sh -p lava-server
If you are building a package to be installed on Jessie, ensure that the
``backports`` packaging branch is used so that the packaging scripts can allow
for differences between unstable and jessie::
$ /usr/share/lava-server/debian-dev-build.sh -p lava-server -b backports
The packages will be built in a temporary directory using a version string
based on the current git tag and the time of the build. The helper outputs the
location of all the built packages at the end of a successful build, ready for
......@@ -104,9 +96,7 @@ use with ``$ sudo dpkg -i``.
To install any package, including the developer build packages, the
corresponding package **must** already be installed at the current production
release version (or better), on the same machine. This ensures that all of the
runtime dependencies already exist on the system. (If you are building for
installation on Jessie, you will need a fully installed Jessie VM to test the
packages built for Jessie.)
runtime dependencies already exist on the system.
.. _devel_branches:
......@@ -165,17 +155,6 @@ the short hash can be used to lookup the commit in the master branch, e.g.::
Distribution differences
========================
LAVA uses a date-based release scheme and PEP440_ imposes constraints on how
local versions can be named and still work reliably with python-setuptools_,
yet these constraints differ between jessie and unstable::
jessie: lava-server-2015.12-5451.f9304da
unstable: lava-server-2015.12+5451.f9304da
There are also changes internally in the *egg* information used by setuptools
when built on jessie and when built on unstable. Binary packages built on
unstable will fail to install on jessie.
**Always** build packages on the suite you expect to use for installation.
Packages available from the :ref:`lava_repositories` are built on
......@@ -235,40 +214,15 @@ number, in accordance with PEP440, so the git tag will be ``2015.8`` instead of
Development using Python3
*************************
LAVA has been moving towards Python3 support as an integral part of the
migration to V2 and with the completion of the migration and the removal of the
V1 codebase, `the announcement has been made
<https://lists.linaro.org/pipermail/lava-announce/2017-June/000032.html>`_ that
all LAVA packages will move exclusively to Python3 support.
Both lava-server and lava-dispatcher optionally support running the unit tests
with Python3 using the ``-a`` option to ``./ci-run``.
In due course, the internal CI within LAVA (called ``lavabot``) will support
running the Python3 unit tests for lava-server as well as lava-dispatcher. At
this point, **all** reviews **must** pass the unit tests when run with Python3.
LAVA has moved to exclusive Python3 support as the final stage of the
migration to V2. See
<https://lists.linaro.org/pipermail/lava-announce/2017-June/000032.html>`_
Once builds for Debian Jessie cease, support for Python2 will be dropped and
**only** Python3 will be supported.
Both lava-server and lava-dispatcher only support running the unit tests with
Python3. **All** reviews **must** pass the unit tests when run with Python3.
The 2018.2 release of LAVA will enable both Python2 and Python3, so that
installations will bring in both sets of dependencies to allow both sets of
unit tests to be run. At runtime, LAVA will still use Python2 for the 2018.1
release but will switch over when support for Jessie ceases.
In the meantime, the :ref:`dev_builds` can support Python3 by using the ``-b``
option to specify the ``python3`` branch::
$ /usr/share/lava-server/debian-dev-build.sh -p lava-server -b python3
$ /usr/share/lava-server/debian-dev-build.sh -p lava-dispatcher -b python3
.. note:: The first time you install a package built using the ``python3``
branch, you are likely to see dependency failures which block the install.
Check the information about the newly built packages and ensure that the
relevant dependencies are installed. In particular,
``python3-django-auth-ldap`` will need to be installed from
``stretch-backports``.
Builds for Debian Jessie have ceased, support for Python2 has been dropped and
**only** Python3 is be supported.
Python3 dependencies include:
......@@ -538,10 +492,6 @@ branch and passing the ``-b`` option to :file:`debian-dev-build-sh`::
$ /usr/share/lava-server/debian-dev-build.sh -p lava-server -b docs
or for installation on jessie::
$ /usr/share/lava-server/debian-dev-build.sh -p lava-server -b backports
.. _architecture_builds:
Building for other architectures
......
......@@ -126,7 +126,7 @@ be configured. This test can be run directly from a git checkout of
.. code-block:: shell
$ python -m unittest -vcf lava_scheduler_app.tests.test_templates.TestTemplates.test_all_templates
$ python3 -m unittest -vcf lava_scheduler_app.tests.test_templates.TestTemplates.test_all_templates
Individual templates have their own unit tests to test for specific elements of
the rendered device configuration.
......
......@@ -96,10 +96,8 @@ Static code analysis
====================
It is essential to run ``pep8 --ignore E501`` routinely on your local
changes as ``./ci-run`` will fail on any PEP8 errors.
.. note:: There can be differences in behaviour between ``pep8`` in Jessie
and in Stretch or unstable. All reviews are tested using Jessie.
changes as ``./ci-run`` will fail on any PEP8 errors. All automated tests
occur using Debian Stretch.
It is important to run tools like :ref:`pylint <pylint_tool>`, particularly
when adding new files, to check for missing or unused imports. Other analysis
......@@ -700,7 +698,7 @@ Python3 support in LAVA is related to a number of factors:
* Forthcoming LTS releases of django which will remove support for python2.7
* Deprecating Debian Jessie and moving development support to Stretch.
* Debian Jessie is now unsupported and development has moved to Stretch.
* Transition within Debian to full python3 support.
......@@ -712,10 +710,8 @@ lava-dispatcher and lava-server now support python3 testing. Code changes to
either codebase **must** be Python3 compatible to not break the unit tests when
run using python3.
LAVA is not yet ready to use python 3.x support at runtime.
All reviews run the ``lava-dispatcher`` and ``lava-server`` unit tests against
python 3.x and changes must pass without breaking compatibility with python 2.x
python 3.x and changes must pass all unit tests.
The ``./ci-run`` script for ``lava-dispatcher`` and ``lava-server`` can run
the unit tests using Python3::
......@@ -723,8 +719,8 @@ the unit tests using Python3::
./ci-run -a
Some additional Python3 dependencies will be required. In particular,
``python3-django-auth-ldap`` will need to be installed from
``stretch-backports``.
``python3-django-auth-ldap`` and ``python3-django-testscenarios`` will need to
be installed from ``stretch-backports``.
.. warning:: Django wil be dropping python2.7 support with the 2.2LTS release,
*frozen* instances of LAVA will not be able to use django updates after that
......
......@@ -538,7 +538,7 @@ your new device type. For example, a new unit test function defined as
.. code-block:: shell
$ python -m unittest -vcf lava_scheduler_app.tests.test_templates.TestTemplates.test_foobar_template
$ python3 -m unittest -vcf lava_scheduler_app.tests.test_templates.TestTemplates.test_foobar_template
Remember that device type templates are not just configuration files - the
templates are processed as source code at runtime and can use various types of
......
......@@ -88,14 +88,14 @@ lava-dispatcher
::
$ python -m unittest discover lava_dispatcher/
$ python3 -m unittest discover lava_dispatcher/
To run a single test, use the test class name as output by a failing test,
without the call to ``discover``::
$ python -m unittest lava_dispatcher.test.test_basic.TestPipelineInit.test_pipeline_init
$ python3 -m unittest lava_dispatcher.test.test_basic.TestPipelineInit.test_pipeline_init
$ python -m unittest -v -c -f lava_dispatcher.test.test_basic.TestPipelineInit.test_pipeline_init
$ python3 -m unittest -v -c -f lava_dispatcher.test.test_basic.TestPipelineInit.test_pipeline_init
The call references the path to the python module, the class and then the test
function within that class. To run all tests in a class, omit the function. To
......@@ -106,10 +106,11 @@ of ``lava-dispatcher`` as well::
$ ./ci-run --test-suite lava_dispatcher.test.test_basic.TestPipelineInit.test_pipeline_init
Also, install the updated ``lava-dispatcher`` package and use it to inspect the
output of the pipeline using the ``--validate`` switch to ``lava-dispatch``::
Also, install the updated ``lava-dispatcher`` package and use it to write out
the pipeline to a ``description.yaml`` file in the specified output directory
using the ``--validate`` switch to ``lava-run``::
$ sudo lava-dispatch --validate --target ./devices/kvm01.yaml ./sample_jobs/kvm.yaml --output-dir=/tmp/test
$ sudo lava-run --validate --target ./devices/kvm01.yaml ./sample_jobs/kvm.yaml --output-dir=/tmp/test --job-id=6
.. note:: The refactoring has changed the behaviour of ``target`` - the value
**must** be a path to a YAML file, not a hostname. This is because the
......@@ -845,7 +846,7 @@ statements in the device configuration or job submission show up inside the
classes is to use a unit test. To run a single unit-test, for example
test_function in a class called TestExtra in a file called test_extra.py, use::
$ python -m unittest -v -c -f lava_dispatcher.test.test_extra.TestExtra.test_function
$ python3 -m unittest -v -c -f lava_dispatcher.test.test_extra.TestExtra.test_function
Example python code:
......
# Standard Jessie amd64 JOB definition for QEMU
# Standard Stretch amd64 JOB definition for QEMU
device_type: qemu
job_name: qemu amd64 standard build, Debian Jessie
job_name: qemu amd64 standard build, Debian Stretch
timeouts:
job:
......@@ -14,10 +14,10 @@ visibility: public
metadata:
source: https://git.linaro.org/lava-team/refactoring.git
path: doc/v2/examples/test-jobs/qemu-amd64-standard-jessie.yaml
build-readme: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/amd64/7/debian-jessie-amd64-readme.html
build-console: https://ci.linaro.org/view/lava-ci/job/lava-debian-stable-amd64-vm/7/console
build-log: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/amd64/7/vmdebootstrap.log
path: doc/v2/examples/test-jobs/qemu-amd64-standard-stretch.yaml
build-readme: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/amd64/2/debian-stretch-amd64-readme.html
build-console: https://ci.linaro.org/view/lava-ci/job/lava-debian-stretch-amd64-vm/console
build-log: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/amd64/2/vmdebootstrap.log
# CONTEXT_BLOCK
context:
......@@ -34,8 +34,8 @@ actions:
images:
rootfs:
image_arg: -drive format=raw,file={rootfs}
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/amd64/7/large-stable.img.gz
sha256sum: 4ab50cc69fc61faa9bf48edada8bc1a317247f77ced5a815f40e75cef1d62cc7
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/amd64/2/stretch.img.gz
sha256sum: b5cdb3b9e65fec2d3654a05dcdf507281f408b624535b33375170d1e852b982c
compression: gz
os: debian
root_partition: 1
......
......@@ -5,7 +5,7 @@ device_type: beaglebone-black
job_name: standard Debian ARMMP nfs test on bbb
timeouts:
job:
minutes: 10
minutes: 15
action:
minutes: 5
connection:
......@@ -16,32 +16,32 @@ visibility: public
metadata:
source: https://git.linaro.org/lava/lava-server.git
path: doc/v2/examples/test-jobs/standard-armmp-nfs-bbb.yaml
build-readme: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/debian-armmp-armhf-readme.html
build-console: https://ci.linaro.org/view/lava-ci/job/lava-debian-armmp-armhf/4/console
build-script: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/armmp-nfs.sh
build-readme: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/debian-stretch-armmp-armhf-readme.html
build-console: https://ci.linaro.org/view/lava-ci/job/lava-debian-stretch-armmp-armhf/3/console
build-script: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/armmp-nfs.sh
actions:
- deploy:
timeout:
minutes: 4
minutes: 10
to: tftp
kernel:
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/vmlinuz
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/vmlinuz-4.9.0-4-armmp
type: zimage
ramdisk:
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/initramfs.cpio.gz
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/initrd.img-4.9.0-4-armmp
compression: gz
# the bootloader needs a u-boot header on the modified ramdisk
add-header: u-boot
modules:
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/modules.tar.gz
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/modules.tar.gz
compression: gz
nfsrootfs:
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/jessie-armhf-nfs.tar.gz
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/stretch-armhf-nfs.tar.gz
compression: gz
os: debian
dtb:
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/dtbs/am335x-boneblack.dtb
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/dtbs/am335x-boneblack.dtb
- boot:
method: u-boot
......@@ -50,7 +50,7 @@ actions:
login_prompt: 'login:'
username: root
prompts:
- 'root@jessie:'
- 'root@stretch:'
timeout:
minutes: 2
......@@ -70,4 +70,3 @@ actions:
repository: http://git.linaro.org/lava-team/lava-functional-tests.git
path: lava-test-shell/single-node/singlenode02.yaml
name: singlenode-intermediate
device_type: cubietruck
# NFS fails on arndale.
# NFS fails on panda and arndale.
job_name: standard Debian ARMMP nfs test on cubietruck
timeouts:
......@@ -16,9 +16,9 @@ visibility: public
metadata:
source: https://git.linaro.org/lava/lava-server.git
path: doc/v2/examples/test-jobs/standard-armmp-nfs-cubietruck.yaml
build-readme: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/debian-armmp-armhf-readme.html
build-console: https://ci.linaro.org/view/lava-ci/job/lava-debian-armmp-armhf/4/console
build-script: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/armmp-nfs.sh
build-readme: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/debian-stretch-armmp-armhf-readme.html
build-console: https://ci.linaro.org/view/lava-ci/job/lava-debian-stretch-armmp-armhf/3/console
build-script: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/armmp-nfs.sh
actions:
- deploy:
......@@ -26,22 +26,22 @@ actions:
minutes: 4
to: tftp
kernel:
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/vmlinuz
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/vmlinuz-4.9.0-4-armmp
type: zimage
ramdisk:
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/initramfs.cpio.gz
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/initrd.img-4.9.0-4-armmp
compression: gz
# the bootloader needs a u-boot header on the modified ramdisk
add-header: u-boot
modules:
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/modules.tar.gz
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/modules.tar.gz
compression: gz
nfsrootfs:
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/jessie-armhf-nfs.tar.gz
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/stretch-armhf-nfs.tar.gz
compression: gz
os: debian
dtb:
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/dtbs/sun7i-a20-cubietruck.dtb
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/dtbs/sun7i-a20-cubietruck.dtb
- boot:
method: u-boot
......@@ -50,7 +50,7 @@ actions:
login_prompt: 'login:'
username: root
prompts:
- 'root@jessie:'
- 'root@stretch:'
timeout:
minutes: 2
......@@ -70,4 +70,3 @@ actions:
repository: http://git.linaro.org/lava-team/lava-functional-tests.git
path: lava-test-shell/single-node/singlenode02.yaml
name: singlenode-intermediate
......@@ -14,9 +14,9 @@ visibility: public
metadata:
source: https://git.linaro.org/lava/lava-server.git
path: doc/v2/examples/test-jobs/standard-armmp-nfs-panda.yaml
build-readme: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/debian-armmp-armhf-readme.html
build-console: https://ci.linaro.org/view/lava-ci/job/lava-debian-armmp-armhf/4/console
build-script: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/armmp-nfs.sh
build-readme: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/debian-stretch-armmp-armhf-readme.html
build-console: https://ci.linaro.org/view/lava-ci/job/lava-debian-stretch-armmp-armhf/3/console
build-script: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/armmp-nfs.sh
actions:
- deploy:
......@@ -24,22 +24,22 @@ actions:
minutes: 5
to: tftp
kernel:
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/vmlinuz
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/vmlinuz-4.9.0-4-armmp
type: zimage
ramdisk:
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/initramfs.cpio.gz
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/initrd.img-4.9.0-4-armmp
compression: gz
# the bootloader needs a u-boot header on the modified ramdisk
add-header: u-boot
modules:
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/modules.tar.gz
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/modules.tar.gz
compression: gz
nfsrootfs:
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/jessie-armhf-nfs.tar.gz
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/stretch-armhf-nfs.tar.gz
compression: gz
os: debian
dtb:
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/dtbs/omap4-panda.dtb
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/dtbs/omap4-panda.dtb
- boot:
method: u-boot
......@@ -48,13 +48,13 @@ actions:
login_prompt: 'login:'
username: root
prompts:
- 'root@jessie:'
- 'root@stretch:'
timeout:
minutes: 10
- test:
timeout:
minutes: 15
minutes: 10
definitions:
- repository: http://git.linaro.org/lava-team/lava-functional-tests.git
from: git
......
......@@ -23,9 +23,9 @@ visibility: public
metadata:
source: https://git.linaro.org/lava/lava-server.git
path: doc/v2/examples/test-jobs/standard-armmp-ramdisk-arndale.yaml
build-readme: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/debian-armmp-armhf-readme.html
build-console: https://ci.linaro.org/view/lava-ci/job/lava-debian-armmp-armhf/4/console
build-script: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4/armmp-nfs.sh
build-readme: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/debian-stretch-armmp-armhf-readme.html
build-console: https://ci.linaro.org/view/lava-ci/job/lava-debian-stretch-armmp-armhf/3/console
build-script: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/armhf/3/armmp-nfs.sh
actions:
- deploy:
......@@ -33,20 +33,20 @@ actions:
minutes: 3
to: tftp
kernel: