Oipo opened a new pull request #261:
URL: https://github.com/apache/celix/pull/261


   @abroekhuis @pnoltes this test currently cannot add the pubsub publisher 
dependencies because it thinks it's in a system bundle. How do I get the test 
to start the publisher properly? The test gives the following output:
   
   ```
   
/home/oipo-unencrypted/Programming/celix-pstm/cmake-build-debug/bundles/pubsub/test/pstm_deadlock_test/pstm_deadlock_testd
   Running main() from 
/home/oipo-unencrypted/Programming/celix-pstm/cmake-build-debug/_deps/googletest-src/googletest/src/gtest_main.cc
   [==========] Running 1 test from 1 test suite.
   [----------] Global test environment set-up.
   [----------] 1 test from DeadlockTestSuite
   [ RUN      ] DeadlockTestSuite.test
   [2020-06-25T16:50:44] [info] [celix_psa_discovery] [PSA_ZMQ] Using 127.0.0.1 
for service annunciation
   [2020-06-25T16:50:44] [info] [celix_psa_discovery] [PSA_ZMQ] Using base till 
max port: 5501 till 6000
   [2020-06-25T16:50:44] [info] [celix_framework] [framework_start:581] Celix 
framework started
   
   -> Cannot open 
/home/oipo-unencrypted/Programming/celix-pstm/cmake-build-debug/bundles/pubsub/test/pubsub_deadlock_sut-Debug.zip
 or 
/home/oipo-unencrypted/Programming/celix-pstm/cmake-build-debug/bundles/pubsub/test/pubsub_deadlock_sut-Debug.zip.zip
   Creating DependencyCmp
   [2020-06-25T16:50:44] [error] [celix_framework] [bundleRevision_create:69] 
File I/O exception: "Failed to create revision"
   [2020-06-25T16:50:44] [error] [celix_framework] 
[bundleArchive_createRevisionFromLocation:606] File I/O exception: "Could not 
create revision 
[location=/home/oipo-unencrypted/Programming/celix-pstm/cmake-build-debug/bundles/pubsub/test/pubsub_deadlock_sut-Debug.zip,inputFile=(null)]"
   [2020-06-25T16:50:44] [error] [celix_framework] 
[bundleArchive_reviseInternal:579] File I/O exception: "Could not revise bundle 
archive"
   [2020-06-25T16:50:44] [error] [celix_framework] [bundleArchive_revise:556] 
File I/O exception: "Could not revise bundle archive"
   [2020-06-25T16:50:44] [error] [celix_framework] [bundleArchive_create:137] 
File I/O exception: "Could not create archive"
   [2020-06-25T16:50:44] [error] [celix_framework] 
[bundleCache_createArchive:193] File I/O exception: "Failed to create archive"
   [2020-06-25T16:50:44] [error] [celix_framework] [fw_installBundle2:776] 
Bundle exception: Could not install bundle
   [Error] Missing mandatory entry for endpoint. Missing key is 
'pubsub.endpoint.uuid'
   [Error] Missing mandatory entry for endpoint. Missing key is 
'pubsub.framework.uuid'
   [Error] Missing mandatory entry for endpoint. Missing key is 
'pubsub.endpoint.type'
   [Error] Missing mandatory entry for endpoint. Missing key is 
'pubsub.topic.name'
   [2020-06-25T16:50:50] [warning] [celix_psa_serializer_json] [json 
serializer] File config.properties does not contain a fully qualified name for 
the parser
   
   [2020-06-25T16:50:50] [warning] [celix_psa_serializer_json] [json 
serializer] Cannot open descriptor file: ''
   
   Destroying DependencyCmp
   Creating DependencyCmp
   [2020-06-25T16:50:54] [info] [celix_framework] [framework_stop:644] Celix 
framework stopped
   [2020-06-25T16:50:56] [warning] [celix_framework] 
[serviceRegistry_logWarningServiceReferenceUsageCount:601] Service Reference 
destroyed with usage count is 1, expected 0. Look for missing 
bundleContext_ungetService calls.
   [2020-06-25T16:50:56] [warning] [celix_framework] 
[serviceRegistry_logWarningServiceReferenceUsageCount:620] Previous Dangling 
service reference warnings caused by bundle 'Framework', for service 'unknown', 
provided by bundle 'unknown'
   [2020-06-25T16:50:56] [error] [celix_framework] 
[serviceRegistry_destroy:113] 1 dangling service listeners
   
   Signal: SIGSTOP (Stopped (signal))
   
   Process finished with exit code 1
   ```


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to