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 684387 - rygel-http-request_http-get.vala:97: Invalid Request
rygel-http-request_http-get.vala:97: Invalid Request
Status: RESOLVED FIXED
Product: rygel
Classification: Applications
Component: general
0.14.x
Other Linux
: Normal blocker
: ---
Assigned To: rygel-maint
rygel-maint
Depends on:
Blocks:
 
 
Reported: 2012-09-19 17:11 UTC by Robert Bruce Park
Modified: 2012-09-25 13:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Robert Bruce Park 2012-09-19 17:11:35 UTC
Hi, we are trying to build Rygel 0.14.3 for Ubuntu quantal and we are getting a test failure in http-get which is blocking the build.

So far, I have tried using git bisect to identify where this failure was introduced, and I am actually getting this failure as far back as 0.14.0, which we had previously built successfully, so I suspect that this failure is caused by some other dependency, rather than in rygel itself. However I don't actually know enough about rygel to identify what the underlying issue might be. 

Does this error message mean anything to any Rygel people?

Thanks.




make  check-TESTS
make[4]: Entering directory `/build/buildd/rygel-0.14.3/tests'
PASS: rygel-http-item-uri-test
PASS: rygel-http-response-test
PASS: rygel-http-byte-seek-test
PASS: rygel-http-time-seek-test

(process:32063): Rygel-WARNING **: rygel-http-request_http-get.vala:97: Invalid Request

(process:32063): Rygel-WARNING **: rygel-http-request_http-get.vala:97: Interactive mode not supported for 'VideoItem'
**
Rygel:ERROR:/build/buildd/rygel-0.14.3/tests/rygel-http-get-test.vala:224:rygel_http_get_test_handle_client_message_co: assertion failed: (_data_->_tmp10_ == ((guint) _data_->_tmp12_))
/bin/bash: line 5: 32063 Aborted                 ${dir}$tst
FAIL: rygel-http-get-test
PASS: rygel-album-art-spec-test

(process:32071): Rygel-WARNING **: rygel-http-request_http-post.vala:97: Pushing data to non-empty item 'TestItem' not allowed

(process:32071): Rygel-WARNING **: rygel-http-request_http-post.vala:97: No writable URI for NullItem available

(process:32071): Rygel-WARNING **: rygel-http-post.vala:126: Item VanishingItem disappeared, stop waiting for it
PASS: rygel-http-post-test
PASS: rygel-searchable-container-test

(process:32078): Rygel-WARNING **: Failed to create item under '(null)': No such object

(process:32078): Rygel-WARNING **: Failed to create item under '0': Comments not allowed in XML

(process:32078): Rygel-WARNING **: Failed to create item under '0': 'Elements' argument missing.

(process:32078): Rygel-WARNING **: Failed to create item under '0': Bad metadata

(process:32078): Rygel-WARNING **: Failed to create item under '0': No items in DIDL-Lite from client: '<?xml version="1.0" encoding="UTF-8"?>
<DIDL-Lite xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns="urn:schemas-upnp-org:metadata-1-0/DIDL-Lite/" xmlns:upnp="urn:schemas-upnp-org:metadata-1-0/upnp/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:schemas-upnp-org:metadata-1-0/DIDL-Lite/         http://www.upnp.org/schemas/av/didl-lite-v2-20060531.xsd       urn:schemas-upnp-org:metadata-1-0/upnp/         http://www.upnp.org/schemas/av/upnp-v2-20060531.xsd">  </DIDL-Lite>
'

(process:32078): Rygel-WARNING **: Failed to create item under '0': Bad metadata

(process:32078): Rygel-WARNING **: Failed to create item under '0': Cannot create restricted item

(process:32078): Rygel-WARNING **: Failed to create item under '0': @id must be set to "" in CreateItem

(process:32078): Rygel-WARNING **: Failed to create item under '0': @id must be set to "" in CreateItem

(process:32078): Rygel-WARNING **: Failed to create item under '0': dc:title must be set in CreateItem

(process:32078): Rygel-WARNING **: Failed to create item under '0': Invalid upnp:class given 

(process:32078): Rygel-WARNING **: Failed to create item under '0': Invalid upnp:class given 

(process:32078): Rygel-WARNING **: Failed to create item under '0': Invalid upnp:class given 

(process:32078): Rygel-WARNING **: Failed to create item under '0': No such object

(process:32078): Rygel-WARNING **: Failed to create item under '0': No such object

(process:32078): Rygel-WARNING **: Failed to create item under '0': Object creation in (null) not allowed

(process:32078): Rygel-WARNING **: Failed to create item under '0': Object creation in (null) not allowed

(process:32078): Rygel-WARNING **: Failed to create item under '0': Creating of objects with class object.item.audioItem is not supported in (null)

(process:32078): Rygel-WARNING **: Failed to create item under 'DLNA.ORG_AnyContainer': No such object

(process:32078): Rygel-WARNING **: Failed to create item under 'DLNA.ORG_AnyContainer': 'object.item.audioItem' UPnP class unsupported
PASS: rygel-item-creator-test
======================================================================
1 of 9 tests failed
Please report to http://bugzilla.gnome.org/enter_bug.cgi?product=Rygel
======================================================================
make[4]: *** [check-TESTS] Error 1
make[4]: Leaving directory `/build/buildd/rygel-0.14.3/tests'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/build/buildd/rygel-0.14.3/tests'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory `/build/buildd/rygel-0.14.3'
make[1]: *** [check] Error 2
make[1]: Leaving directory `/build/buildd/rygel-0.14.3'
dh_auto_test: make -j1 check returned exit code 2
make: *** [build-arch] Error 29
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
******************************************************************************
Build finished at 20120919-0926
FAILED [dpkg-buildpackage died]
******************************************************************************
Finished at 20120919-0926
Comment 1 Jens Georg 2012-09-20 15:06:33 UTC
I think this is related to bug 680496.
Comment 2 Jens Georg 2012-09-25 13:38:45 UTC
This is fixed in the upcoming 0.16 release.