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 621763 - evolution-data-server-2.30.1: FAIL: test-ebook-stress-factory--fifo
evolution-data-server-2.30.1: FAIL: test-ebook-stress-factory--fifo
Status: RESOLVED OBSOLETE
Product: evolution-data-server
Classification: Platform
Component: general
2.30.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-06-16 11:44 UTC by Pacho Ramos
Modified: 2010-06-21 15:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pacho Ramos 2010-06-16 11:44:45 UTC
I get the following:

PASS: test-ebook-remove
PASS: test-ebook-get-required-fields
PASS: test-ebook-get-static-capabilities
PASS: test-ebook-get-supported-fields
PASS: test-ebook-get-supported-auth-methods
PASS: test-ebook-add-contact
PASS: test-ebook-get-contact
PASS: test-ebook-get-book-view
PASS: test-ebook-commit-contact
PASS: test-ebook-remove-contact
PASS: test-ebook-remove-contact-by-id
PASS: test-ebook-remove-contacts
PASS: test-ebook-stress-factory--serial

(process:1071): libebook-WARNING **: e-book.c:2576: unmatched error name org.gnome.evolution.dataserver.addressbook.Book.EDATABOOKSTATUSOTHERERROR

** (process:1071): WARNING **: failed to remove book; Cannot remove book

FAIL: test-ebook-stress-factory--fifo
PASS: test-ebook-stress-factory--single-book
======================================================================================
1 of 15 tests failed
Please report to http://bugzilla.gnome.org/enter_bug.cgi?product=Evolution-Data-Server
======================================================================================
make[4]: *** [check-TESTS] Error 1
make[4]: Leaving directory `/home/pacho/evolution-data-server-2.30.1/addressbook/tests/ebook'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/home/pacho/evolution-data-server-2.30.1/addressbook/tests/ebook'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory `/home/pacho/evolution-data-server-2.30.1/addressbook/tests'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/pacho/evolution-data-server-2.30.1/addressbook'
make: *** [check-recursive] Error 1

Thanks for solving this
Comment 1 Matthew Barnes 2010-06-20 17:56:57 UTC
Worked fine when I distchecked evolution-data-server before releasing 2.30.2.  Ran the tests several times to be sure, with this bug in mind.

Note when running these tests you should make sure you're running the newly built D-Bus calendar and addressbook services and your distro-provided D-Bus services, which are probably older.

Closing this bug as obsolete.
Comment 2 Matthew Barnes 2010-06-20 17:57:50 UTC
Correction: ...and -NOT- your distro-provided D-Bus services...
Comment 3 Pacho Ramos 2010-06-20 19:23:49 UTC
But, shouldn't test suite link to just compiled files instead of older ones? Otherwise, this will always fail when running tests before installing the files to be tested before
Comment 4 Matthew Barnes 2010-06-20 19:36:19 UTC
It's not a question of linking, it's a question of which binaries are providing the D-Bus service being tested.
Comment 5 Pacho Ramos 2010-06-20 19:47:00 UTC
Isn't there any way to  make tests use new dbus service before installing files in real filesystem then? Thanks for the info :-)
Comment 6 Matthew Barnes 2010-06-20 20:33:18 UTC
Run the services manually from the source tree:

Terminal 1:
(kill running e-addressbook-factory process)
$ .../evolution-data-server/addressbook/libedata-book/e-addressbook-factory

Terminal 2:
(kill running e-calendar-factory process)
$ .../evolution-data-server/calendar/libedata-cal/e-calendar-factory
Comment 7 Pacho Ramos 2010-06-21 15:37:04 UTC
And, why "make check" doesn't run that tests in that way instead of what is doing currently? I think that the sense of running tests is to check if binaries that will be installed work ok before really installing it and, for that, test need to use services from new binaries instead of old ones (this would also benefit us a lot at Gentoo ;-))