Skip to content
Snippets Groups Projects
  1. Nov 12, 2021
  2. Nov 07, 2021
    • Manuel Stoeckl's avatar
      gl-renderer: add support for (a|x)bgr16161616f shm formats · 742a0232
      Manuel Stoeckl authored
      
      These formats will be eventually be useful for color managed clients
      using wl_shm that wish to submit buffers encoding high dynamic range
      images.
      
      While the minimum requirement for linearly filterable half float
      textures is GL ES 2.0 + GL_OES_texture_half_float_linear, to keep
      the code simple, this commit only enables the new formats when
      the requirements for color management (notably including GL ES 3.0
      and GL_EXT_color_buffer_half_float) are available.
      
      Signed-off-by: default avatarManuel Stoeckl <code@mstoeckl.com>
      742a0232
  3. Nov 03, 2021
  4. Nov 02, 2021
  5. Nov 01, 2021
  6. Oct 27, 2021
  7. Oct 25, 2021
  8. Oct 20, 2021
  9. Oct 18, 2021
  10. Oct 15, 2021
  11. Oct 14, 2021
  12. Oct 05, 2021
  13. Oct 01, 2021
  14. Sep 29, 2021
  15. Sep 28, 2021
    • Derek Foreman's avatar
      input: fix keyboard focus crash · a822afaa
      Derek Foreman authored and Marius Vlad's avatar Marius Vlad committed
      
      If two or more clients were running and the one that was focused when
      weston itself lost keyboard focus was killed, weston would crash.
      
      This is because commit 85d55540 changed the way we handle saved keyboard
      focus when we lose focus, and did so in such a way that the saved keyboard
      focus listener could be removed from the surface destroy signal list
      during the emit of the surface destroy signal. This corrupted the list
      and led to a NULL pointer dereference.
      
      Fix this by using a boolean flag to determine whether we should obey the
      saved keyboard focus. We can set this safely in cases where
      removing the listener would cause a crash.
      
      Fixes #138
      
      Signed-off-by: default avatarDerek Foreman <derek.foreman@collabora.com>
      a822afaa
  16. Sep 22, 2021
    • Pekka Paalanen's avatar
      ci: bump test timeouts · 645df955
      Pekka Paalanen authored
      This is prompted by the spurious CI failure
      https://gitlab.freedesktop.org/wayland/weston/-/jobs/13891809
      
      
      saying:
      
      31/36 output-damage                          TIMEOUT        122.52s   8 subtests passed
      32/36 output-transforms                      TIMEOUT        122.52s   16 subtests passed
      33/36 subsurface                             TIMEOUT        122.52s
      34/36 xwayland                               TIMEOUT        122.51s
      35/36 ivi-shell-app                          TIMEOUT        122.51s
      ERROR: Job failed: execution took longer than 5m0s seconds
      
      That is hitting both kinds of timeouts at the same time: the per-test
      timeouts, and the CI job total timeout.
      
      That run seems to have had a particularly ill fortune, as a simple retry
      finished the same job in 2 minutes, and the longest running test took
      only 24 seconds.
      
      Nevertheless, by Daniel Stone's suggestion let's bump both timeouts:
      
      - the per-test timeout to 120 seconds, which with the multiplier in CI
        goes up to 8 minutes
      
      - the job timeout for all build related jobs to 15 minutes
      
      The timeout for tests_standalone is not bumped as we are not adding
      significant amounts of new tests there.
      
      Signed-off-by: default avatarPekka Paalanen <pekka.paalanen@collabora.com>
      645df955
  17. Sep 15, 2021
Loading