After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 735257 - tracker-steroids test failure
tracker-steroids test failure
Status: RESOLVED FIXED
Product: tracker
Classification: Core
Component: Tests
1.1.x
Other Linux
: Normal normal
: ---
Assigned To: tracker-general
tracker-general
Depends on:
Blocks:
 
 
Reported: 2014-08-23 01:36 UTC by darkxst
Modified: 2016-05-14 11:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description darkxst 2014-08-23 01:36:21 UTC
These tests are now failing on 1.1 and 1.0 branches

==========================================================
   tracker 1.1.3: tests/tracker-steroids/test-suite.log
==========================================================

# TOTAL: 2
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 2

.. contents:: :depth: 2

ERROR: tracker-test
===================

**
Tracker:ERROR:tracker-test.c:62:insert_test_data: assertion failed (error == NULL): GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: cannot commit transaction - SQL statements in progress (strerror of errno (not necessarily related): Resource temporarily unavailable) (tracker_sparql_error-quark, 6)
# random seed: R02S8542254c186f7474b19360e90f56248d
Aborted (core dumped)
# Tracker:ERROR:tracker-test.c:62:insert_test_data: assertion failed (error == NULL): GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: cannot commit transaction - SQL statements in progress (strerror of errno (not necessarily related): Resource temporarily unavailable) (tracker_sparql_error-quark, 6)
ERROR: tracker-test - missing test plan
ERROR: tracker-test - exited with status 134 (terminated by signal 6?)
Comment 1 Martyn Russell 2014-08-26 09:01:19 UTC
Hi Darkxst,

I haven't been able to reproduce this on master or the tracker-1.0 branches so I can't verify this.

But it looks like you're DB is busy (indexing?) with other things. If so, it's entirely possible a timeout causes this test failure.

Are you able to verify that?
Comment 2 Martyn Russell 2015-07-12 19:52:30 UTC
Moving bugs into new "tests" component.
Comment 3 Carlos Garnacho 2016-05-14 11:38:59 UTC
A few years (and a few releases/distcheck in between) went by. I'm assuming this is fixed.