Skip to content

tests: Allow progress to be unknown or 100% after flatpak installation

This might fix a flaky test in the CI, where sometimes the progress after installation is queried as 100%, and sometimes it’s queried as unknown.

I think the race happens because flatpak operations (and progress updates) happen in another thread, and the unit test code can query at the point of installation being complete (seeing 100%), or once the app progress has been reset after installation (seeing unknown).

Signed-off-by: Philip Withnall pwithnall@endlessos.org

Fixes: #1107 (closed)

Merge request reports