Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rdf4j-dev] Error in test

I pulled develop now and did a clean install. Tests are passing for me now.

Thanks Jeen for fixing this. Hopefully we can find a permanent fix.

Håvard


On 29 Jun 2019, at 06:33, Jeen Broekstra <jeen.broekstra@xxxxxxxxx> wrote:

Alright, workaround found. Here's the current setup:

1. the compliance modules in both rdf4j and rdf4j-storage are now only executed when the maven profile 'compliance' is activated (-Pcompliance).
2. all compliance tests again rely on the latest project version of the rdf4j-server, instead of a fixed older version. This should prevent such incompatibility errors.
3. Jenkins now first builds and deploys rdf4j, rdf4j-storage, and rdf4j-tools (running unit tests, but not compliance tests). After rdf4j-tools is successfully deployed, it runs a second verification pass, which executes the compliance tests in rdf4j, rdf4j-storage, and rdf4j-tools. This setup ensures that compliance tests are always ran against the most recent snapshot build of rdf4j-server.

I call this a workaround because I don't think it's satisfactory to have to skip compliance/integration testing like this, just to avoid cyclic dependencies. What I want to achieve is a setup where the compliance tests in rdf4j and rdf4j-storage can be run without having to spin up a full rdf4j server - we should instead use tools such as Wiremock to stub/mock server responses. Not only does that solve the dependency issue, it's also cleaner from a testing responsibility perspective: we're testing the client-side behaviour after all, not if the server itself executes operations correctly (that kind of testing should actually happen in rdf4j-tools).

Jeen

On Thu, Jun 27, 2019 at 9:09 AM Jeen Broekstra <jeen.broekstra@xxxxxxxxx> wrote:
I'm getting a similar error. I think it may have to do with the fact that I tried to get the compliance tests to run with a fixed, released version of rdf4j server (2.5.0), but because the compliance tests also have a dependency on the memory sail itself, we get a classpath conflict between the memory sail included in that server, and the snapshot one, included directly.

My head hurts. I'll try and find a way around.

Fwiw in the previous setup this pain was avoided by having the build execute in stages in Jenkins: we first built all modules (and deployed them to sonatype snapshot), and then in a second pass we executed all the compliance tests (so that the compliance tests can use anything in the project, becuase it's already deployed). I removed that setup because I _thought_ I had eliminated all these pain points, but clearly I have made some mistakes here.

I may do a quick-n-dirty fix just to get a stable build for the M1, then afterwards find a neater solution.

Jeen

On Thu, Jun 27, 2019 at 4:33 AM "Håvard M. Ottestad" <hmottestad@xxxxxxxxx> wrote:
Thanks for checking Bart :)

Håvard

On 26 Jun 2019, at 20:33, Håvard M. Ottestad <hmottestad@xxxxxxxxx> wrote:

I think thats going to have to be my next step.

Håvard

On 26 Jun 2019, at 20:27, Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx> wrote:

Hi,

and mvn clean install also works for me on Debian, 64-bit openJDK 1.8.0_212.
Build success for both rdf4j and rdf4j-storage...

Have you tried building from a fresh git clone ? Maybe that helps...

Bart

From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> on behalf of Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx>
Sent: Wednesday, June 26, 2019 4:02:42 PM
To: rdf4j developer discussions
Subject: Re: [rdf4j-dev] Error in test
 
Hi Håvard,

Building and mvn clean install on MS-Windows with AdoptOpenJDK 8 (1.8.0_191) seemed to have  worked
(though I have found a platform / separator specific bug in a lucene test)

I'll check on linux this evening.


Best regards

Bart
-----Original Message-----
From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> On Behalf Of Håvard Ottestad
Sent: dinsdag 25 juni 2019 20:43
To: rdf4j developer discussions <rdf4j-dev@xxxxxxxxxxx>
Subject: [rdf4j-dev] Error in test

Hi,

I’m getting an error on develop in rdf4j-storage in SPARQLServiceEvaluationTest.

Error: org.eclipse.rdf4j.repository.RepositoryException: Handler dispatch failed; nested exception is java.lang.AbstractMethodError: Method org/eclipse/rdf4j/sail/memory/MemoryStoreConnection.pendingRemovals()Z is abstract

I have tried to do mvn clean, delete the rdf4j directory in .m2 and done a new install. Still fails. It does not fail on jenkins.

Jenkins thinks everything is fine … but I don’t trust jenkins.

Could someone else
 - checkout develop on rdf4j-storage
 - mvn clean
 - rm -r  ~/.m2/repository/org/eclipse/rdf4j/
 - mvn clean install

Håvard
_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/rdf4j-dev
_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/rdf4j-dev
_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/rdf4j-dev
_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/rdf4j-dev
_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/rdf4j-dev


Back to the top