I've reconfigured all the jobs to works the same as before.
I've tried to replicate the issue with Byteman but it seems everything is
working well now.
Sanne, am I missing something about the way to run the build with search?
On Thu, Aug 20, 2015 at 9:44 AM, Sanne Grinovero
wrote:
> +1 for a)
+1 for a) as many jobs use Byteman, including ORM, and on many branches.
On 20 August 2015 at 09:26, Hardy Ferentschik wrote:
> On Thu, Aug 20, 2015 at 08:48:36AM +0200, Gunnar Morling wrote:
>> Wouldn't a better approach be to either a) run the NoSQL store in
>> question on another port or b) c
On Thu, Aug 20, 2015 at 08:48:36AM +0200, Gunnar Morling wrote:
> Wouldn't a better approach be to either a) run the NoSQL store in
> question on another port or b) configure Byteman to use another port?
I guess both options work, but given that ports are anyways configurable in
the OGM build, a)
Wouldn't a better approach be to either a) run the NoSQL store in
question on another port or b) configure Byteman to use another port?
Limiting the number of nodes where certain jobs can run contradicts
our previous efforts for scaling out the CI environment and improve
build job turn around time
Hi all,
it seems that the Hibernate Search tests using Byteman are having some
conflicts with some ports used by the NoSql dbs we installed to test OGM.
For now I just set up the Search jobs to work on ci-slave-4 where I have
stopped the dbs.
Tomorrow I will try to figure out the process that ar
