Multiple failures occurring against geary builds when scheduled on gcc150.osuosl.org
CI unit tests that write SQLite databases to disk fail when run on gcc150.osuosl.org
Geary has a couple of unit tests that necessarily involve writing data to disk. While SQLite does support in-memory databases and a few tests use that, its support for that is somewhat flaky so other tests need to use a persistent storage backed db. These tests call g_dir_make_tmp()
to create a new random temp dir under /tmp for each such test case in setup, the db file gets written there during the test, then the temp dir and its contents is deleted afterwards in teardown.
These tests run as as part of CI builds, and they in general succeed, except when run on gcc150.osuosl.org. When CI jobs run on that host, the job usually fails as a result of the unit tests timing out, and when that happens it's always one of these tests that writes a SQLite db to disk. My suspicion is either that the host clears /tmp whenever some job is finished, and another job finishing is thus nuking the test's files while running, or maybe whatever kind of volume /tmp resides is somehow estoetric enough that SQLite's locking etc can't handle it (NFS, maybe?).
If you look at Geary's CI jobs, essentially all of the successful ones haven't run on gcc150.osuosl.org, and all of the failed jobs have run on that host.
Flatpak CI jobs failing on gcc150.osuosl.org with "error: org.gnome.Sdk/x86_64/3.30 not installed"
Running with gitlab-runner 11.4.2 (cf91d5e1)
on gcc150.osuosl.org d836cf30
Using Docker executor with image registry.gitlab.gnome.org/gnome/gnome-runtime-images/gnome:master ...
Pulling docker image registry.gitlab.gnome.org/gnome/gnome-runtime-images/gnome:master ...
Using docker image sha256:0c9a97b2c4d9225bed94c32778b30e3ca285b37f9bc8f416e5da203e2c49d2aa for registry.gitlab.gnome.org/gnome/gnome-runtime-images/gnome:master ...
Running on runner-d836cf30-project-1894-concurrent-2 via gcc150.bak.milne.osuosl.org...
Cloning repository...
Cloning into '/builds/GNOME/geary'...
Checking out ae222ca8 as geary-0.13...
Skipping Git submodules setup
Checking cache for flatpak...
No URL provided, cache will be not downloaded from shared cache server. Instead a local version of cache will be extracted.
Successfully extracted cache
$ flatpak-builder --stop-at=${FLATPAK_MODULE} app ${MANIFEST_PATH}
error: org.gnome.Sdk/x86_64/3.30 not installed
Failed to init: Unable to find sdk org.gnome.Sdk version 3.30
Uploading artifacts...
WARNING: geary-dev.flatpak: no matching files
WARNING: _build/meson-logs/meson-log.txt: no matching files
WARNING: _build/meson-logs/testlog.txt: no matching files
ERROR: No files to upload
ERROR: Job failed: exit code 1