GitLab

Ryan Gonzalez authored Dec 27, 2021 and Walter Lozano committed Jan 18, 2022

https://phabricator.apertis.org/T6660

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

Emanuele Aina authored Jan 07, 2022 and Walter Lozano committed Jan 18, 2022

Commit 9af32dad

 "Consider the release when checking for completion"
added the ability to include the release name in the notification
emails, but the override in the sample config was not updated to make
use of that.
Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

When building latest images, minimal rendering differences are noticed
causing unit test to fail. Update the screenshots to allow the tests
to pass.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

When using pygit2 1.7.2 on Debian Bullseye SSL cerficate check for
gitlab.apertis.org fails with `user rejected certificate for
gitlab.apertis.org` preventing updates test cases.

Work around this issue by force installing pygit2 version 1.7.1.

See: https://github.com/libgit2/pygit2/issues/1115

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Detlev Casanova authored Dec 17, 2021 and Emanuele Aina committed Dec 18, 2021

This fixes an issue where hmi amd64 ostree images have no tests.
Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

The name 'sdk-arm64-uefi' was used but the correct board name for SDK
images is 'sdk'. All entries of 'sdk-arm64-uefi' is replaced by 'sdk-arm64-sdk'
Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

Detlev Casanova authored Dec 02, 2021 and Emanuele Aina committed Dec 03, 2021

Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

Rename an entry identifier from `target-armhf-internal` to
`target-armhf-uboot-internal` for v2020 and prior reports to fix an
exception when rendering.
Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Manual test results that got submitted with this app have
`image_platform` set to `NULL`, which causes any report that includes
manual test results to blow up with a "Report error" exception due
to `str.join()` stumbling on `None` when computing image type
identifiers like `target-amd64-uefi-public`.

Luckily in old submissions we can infer the platform quite reliably from
just the image type and architecture. New submissions should get the
`image_platform` field set appropriately since commit
01ab19a3

 "pages: Add platform name in image_type list".
Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

This adds the following images:
 * fixedfunction-arm64-rpi64-public (apt + ostree)
 * hmi-arm64-rpi64-public
Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

This adds a field in the image type strings:
* uboot for armhf and arm64
* uefi for amd64

This is a preparation change to add test results for the
IMAGE_TYPE-arm64-rpi64 image type
Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

Emanuele Aina authored Nov 17, 2021 and Walter Lozano committed Nov 17, 2021

Align the bugs created by the bridge to the template used when manually
creating them.
Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Emanuele Aina authored Nov 17, 2021 and Walter Lozano committed Nov 17, 2021

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

Emanuele Aina authored Nov 17, 2021 and Walter Lozano committed Nov 17, 2021

When tracking the pending jobs, use both the release and the build id to
identify a batch, not just the build id.

This has been the case in practice for a while, since the build ids
reflect the time each build is started and they are scheduled
differently, but formalizing it in the code allow us to explicitly
indicate the release when sending notifications.
Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Emanuele Aina authored Nov 16, 2021 and Walter Lozano committed Nov 17, 2021

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

Include a new test case based on previous one to take into account LAVA
jobs that use branch instead of revision.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Test cases can use branch instead of revision to allow LAVA to use a
shallow clone and reducing the overlay size. Add its support to allow
the app the parse these LAVA test definitions.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

In order to be consistent across the whole document fix the format used
in the deployment section.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Since in some cases it is needed to do testing with real data add steps
to import the database from production.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored Oct 05, 2021 and Frederic Danis committed Oct 06, 2021

Fix the command line use to launch application in development mode.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Walter Lozano authored Oct 05, 2021 and Frederic Danis committed Oct 06, 2021

In order to allow git fetch to properly update a bare repository use
mirror, which implies bare and also maps refs.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Sjoerd Simons authored Oct 01, 2021 and Emanuele Aina committed Oct 01, 2021

To allow easy monitor the submitted jobs in another *gitlab* job dump
add the ability to dump the ids to a json file. This can then be used as
an artifact to pass on to a monitoring job.
Signed-off-by: Sjoerd Simons <sjoerd@collabora.com>

The `qa-report-app` container does not allow to run with setting GitLab
authentication, which doesn't allow easy development.

Add a parameter to `qa-report-app` to disable authentication, and configure
the development container, i.e. docker-compose.override.yml, to disable
authentication and connection to Phabricator.
Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Retrieval of test cases by release are now done using remote branches, we
can avoid to check out the worktree and directly work on bare repository.
Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Even if its public and encode by Lava in job data, it's better to remove
the token from job_data for tests.
Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

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

The branches needs to be updated or removed before updating the testcases
directory.
Simplify the code by using pygit2.
Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Current version generates the testcases from default branches, i.e. the
latest release. As the test cases diverge from release to release, some of
the previous versions tests are not available.

This commit generates the list of all tests for each version.
Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

`target` images have been renamed to `hmi` during the v2022 development 
cycle, let's make sure this is taken into account.
Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

The recent changes in the testcases caused the results for minimal and
internal images to ber marked `N/A` on older releases like v2020 and
v2020, due to the app not really supporting diverging releases since it
only loads the testcase definitions from the apertis-test-cases HEAD.

To work around the issue, add some hacks until diverging releases are
properly supported, see https://phabricator.apertis.org/T8245.

This also reverts commit 86bf12d6

 "Update test screenshot"
which actually caught the issue but was mistakenly interpreted as the
desired outcome.
Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

During the process of adding support for fixed function image a bug wasi
introduced that caused only fixed function images reports where showed.

Fix the different conditions used to render the report between different
releases.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

This reflects the change in our infrastructure and the name of the
`qa-report-app` container.
Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

The minimal test are no more applicable as they have been replaced by
fixedfunction one, so the test image needs to be updated.
Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

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

Comment added to bug task doesn't indicate the release version for which
the failure occurs, people need to open the links to the LAVA logs to find
whether the bug affect a release (like v2021dev2 vs. v2020 vs. etc.).

It should also indicate the board tag used in the test, like `cbg-0` or
`cbg-1`, to make it easier to identify board specific issues.

And it should have links to the involved images, like it is being done
when creating the task.
Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>