You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@groovy.apache.org by pa...@apache.org on 2020/09/18 02:57:51 UTC
[groovy] branch master updated: explore whether using a Short
instead of String for improves metaclass test robustness for CI
This is an automated email from the ASF dual-hosted git repository.
paulk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/groovy.git
The following commit(s) were added to refs/heads/master by this push:
new c6653eb explore whether using a Short instead of String for improves metaclass test robustness for CI
c6653eb is described below
commit c6653eb49346061518f5026675f0a164b4a1c60e
Author: Paul King <pa...@asert.com.au>
AuthorDate: Fri Sep 18 12:57:34 2020 +1000
explore whether using a Short instead of String for improves metaclass test robustness for CI
---
src/test/groovy/lang/MetaClassPropertyTest.groovy | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/test/groovy/lang/MetaClassPropertyTest.groovy b/src/test/groovy/lang/MetaClassPropertyTest.groovy
index fa5b2df..89ec1e8 100644
--- a/src/test/groovy/lang/MetaClassPropertyTest.groovy
+++ b/src/test/groovy/lang/MetaClassPropertyTest.groovy
@@ -23,7 +23,7 @@ import groovy.test.GroovyTestCase
class MetaClassPropertyTest extends GroovyTestCase {
void testForJavaClass() {
- checkMetaClassBehavior("hello world")
+ checkMetaClassBehavior(Short.valueOf("1"))
}
void testForGroovyClass() {