1. 21 May, 2022 2 commits
    • Benjamin Otte's avatar
      CI: Use mutter for the x11-full testsuite run · 68161f02
      Benjamin Otte authored
      This spawns a mutter WM for the xvfb instance and wraps it in its own
      dbus session.
      
      Also use a larger screen size (1080p) - mostly so we can check the
      testuite runs with differently sized screens, but alspo because that's
      today's default screen size.
      
      This exposes the issue from #4136 in the testsuite.
      68161f02
    • Benjamin Otte's avatar
      testsuite: Split X11 testsuite · 0e95145a
      Benjamin Otte authored
      Duplicate the X11 testsuite into x11full and x11bare.
      Run both of them in the Fedora CI runner.
      
      For now they do the same thing (followup commits will change that), but
      the goal is to have 2 testruns:
      
      x11full should get as close to simulating a modern full-featured setup
      with a compositing WM and all extensions.
      
      x11bare should have the minimum required setup that te testsuite needs,
      but nothing more. No compositor, a WM wit the minimal set of features,
      etc.
      0e95145a
  2. 09 Oct, 2021 1 commit
    • Benjamin Otte's avatar
      testsuite: Add run for GLES · e581c148
      Benjamin Otte authored
      This is supposed to test the most fallback GL stuff, so we might want to
      set even more env vars here.
      
      Also enable the run for the Fedora builder in CI.
      e581c148
  3. 22 Jan, 2021 2 commits
  4. 04 Aug, 2020 1 commit
  5. 26 Jul, 2020 1 commit
  6. 10 Jul, 2020 3 commits
  7. 09 Jul, 2020 1 commit
    • Matthias Clasen's avatar
      ci: Set LSAN_OPTIONS for tests · fa90e42a
      Matthias Clasen authored
      When running the testsuite with the address sanitizer,
      many of our dependencies cause it to report cause it
      to report memory leaks, causing tests to fail.
      Therefore, point the leak sanitizer at a list of
      suppressions. The list is kept in the lsan.supp
      file in git.
      fa90e42a
  8. 28 May, 2020 1 commit
  9. 16 May, 2020 1 commit
  10. 15 May, 2020 3 commits
    • Matthias Clasen's avatar
      ci: Add the backend to the reports · 01bd6cfd
      Matthias Clasen authored
      We want the test names in the junit xml to be
      unique across all the tests in a job, so we need
      to include the backend in the test name.
      
      And we also want to see the used backend in
      the html report.
      01bd6cfd
    • Matthias Clasen's avatar
      ci: Ignore Broadway failures · 30ef4814
      Matthias Clasen authored
      These need some more work, so ignore them for now,
      to get the initial multi-backend testsuite into
      production.
      30ef4814
    • Matthias Clasen's avatar
      ci: Run tests with different backends · 31cf8940
      Matthias Clasen authored
      Run the testsuite under x11, wayland and broadway
      in the fedora-x86_64 job. This requires us to use
      the v17 image which includes weston.
      31cf8940
  11. 12 Feb, 2020 1 commit
  12. 11 Feb, 2020 3 commits
    • Emmanuele Bassi's avatar
      ci: Generate the report for the release builds · 59028d7d
      Emmanuele Bassi authored
      We are going to need to hide the report generation into the test runner
      script, as we want the job to produce the reports even in case of
      failure, instead of bailing out immediately.
      59028d7d
    • Emmanuele Bassi's avatar
      ci: Add missing newline escape · c4dfacc4
      Emmanuele Bassi authored
      Otherwise we're going to run the accessibility test suite, and it's
      going to fail.
      c4dfacc4
    • Emmanuele Bassi's avatar
      ci: Refactor the CI pipeline · 56f9cdd9
      Emmanuele Bassi authored
      We should have a single job for building both static and shared
      versions of GTK. On the other hand, having a separate job for the
      release build would be a plus.
      
      Additionally, we shouldn't use an opaque script to build GTK; the only
      step in the process that requires hand-holding is running the tests
      suites under Xvfb, and having the build options visible from the YAML
      file gives us a better idea of what kind of build we're running.
      56f9cdd9