You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@marmotta.apache.org by Gustavo Mora <gm...@gmail.com> on 2017/05/17 19:55:22 UTC

Setting testing environment

Hi,

I've trying to set my machine to execute all tests, so I can know if
something does not work while changing a version of Sesame or RDF4J. I set
some databases in MYSQL and postgreSQL; however, some tests are failing. I
see that Travis CI has also been failing. I changed the configuration of
Travis CI file because some tests are skipped; however, I can't change it
to make it pass all tests[1].  The problem is in KiWi Triplestore: Core, so
how can I make all tests pass? Is there any specific version that I should
use?

BTW, I am using MYSQL 5.7.6, PostgreSQL 9.3, mvn 3.3.9, OS X Capitan.


Regards,
Gustavo.

[1] https://travis-ci.org/gmora1223/marmotta

Re: Setting testing environment

Posted by Sergio Fernández <wi...@apache.org>.
On Mon, May 22, 2017 at 9:54 AM, Sergio Fernández <wi...@apache.org> wrote:
>
> Take into account that each specific KiWi database follows a convention
> (db name, credentials, etc.) you should use to run the tests.
>

I forgot to reference the convention the KiWiDatabaseRunner follows:

https://github.com/apache/marmotta/blob/develop/libraries/kiwi/kiwi-triplestore/src/test/java/org/apache/marmotta/kiwi/test/junit/KiWiDatabaseRunner.java#L47

Re: Setting testing environment

Posted by Sergio Fernández <wi...@apache.org>.
FYI, I've reported https://issues.apache.org/jira/browse/INFRA-14313

On Wed, Jun 7, 2017 at 5:48 PM, Sergio Fernández <wi...@apache.org> wrote:

> Hi Gustavo,
>
> now on the develop branch I can locally get a clean build:
>
> $ mvn clean install
> (...)
> [INFO] ------------------------------------------------------------
> ------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------
> ------------
> [INFO] Total time: 14:24 min
> [INFO] Finished at: 2017-06-07T17:39:57+02:00
> [INFO] Final Memory: 274M/4052M
> [INFO] ------------------------------------------------------------
> ------------
>
> Although some (concurrency) tests on KiWi may occasionally fail. I need to
> spend some time looking for the source of that.
>
> In addition we have to take a look to our CI tools: Jenkins is pretty
> unstable is throws weird errors, and memory issues on Travis.
>
>
> On Tue, Jun 6, 2017 at 12:21 PM, Sergio Fernández <wi...@apache.org>
> wrote:
>
>> I'll try to get a clean testsuite on develop by the end of the week.
>>
>> On Wed, May 24, 2017 at 5:45 AM, Gustavo Mora <gm...@gmail.com>
>> wrote:
>>
>>> Hi Sergio,
>>>
>>>
>>> > what specific tests are not
>>> > workung for you? Please, register jira issues with the details.
>>> >
>>> >
>>> The detailed log of the tests are here [1]. The setup in my computer is
>>> basically the same.
>>>
>>>
>>> > Take into account that each specific KiWi database follows a
>>> convention (db
>>> > name, credentials, etc.) you should use to run the tests.
>>> >
>>> >
>>> The new configuration file of Travis CI is here [2]. I think I configured
>>> the databases, so I think it should work.
>>>
>>>
>>> > You should make the best out of theCommunity Bounding Period to
>>> progress on
>>> > these things before you jump into the project development.
>>>
>>>
>>> Yes, I also started the migration process for the version of Sesame
>>> 2.8.11,
>>> so I hope for the first week of June have everything working.
>>>
>>> [1] https://travis-ci.org/gmora1223/marmotta
>>> [2]
>>> https://github.com/gmora1223/marmotta/commit/15b3165752d2e4b
>>> 0c521f5c291ea3a031336607f
>>>
>>
>>
>

Re: Setting testing environment

Posted by Sergio Fernández <wi...@apache.org>.
Hi Gustavo,

now on the develop branch I can locally get a clean build:

$ mvn clean install
(...)
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 14:24 min
[INFO] Finished at: 2017-06-07T17:39:57+02:00
[INFO] Final Memory: 274M/4052M
[INFO]
------------------------------------------------------------------------

Although some (concurrency) tests on KiWi may occasionally fail. I need to
spend some time looking for the source of that.

In addition we have to take a look to our CI tools: Jenkins is pretty
unstable is throws weird errors, and memory issues on Travis.


On Tue, Jun 6, 2017 at 12:21 PM, Sergio Fernández <wi...@apache.org> wrote:

> I'll try to get a clean testsuite on develop by the end of the week.
>
> On Wed, May 24, 2017 at 5:45 AM, Gustavo Mora <gm...@gmail.com> wrote:
>
>> Hi Sergio,
>>
>>
>> > what specific tests are not
>> > workung for you? Please, register jira issues with the details.
>> >
>> >
>> The detailed log of the tests are here [1]. The setup in my computer is
>> basically the same.
>>
>>
>> > Take into account that each specific KiWi database follows a convention
>> (db
>> > name, credentials, etc.) you should use to run the tests.
>> >
>> >
>> The new configuration file of Travis CI is here [2]. I think I configured
>> the databases, so I think it should work.
>>
>>
>> > You should make the best out of theCommunity Bounding Period to
>> progress on
>> > these things before you jump into the project development.
>>
>>
>> Yes, I also started the migration process for the version of Sesame
>> 2.8.11,
>> so I hope for the first week of June have everything working.
>>
>> [1] https://travis-ci.org/gmora1223/marmotta
>> [2]
>> https://github.com/gmora1223/marmotta/commit/15b3165752d2e4b
>> 0c521f5c291ea3a031336607f
>>
>
>

Re: Setting testing environment

Posted by Sergio Fernández <wi...@apache.org>.
I'll try to get a clean testsuite on develop by the end of the week.

On Wed, May 24, 2017 at 5:45 AM, Gustavo Mora <gm...@gmail.com> wrote:

> Hi Sergio,
>
>
> > what specific tests are not
> > workung for you? Please, register jira issues with the details.
> >
> >
> The detailed log of the tests are here [1]. The setup in my computer is
> basically the same.
>
>
> > Take into account that each specific KiWi database follows a convention
> (db
> > name, credentials, etc.) you should use to run the tests.
> >
> >
> The new configuration file of Travis CI is here [2]. I think I configured
> the databases, so I think it should work.
>
>
> > You should make the best out of theCommunity Bounding Period to progress
> on
> > these things before you jump into the project development.
>
>
> Yes, I also started the migration process for the version of Sesame 2.8.11,
> so I hope for the first week of June have everything working.
>
> [1] https://travis-ci.org/gmora1223/marmotta
> [2]
> https://github.com/gmora1223/marmotta/commit/
> 15b3165752d2e4b0c521f5c291ea3a031336607f
>

Re: Setting testing environment

Posted by Gustavo Mora <gm...@gmail.com>.
Hi Sergio,


> what specific tests are not
> workung for you? Please, register jira issues with the details.
>
>
The detailed log of the tests are here [1]. The setup in my computer is
basically the same.


> Take into account that each specific KiWi database follows a convention (db
> name, credentials, etc.) you should use to run the tests.
>
>
The new configuration file of Travis CI is here [2]. I think I configured
the databases, so I think it should work.


> You should make the best out of theCommunity Bounding Period to progress on
> these things before you jump into the project development.


Yes, I also started the migration process for the version of Sesame 2.8.11,
so I hope for the first week of June have everything working.

[1] https://travis-ci.org/gmora1223/marmotta
[2]
https://github.com/gmora1223/marmotta/commit/15b3165752d2e4b0c521f5c291ea3a031336607f

Re: Setting testing environment

Posted by Sergio Fernández <wi...@apache.org>.
Hi Gustavo,

I'm travelling with limited connectivity. Later this week I'll try to see
in whmhat shaoe our test suite actually is. what specific tests are not
workung for you? Please, register jira issues with the details.

Take into account that each specific KiWi database follows a convention (db
name, credentials, etc.) you should use to run the tests.

You should make the best out of theCommunity Bounding Period to progress on
these things before you jump into the project development.

Cheers,

On May 17, 2017 21:55, "Gustavo Mora" <gm...@gmail.com> wrote:

Hi,

I've trying to set my machine to execute all tests, so I can know if
something does not work while changing a version of Sesame or RDF4J. I set
some databases in MYSQL and postgreSQL; however, some tests are failing. I
see that Travis CI has also been failing. I changed the configuration of
Travis CI file because some tests are skipped; however, I can't change it
to make it pass all tests[1].  The problem is in KiWi Triplestore: Core, so
how can I make all tests pass? Is there any specific version that I should
use?

BTW, I am using MYSQL 5.7.6, PostgreSQL 9.3, mvn 3.3.9, OS X Capitan.


Regards,
Gustavo.

[1] https://travis-ci.org/gmora1223/marmotta