[ 
https://issues.apache.org/jira/browse/CASSANDRA-18133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742684#comment-17742684
 ] 

Stefan Miklosovic commented on CASSANDRA-18133:
-----------------------------------------------

I can confirm that. It fails on this

{code}
test-jvm-dtest-some:
    [mkdir] Created dir: 
/home/fermat/dev/cassandra/cassandra-instaclustr/cassandra/build/test/cassandra
    [mkdir] Created dir: 
/home/fermat/dev/cassandra/cassandra-instaclustr/cassandra/build/test/output
[junit-timeout] Testsuite: 
org.apache.cassandra.distributed.test.ByteBuddyExamplesTest-.jdk1.8
[junit-timeout] Exception in thread "main" Unable to write log file
[junit-timeout]         at 
org.apache.cassandra.CassandraXMLJUnitResultFormatter.endTestSuite(CassandraXMLJUnitResultFormatter.java:224)
[junit-timeout]         at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.fireEndTestSuite(JUnitTestRunner.java:854)
[junit-timeout]         at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:578)
[junit-timeout]         at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1197)
[junit-timeout]         at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:1042)
[junit-timeout] Caused by: java.nio.file.NoSuchFileException: 
/home/fermat/dev/cassandra/cassandra-instaclustr/cassandra/home/fermat/dev/cassandra/cassandra-instaclustr/cassandra/build/test/output/TEST-org.apache.cassandra.distributed.test.ByteBuddyExamplesTest.xml
...
{code}

If you look closer, the path is consisting of 

/home/fermat/dev/cassandra/cassandra-instaclustr/cassandra/

plus

/home/fermat/dev/cassandra/cassandra-instaclustr/cassandra/build/test/output/TEST-org.apache.cassandra.distributed.test.ByteBuddyExamplesTest.xml

There should be just the second one. I think this is just a detail and it will 
be easy to fix.

> In-tree build scripts
> ---------------------
>
>                 Key: CASSANDRA-18133
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18133
>             Project: Cassandra
>          Issue Type: Task
>          Components: CI
>            Reporter: Michael Semb Wever
>            Assignee: Michael Semb Wever
>            Priority: Normal
>             Fix For: 5.0
>
>
> Bring the artifact/deb/rpm build scripts (and associated docker images) from 
> cassandra-builds repo to the .build directory.
> -The declarative Jenkinsfile can then directly declare the artifacts jobs in 
> its pipeline. And the packaging jobs can be separated and run in parallel.- 
> EDIT: this bit has been moved to CASSANDRA-18594
> This addresses the epic's stated existing problems:
>  - difficult to pre-commit test jenkins and cassandra-build changes,
>  - CI development efforts is split between ci-cassandra and circleci, despite 
> ci-cassandra being our canonical and non-commercial CI,
>  - lacking parity of what is tested between ci-cassandra and circleci
>  - cassandra-builds as a separate repo (without release branches matching 
> in-tree) adds complexity to changing matrix values (jdks, pythons, dist)
>  - -mixture of jenkins dsl groovy, declarative and scripting pipeline.-
>  - -different pre-commit and post-commit jenkins pipelines are used.-
> In addition it addresses:
>  - -stage jobs don't always running on the same SHA as the pipeline's run,-
>  - infra issues around networking, specifically git cloning additional 
> cassandra-builds repository,
>  - -a more readable Jenkinsfile-
>  - more UX friendly build and test scripts



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to