Skip to content

Commit

Permalink
retry ci for skipped tests w/ recent #54 fix
Browse files Browse the repository at this point in the history
  • Loading branch information
carueda committed Oct 7, 2019
1 parent b2a0d9a commit a17a7f5
Show file tree
Hide file tree
Showing 4 changed files with 0 additions and 12 deletions.
1 change: 0 additions & 1 deletion changelog.md
Expand Up @@ -12,7 +12,6 @@
- scoping should be handled already
- no support for recursive type
(example spec would look like issue54c.spec.conf)
- skip a test for travis-ci as a class gets wrongly generated only there!

2019-09-03 - 0.9.93

Expand Down
@@ -1,4 +1,3 @@
// GenOpts: --java
root {
#@define
Shared {
Expand Down
2 changes: 0 additions & 2 deletions src/test/scala/tscfg/generators/java/JavaMainSpec.scala
Expand Up @@ -762,7 +762,6 @@ class JavaMainSpec extends Specification {
}
}

/* SKIP due to weird travis-ci issue (with the scala version, not the java one)
"issue 54 - shared config - example2" should {
"be handled" in {
val c = new JavaIssue54bCfg(ConfigFactory.parseString(
Expand All @@ -787,7 +786,6 @@ class JavaMainSpec extends Specification {
c.root.f.get(0).c.d === 2
}
}
*/

"issue 55 - valid regexes" should {
"be properly reflected" in {
Expand Down
8 changes: 0 additions & 8 deletions src/test/scala/tscfg/generators/scala/ScalaMainSpec.scala
Expand Up @@ -671,13 +671,6 @@ class ScalaMainSpec extends Specification {
}
}

// for some strange reason ScalaIssue54bCfg keeps of getting wrongly generated on travis-ci:
// [error] /home/travis/build/carueda/tscfg/src/test/scala/tscfg/example/ScalaIssue54bCfg.scala:8: not found: type Shared
// [error] e : Shared,
// [error] ^
// But this gets correctly generated locally.
// So, U guess I'll just skip it so it doesn't affect the build status on github
/*
"issue 54 - shared config - example2" should {
"be handled" in {
val c = ScalaIssue54bCfg(ConfigFactory.parseString(
Expand All @@ -702,7 +695,6 @@ class ScalaMainSpec extends Specification {
c.root.f.head.c.d === 2
}
}
*/

"issue 55 - valid regexes" should {
"be properly reflected" in {
Expand Down

0 comments on commit a17a7f5

Please sign in to comment.