15/38 tracker:fts / fts FAIL 0.62s killed by signal 5 SIGTRAP against sqlite-3.42.0 (3.41.2 was ok)
Noticed the problem a s tracer
test failure after NixOS
upgraded sqlite
from 3.41.2
to 3.42.0
: https://github.com/NixOS/nixpkgs/pull/232333
There one tracker
test started failing:
15/38 tracker:fts / fts FAIL 0.62s killed by signal 5 SIGTRAP
>>> TRACKER_DEBUG=fts-integrity TRACKER_LANGUAGE_STOP_WORDS_DIR=/build/tracker-3.5.1/src/libtracker-common/stop-words LANG=en_US.UTF8 MALLOC_PERTURB_=80 LD_LIBRARY_PATH=/build/tracker-3.5.1/build/src/libtracker-sparql:/build/tracker-3.5.1/build/tests/common /build/tracker-3.5.1/build/tests/fts/tracker-fts-test
✀
stdout:
TAP version 13
# random seed: R02S9d86e359fa83765166c1026681d36431
1..10
# Start of fts tests
# GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
# Tracker-DEBUG: Checking for adequate disk space to create databases, 96.1?GB remaining, 5.2?MB required as a minimum
# Tracker-DEBUG: Applying ontologies from /build/tracker-3.5.1/tests/fts
# Tracker-DEBUG: Saving DB locale as: 'C'
# Tracker-DEBUG: Cleaning up stale resource URIs
ok 1 /fts/fts3aa
# Tracker-DEBUG: Checking for adequate disk space to create databases, 96.1?GB remaining, 5.2?MB required as a minimum
# Tracker-DEBUG: Applying ontologies from /build/tracker-3.5.1/tests/fts
# Tracker-DEBUG: Saving DB locale as: 'C'
# Tracker-DEBUG: Cleaning up stale resource URIs
ok 2 /fts/fts3ae
# Start of consistency tests
# Tracker-DEBUG: Checking for adequate disk space to create databases, 96.1?GB remaining, 5.2?MB required as a minimum
# Tracker-DEBUG: Applying ontologies from /build/tracker-3.5.1/tests/fts
# Tracker-DEBUG: Saving DB locale as: 'C'
# Tracker-DEBUG: Cleaning up stale resource URIs
ok 3 /fts/consistency/partial-update
# Tracker-DEBUG: Checking for adequate disk space to create databases, 96.1?GB remaining, 5.2?MB required as a minimum
# Tracker-DEBUG: Applying ontologies from /build/tracker-3.5.1/tests/fts
# Tracker-DEBUG: Saving DB locale as: 'C'
# Tracker-DEBUG: Cleaning up stale resource URIs
ok 4 /fts/consistency/insert-or-replace
# End of consistency tests
# Start of prefix tests
# Tracker-DEBUG: Checking for adequate disk space to create databases, 96.1?GB remaining, 5.2?MB required as a minimum
# Tracker-DEBUG: Applying ontologies from /build/tracker-3.5.1/tests/fts
# Tracker-DEBUG: Saving DB locale as: 'C'
# Tracker-DEBUG: Cleaning up stale resource URIs
ok 5 /fts/prefix/fts3prefix
# End of prefix tests
# Start of limits tests
# Tracker-DEBUG: Checking for adequate disk space to create databases, 96.1?GB remaining, 5.2?MB required as a minimum
# Tracker-DEBUG: Applying ontologies from /build/tracker-3.5.1/tests/fts
# Tracker-DEBUG: Saving DB locale as: 'C'
# Tracker-DEBUG: Cleaning up stale resource URIs
ok 6 /fts/limits/fts3limits
# End of limits tests
# Start of input tests
# Tracker-DEBUG: Checking for adequate disk space to create databases, 96.1?GB remaining, 5.2?MB required as a minimum
# Tracker-DEBUG: Applying ontologies from /build/tracker-3.5.1/tests/fts
# Tracker-DEBUG: Saving DB locale as: 'C'
# Tracker-DEBUG: Cleaning up stale resource URIs
ok 7 /fts/input/fts3input
# End of input tests
# Start of functions tests
# Tracker-DEBUG: Checking for adequate disk space to create databases, 96.1?GB remaining, 5.2?MB required as a minimum
# Tracker-DEBUG: Applying ontologies from /build/tracker-3.5.1/tests/fts
# Tracker-DEBUG: Saving DB locale as: 'C'
# Tracker-DEBUG: Cleaning up stale resource URIs
ok 8 /fts/functions/rank
# Tracker-DEBUG: Checking for adequate disk space to create databases, 96.1?GB remaining, 5.2?MB required as a minimum
# Tracker-DEBUG: Applying ontologies from /build/tracker-3.5.1/tests/fts
# Tracker-DEBUG: Saving DB locale as: 'C'
# Tracker-DEBUG: Cleaning up stale resource URIs
ok 9 /fts/functions/offsets
# Tracker-DEBUG: Checking for adequate disk space to create databases, 96.1?GB remaining, 5.2?MB required as a minimum
# Tracker-DEBUG: Applying ontologies from /build/tracker-3.5.1/tests/fts
# Tracker-DEBUG: Saving DB locale as: 'C'
not ok /fts/functions/snippet - Tracker-FATAL-ERROR: --- /build/tracker-3.5.1/tests/fts/functions/snippet-3.out 2023-04-25 14:30:54.000000000 +0000 +++ - 2023-05-20 07:15:39.291404466 +0000 @@ -1,4 +1,4 @@ "http://www.example.org/test#1" ">>>bananas<<<..." -"http://www.example.org/test#2" ">>>bananas<<< >>>bananas<<<..." +"http://www.example.org/test#2" ">>>bananas<<<..." "http://www.example.org/test#4" ">>>bananas<<<..." "http://www.example.org/test#3" ">>>bananas<<<"
Bail out!
stderr:
parsing-error: file:///build/tracker-3.5.1/tests/fts/data.ontology:11:21: Duplicate definition of namespace http://tracker.api.gnome.org/ontology/v3/fts#
parsing-error: file:///build/tracker-3.5.1/tests/fts/data.ontology:11:21: Duplicate definition of namespace http://tracker.api.gnome.org/ontology/v3/fts#
parsing-error: file:///build/tracker-3.5.1/tests/fts/data.ontology:11:21: Duplicate definition of namespace http://tracker.api.gnome.org/ontology/v3/fts#
parsing-error: file:///build/tracker-3.5.1/tests/fts/data.ontology:11:21: Duplicate definition of namespace http://tracker.api.gnome.org/ontology/v3/fts#
parsing-error: file:///build/tracker-3.5.1/tests/fts/data.ontology:11:21: Duplicate definition of namespace http://tracker.api.gnome.org/ontology/v3/fts#
parsing-error: file:///build/tracker-3.5.1/tests/fts/data.ontology:11:21: Duplicate definition of namespace http://tracker.api.gnome.org/ontology/v3/fts#
parsing-error: file:///build/tracker-3.5.1/tests/fts/data.ontology:11:21: Duplicate definition of namespace http://tracker.api.gnome.org/ontology/v3/fts#
parsing-error: file:///build/tracker-3.5.1/tests/fts/data.ontology:11:21: Duplicate definition of namespace http://tracker.api.gnome.org/ontology/v3/fts#
parsing-error: file:///build/tracker-3.5.1/tests/fts/data.ontology:11:21: Duplicate definition of namespace http://tracker.api.gnome.org/ontology/v3/fts#
parsing-error: file:///build/tracker-3.5.1/tests/fts/data.ontology:11:21: Duplicate definition of namespace http://tracker.api.gnome.org/ontology/v3/fts#
Could be some side-effect of sqlite
change?