Frederic Danis authored 4 years ago and Denis Pynkin committed 4 years ago

wget needs the complete URL to be able to download key0.key file.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Earlier, we were using an old kerne and rootfs from 18.09.xx.

We've now switched to using a much newer one from v2020, which is where
it requires an update of our assumpt login prompts

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

In commit 83772e1 and later commits DTB names in Linux kernel was
renamed to align names with config options.
Hence the old DTB name `r8a7796-m3ulcb.dtb` is `8a77960-ulcb.dtb` for
Renesas M3 boards used in LAVA.

Old U-Boot versions are using the old naming schema including version
used in v2021dev3 atm.

This commit set proper name only for v2021dev3 branch allowing to boot
images for Renesas boards in LAVA.

Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>

Martyn Welch authored 4 years ago and Emanuele Aina committed 4 years ago

Rather than looping over branches (in included template from `pages`),
generate the test cases here, provide these as an artifact and deploy
in a separate job. This avoids the regeneration of pages that have
not changed.

Use the apertis-test-cases-web as part of a multi-project pipeline to
deploy. Remove the deployment tools from this branch.

Whilst we are here, utilise an environment variable for the release to
make it easier to migrate this between releases.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

The bundle generation with an unknown key doesn't display correctly.
Move bundle generation to `pre-conditions`.
Add `cryptsetup` package installation

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

The GitLab CI logic has been moved to the pages branch, remove the
logic from this branch and use the version on the pages branch.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

We want to have the pages updated whenever there's a change on any
`apertis/` branch. Drop the test case and allow the pages pipeline to be
run on any `apertis/` branch.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

We are going to start generating test cases for multiple generations of
Apertis to enable testing of stable releases. Add a menu to enable
browsing of the various releases.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Having the argument parsing in the atc_renderer code makes it much
harder to use it as a library. Pull the arg parsing into the
application.

As it turns out, atc didn't end up being used in this manner, but fix
it now to avoid this potentially needing to be addressed again in the
future.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

We want to redirect linking that pages without a version specified to
the latest to ensure existing linking continues to work. For everything
else, lets redirect to the main page.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

We want to move to providing test cases for multiple generations of
Apertis so as to enable us to develop the bits we need to do this,
begin by putting the existing output in `latest/`.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

The bundle generation with an unknown key doesn't display correctly.
Add a command to retrieve the `key0.key` file from gitlab.apertis.org.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

By default SabreLite board plays sound through HDMI connector.
In case tester want to output sound through headphone connector he should
configure PulseAudio for it.

After the 2 first commands (set-default-sink and set-sink-port) the sound
is heard correctly, but not after a reboot. This is due to mute state not
saved at this time, this needs the third command (after reboot) to fix it.
Further reboot will play sound correctly.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

This commit add commands to generate a static update bundle with a key
not known by the DUT, from the original encrypted update.
It allows to test that a static update encrypted with an unknown key is not
applied.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

New version of apertis-update-manager expects offline updates to be
encrypted.
The apertis-update-manager-automount test ensure that non encrypted
updates are not applied, while encrypted updates applies correctly.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Signed-off-by: Ritesh Raj Sarraf <rrs@debian.org>

The ssh-copy-id command syntax in sdk-ade-remote-debugging.yaml is
incorrect in two ways:

- The user is in capitals, whilst the actual username used should be in
  lower case
- The test case uses `$HOST` as a convention for the hostname/IP to be used
  for the target device, this command is missing the dollar sign.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Baghmar Tarun authored 4 years ago and Martyn Welch committed 4 years ago

Rework the testcase to not require packages to be installed and thus work on systems with an immutable rootfs like the ostree images.

Apertis: T5734

Signed-off-by: Tarun Baghmar <tarun.baghmar@in.bosch.com>

Commit  d0487486 "lava: Reduce redundancy in the profile
definitions" introduced a change that ended up causing issues with the
AUM tests, so let's go back to the previous state.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Emanuele Aina authored 4 years ago and Peter Senna Tschudin committed 4 years ago

Move from the old variable names which dates back to when the pipeline
was on Jenkins to something a bit more consistent.

This would be a breaking change for pipelines which include the
template, but since the main recipe repo has not switched over yet we
can play fast and loose safely.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Emanuele Aina authored 4 years ago and Peter Senna Tschudin committed 4 years ago

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Use YAML anchors and extensions to avoid repeating the same contents over
and over.

This commit does not introduce any change in the generated job
definitions, except for the case below, which is harmless:

    apertis_ostree-minimal-armhf-uboot
    -      commands: ['reset']
    +      commands: ['run bootcmd_mmc0']

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

The test currently fails due to timeout.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Use the multiple ostree preconditions support introduced in 6b2fd91e
instead of hardcoding the blurb for the second repository.

Also fix the branches and the resulting paths for the unpacked scripts.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

It turns out that LAVA really wants strings for the metadata entries and
didn't like nesting a dictionary there.

For this reason it was failing to submit jobs with this error:

    Submitting job group-apparmor-tpl.yaml: <Fault 400: "Problem with submitted job data: expected str for dictionary value @ data['metadata']['source']">

Unfortunately our custom `lava-submit.py` was silently eating the error
so the pipeline was marked as successful.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Baghmar Tarun authored 4 years ago and Emanuele Aina committed 4 years ago

Rework the testcase to not require packages to be installed and thus
work on systems with an immutable rootfs like the ostree images.

Apertis: T5734

Signed-off-by: Baghmar Tarun <tarun.baghmar@in.bosch.com>

The `${source_wip:=false}` snippet not only sets the `$source_wip`
variable if unset, but also executes the result of its expansion.

In our case it executed `false`, which made the pipeline very unhappy.

However, all tests submitted from this repository directly should be
considered "wip" and it will be up to the image repository including the
gitlab-ci job template to define the logic for which submissions should
be "wip" or not.

So drop the logic and use a plain `source_wip` variable defaulting to
`true`. The meaning of the variable was not documented either, so add a
blurb about it.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Address a regression introduced in commit 6b2fd91e "Turn the OSTree
preconditions into a list" where the iteration on the preconditions list
was done improperly.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

The LAVA lab is currently facing badnwidth issues. Switching to a
different ISP is planned, but due to the COVID impact there's no
progress on that front.

The current ade tests got badly impacted, with the download phase
consuming all the allocated time.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

The `source:wip:` metadata can be used to indicate that a submission
came from a work-in-progress branch and that it should not be accounted
when checking the overall health of the projects.

For instance, the Phabricator bridge can use this information to avoid
opening bug tasks for failures coming from a WIP branch.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Introduce the variables below:

* source_ref
* source_commit
* source_pipeline
* source_job

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

In preparation for adding more metadata, make the `source` entry an
object rather than a single string.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Default to `null` rather than hardconding a possibly misleading source.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Baghmar Tarun authored 4 years ago and Emanuele Aina committed 4 years ago

If a test case requires multiple repositories it can now use a list of
objects as the OSTree preconditions to check them all out.

Signed-off-by: Baghmar Tarun <tarun.baghmar@in.bosch.com>

Submit every modification to LAVA as part of the pipeline to set up a
direct feedback loop on non-main branches.

The image recipes pipeline can then re-use the job template here.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Port the below MR from apertis-tests, which got landed while we were
moving the templates around:
https://gitlab.apertis.org/pkg/development/apertis-tests/-/merge_requests/190



This reverts the introduction of the OTA update tests on the internal
minimal armhf since their behavior isn't stable and there is no value to
test AUM on this platform.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Keeping the LAVA job templates in `apertis-tests` has many problems.

Since `apertis-tests` is also a package, updates for stable releases
should go through `-updates` branches, but that plays badly with the
image building recipes as they only pull from the the main branch.

There's also an annoying disconnect about what the testcases here say
about where they should be run, and the actual groups used by the
templates.

By moving the LAVA templates here we can later improve them by
generating the groups based on the actual data in the testcases.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>