Byteman needs to open a listening network socket in the agent, so that
the test fixture can connect to it and control the agent to upload the
instrumentation rules (the default is 9091).
If this is your local workstation, maybe you have the port taken by a
different server?
If it's a CI server, I
org.hibernate.test.annotations.xml.ejb3.NonExistentOrmVersionTest STANDARD_OUT
14:19:50,895 INFO SchemaExport:343 - HHH000227: Running hbm2ddl schema
export
14:19:50,896 DEBUG SchemaExport:353 - Import file not found: /import.sql
14:19:50,896 INFO SchemaExport:405 - HHH000230: Schema
Hi,
> The jar seems to be correctly uploaded:
> https://repository.jboss.org/nexus/content/groups/public-jboss/org/infinispan/infinispan-core/5.1.2.FINAL/
>
> But I get your same error when running tests:
>
> * What went wrong:
> Could not resolve all dependencies for configuration
> ':hibernate
On 22 March 2012 09:31, Hardy Ferentschik wrote:
>
> On Mar 20, 2012, at 1:27 PM, Steve Ebersole wrote:
>
>> I am curious Strong why you explicitly handle classes.jar (apparently
>> for MacOS) when it is already handled?
>
> Right, I think we should get away w/ just
>
> toolsJar = file("${S
On Mar 20, 2012, at 1:27 PM, Steve Ebersole wrote:
> I am curious Strong why you explicitly handle classes.jar (apparently
> for MacOS) when it is already handled?
Right, I think we should get away w/ just
toolsJar = file("${System.getProperty('java.home')}/../lib/tools.jar")
At leas
4.1.1
-Original Message-
From: hibernate-dev-boun...@lists.jboss.org
[mailto:hibernate-dev-boun...@lists.jboss.org] On Behalf Of Steve
Ebersole
Sent: Tuesday, March 20, 2012 6:27 AM
To: hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] byteman
You'll have to give me more
Strong passed that to the Gradle file() method, which handles the file
separators I believe. files() does the same, calling file() for each
thing in whatever collection it is given.
I am curious Strong why you explicitly handle classes.jar (apparently
for MacOS) when it is already handled?
O
You'll have to give me more info. All tests pass here for me aside from
the one originally discussed on this thread:
> Building > :hibernate-core:matrixUnitTest > Resolving dependencies
':hibernate:hibernate-core:matrixUnitTest
Test org.hibernate.test.annotations.xml.ejb3.OrmVersion1SupportedT
On Mar 20, 2012, at 11:02, Sanne Grinovero wrote:
> On 20 March 2012 08:42, Strong Liu wrote:
>>
>> On Mar 20, 2012, at 4:32 PM, Sanne Grinovero wrote:
>>
>> Nice, but I guess that won't work on Windows?
>>
>>
>> the file path separator?
>
> Yes I'm thinking about the file separator, but I
On 20 March 2012 08:42, Strong Liu wrote:
>
> On Mar 20, 2012, at 4:32 PM, Sanne Grinovero wrote:
>
> Nice, but I guess that won't work on Windows?
>
>
> the file path separator?
Yes I'm thinking about the file separator, but I didn't try it.. maybe
it's fine because of some groovy magic.
For the
On Mar 20, 2012, at 4:32 PM, Sanne Grinovero wrote:
> Nice, but I guess that won't work on Windows?
the file path separator?
>
> On 20 March 2012 06:33, Hardy Ferentschik wrote:
>>
>> On Mar 20, 2012, at 6:15 AM, Strong Liu wrote:
>>
>>> fixed
>>> https://github.com/hibernate/hibernate-or
Nice, but I guess that won't work on Windows?
On 20 March 2012 06:33, Hardy Ferentschik wrote:
>
> On Mar 20, 2012, at 6:15 AM, Strong Liu wrote:
>
>> fixed
>> https://github.com/hibernate/hibernate-orm/commit/749f7c1eb5206ab456db08bb901befa39ac5c11e
>
> Sweet :-) Cool that you figured it out.
>
On Mar 20, 2012, at 6:15 AM, Strong Liu wrote:
> fixed
> https://github.com/hibernate/hibernate-orm/commit/749f7c1eb5206ab456db08bb901befa39ac5c11e
Sweet :-) Cool that you figured it out.
--Hardy
___
hibernate-dev mailing list
hibernate-dev@lists.j
On Mar 20, 2012, at 1:15 PM, Strong Liu wrote:
> fixed
> https://github.com/hibernate/hibernate-orm/commit/749f7c1eb5206ab456db08bb901befa39ac5c11e
FYI http://issues.gradle.org/browse/GRADLE-1477
>
> and I'm seeing two test failures, probably caused by HHH-7020 / HHH-7090
>
> :hibernate-cor
fixed
https://github.com/hibernate/hibernate-orm/commit/749f7c1eb5206ab456db08bb901befa39ac5c11e
and I'm seeing two test failures, probably caused by HHH-7020 / HHH-7090
:hibernate-core:testTest
org.hibernate.test.connections.CurrentSessionConnectionTest FAILED
Test org.hibernate.test.connectio
On Mar 19, 2012, at 8:10 PM, Sanne Grinovero wrote:
> I guess who tested this was on OsX, and you are not.
I wonder who that could be :-) I was not aware of this side of using Byteman
and
as Sanna says, it works just fine for me.
> With Hibernate Search (Maven) we have it setup like:
> https:
Hi Steve,
I guess who tested this was on OsX, and you are not.
Byteman requires the tools.jar from the JDK on it's classpath to be
able to load the agent dynamically (i.e. not require the agent to be
defined on the JVM boot parameters).
The tool.jar happens to be on the classpath by default when r
Ugh, I see... Gradle seems to now store repo caches by Gradle version
under ~/caches/{gradleVersion}. Anyway, the test still fails for me
locally...
On Mon 19 Mar 2012 01:49:04 PM CDT, Steve Ebersole wrote:
> Actually, not sure its really working in Gradle side either., I get
> one failure af
Actually, not sure its really working in Gradle side either., I get
one failure after pull, which is the (afaict) single test using byteman:
Test org.hibernate.test.annotations.xml.ejb3.OrmVersion1SupportedTest
FAILED
java.lang.NoClassDefFoundError:
com/sun/tools/attach/AgentInitializationExc
Having some problems getting the recently added byteman stuff to work in
terms of IntelliJ. Basically it comes down to I cannot find the byteman
jars anywhere. I run the compileTestJava task and see gradle/ivy
downloading the jars. But afterwards I cannot find them in
~/.gradle/cache. I als
Ok,
enabling it as HSEARCH-644 so we can keep the change separate from HSEARCH-625.
Sanne
2010/12/9 Hardy Ferentschik :
> +1 for Byteman
>
> Anything which makes testing easier sounds good and I've heard before that
> Byteman makes
> it easier to test border/exception cases.
>
> --Hardy
>
> On Th
+1 for Byteman
Anything which makes testing easier sounds good and I've heard before that
Byteman makes
it easier to test border/exception cases.
--Hardy
On Thu, 09 Dec 2010 10:45:04 +0100, Sanne Grinovero
wrote:
> Hello,
> In the quest to write a proper unit test for HSEARCH-625 this nigh
Hello,
In the quest to write a proper unit test for HSEARCH-625 this night
I've introduced Byteman
in the testsuite of Hibernate Search.
I must say I'm impressed and love the tool, the fix is ready and the
test rocks, it empowered me to
write code with confidence to catch the IOException errors in
23 matches
Mail list logo
