1. 15 Oct, 2021 2 commits
  2. 06 Oct, 2021 4 commits
  3. 01 Oct, 2021 1 commit
  4. 17 Sep, 2021 1 commit
    • Frederic Danis's avatar
      Add development test mode · 33eb4598
      Frederic Danis authored
      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: Frederic Danis's avatarFrédéric Danis <frederic.danis@collabora.com>
  5. 16 Sep, 2021 1 commit
  6. 13 Sep, 2021 4 commits
  7. 08 Sep, 2021 1 commit
  8. 01 Sep, 2021 1 commit
  9. 27 Aug, 2021 1 commit
  10. 26 Aug, 2021 2 commits
  11. 25 Aug, 2021 1 commit
  12. 19 Aug, 2021 2 commits
    • Frederic Danis's avatar
      Add release version and board tag · a4da9c15
      Frederic Danis authored
      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: Frederic Danis's avatarFrédéric Danis <frederic.danis@collabora.com>
    • Frederic Danis's avatar
      Use image_url · a2be2a05
      Frederic Danis authored
      The image URL is already provided and we don't have to create it manually.
      Signed-off-by: Frederic Danis's avatarFrédéric Danis <frederic.danis@collabora.com>
  13. 02 Jul, 2021 1 commit
  14. 01 Jul, 2021 3 commits
  15. 17 Mar, 2021 1 commit
  16. 12 Mar, 2021 1 commit
  17. 07 Jan, 2021 2 commits
  18. 19 Nov, 2020 2 commits
    • Emanuele Aina's avatar
      gitlab-ci: Tag the tagging job as lightweight · d4dff7e8
      Emanuele Aina authored
      Use a lightweight runner to tag the Docker images so it has a much
      reduced latency as it does not have to spin up a (expensive) VM
      from scratch.
      Other jobs are likely too heavy for the lightweight runner.
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
    • Emanuele Aina's avatar
      Ensure that re-starting a test job updates the report · 3802c3b5
      Emanuele Aina authored
      Sometimes test job fail for a multitude of reasons, so it's useful to be
      able to re-trigger them and see the updated results in the report.
      Unfortunately the report was not using any kind of consistent ordering,
      so it may have picked results from older jobs even if a new one had been
      completed for the same release/buildid/suites.
      Tweak the report to pick jobs by the time the app gets notified about
      them, so that when a re-triggered job gets submitted its results
      override in the report the results from previous jobs.
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
  19. 17 Nov, 2020 1 commit
    • Emanuele Aina's avatar
      Summarize results in the index · 274128d2
      Emanuele Aina authored
      Provide an overview of the results for each run by showing some
      aggregated counters by deployment type, listing the number of
      executed testcases, how many of them are automated vs. manual,
      and pass/skip/fail/incomplete counters.
      Do this with a single SQL query returning a nested JSON structure
      with all the data in it.
      This moves some complexity from Python code to a relatively large but
      not overly complex SQL query.
      As a shortcut, the SQL query uses the Postgres-specific `DISTINCT ON`
      syntax to keep things simple and fast.
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
  20. 10 Nov, 2020 4 commits
  21. 04 Nov, 2020 1 commit
  22. 03 Nov, 2020 1 commit
    • Emanuele Aina's avatar
      Fix handling of incomplete jobs failing before git checkout · ab7148ee
      Emanuele Aina authored
      When available, we look for the checkout information to find the commit
      id for each testcase. However, if the job fails in the early stages,
      before being able to check anything out, then such information is not
      available, so we should handle gracefully the case instead of hitting
      an exception:
          Exception on / [POST]
          Traceback (most recent call last):
            File "/usr/lib/python3/dist-packages/flask/app.py", line 2292, in wsgi_app
              response = self.full_dispatch_request()
            File "/usr/lib/python3/dist-packages/flask/app.py", line 1815, in full_dispatch_request
              rv = self.handle_user_exception(e)
            File "/usr/lib/python3/dist-packages/flask/app.py", line 1718, in handle_user_exception
              reraise(exc_type, exc_value, tb)
            File "/usr/lib/python3/dist-packages/flask/_compat.py", line 35, in reraise
              raise value
            File "/usr/lib/python3/dist-packages/flask/app.py", line 1813, in full_dispatch_request
              rv = self.dispatch_request()
            File "/usr/lib/python3/dist-packages/flask/app.py", line 1799, in dispatch_request
              return self.view_functions[rule.endpoint](**req.view_args)
            File "./webhook.py", line 203, in post_results
              return process_job(job_data)
            File "./webhook.py", line 248, in process_job
              jobs.setdefault(job_id, TestJob(job_data)).update(job_data)
            File "/app/testobjects.py", line 216, in __init__
            File "/app/testobjects.py", line 224, in update
              data = lava_jobdata_extract(rawdata)
            File "/app/testobjects.py", line 185, in lava_jobdata_extract
            File "/app/testobjects.py", line 150, in lava_jobdata_extract_results
              action, extra = actions[t['repository'], t['path']]
          KeyError: ('https://gitlab.apertis.org/tests/apertis-test-cases.git
      ', 'test-cases/sanity-check.yaml')
      In turn, this exception causes jobs not being marked as completed,
      and thus we never manage to update Phabricator since the batch is stuck
      with pending jobs forever.
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
  23. 04 Oct, 2020 1 commit
  24. 24 Sep, 2020 1 commit