Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test case "properties" fails #256

Closed
donpellegrino opened this issue Mar 13, 2022 · 1 comment
Closed

Test case "properties" fails #256

donpellegrino opened this issue Mar 13, 2022 · 1 comment

Comments

@donpellegrino
Copy link
Contributor

Running the "properties" test case (make check) fails with the following error:

~/src/hdt-cpp/libhdt/tests$ cat test-suite.log
===============================================
   libhdt 1.3.3: libhdt/tests/test-suite.log
===============================================

# TOTAL: 11
# PASS:  10
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: properties
================

Catch exception load: Error: The subjects must be correlative.
Error: The subjects must be correlative.
terminate called after throwing an instance of 'std::runtime_error'
  what():  Couldn't read header
FAIL properties (exit status: 134)

This error message comes from BitmapTriples.cpp:

~/src/hdt-cpp$ grep -r "The subjects must be correlative."
libhdt/src/triples/BitmapTriples.cpp:                throw std::runtime_error("Error: The subjects must be correlative.");

All three preset configurations run by the properties test case use triples.type <http://purl.org/HDT/hdt#triplesBitmap>:

        std::vector<std::string> elem = {
                "../presets/dictionaryfour.hdtcfg",
                "../presets/dictionaryliteral.hdtcfg",
                "../presets/ops.hdtcfg"};
donpellegrino pushed a commit to donpellegrino/hdt-cpp that referenced this issue Mar 13, 2022
…d by running the test suite and the failure described in rdfhdt#256.
@donpellegrino
Copy link
Contributor Author

Sorry, I discovered this was my own fault. I added a commit to the Pull Request for Issue #244 that fixes the problem. I confirmed that Pull Request and all my other Pull Requests that had the code from that branch pass the default test suite without any errors or warnings.

Getting the tests to execute required the code I did for Issue #254 as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant