[ https://issues.apache.org/jira/browse/CASSANDRA-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165590#comment-17165590 ]
Berenguer Blasi edited comment on CASSANDRA-15925 at 7/27/20, 10:10 AM: ------------------------------------------------------------------------ [~mck] I was looking into this and saw some problems. Let me know if I am holding the wrong end of the stick though: - Take run [#220|https://ci-cassandra.apache.org/job/Cassandra-devbranch/220/] reporting 3 failures - On it's console out you can see it runs [Cassandra-devbranch-test #198|https://ci-cassandra.apache.org/job/Cassandra-devbranch/220/console] with [2 failures|https://ci-cassandra.apache.org/job/Cassandra-devbranch-test/198/] - org.apache.cassandra.transport.frame.checksum.ChecksummingTransformerTest.corruptionCausesFailure is missing from the top #220 failures report and timestamps and [out|https://ci-cassandra.apache.org/job/Cassandra-devbranch-test/198/testReport/junit/org.apache.cassandra.cql3.validation.operations/TTLTest/testCapNoWarnExpirationOverflowPolicy/] from testCapNoWarnExpirationOverflowPolicy failure doesn't match that of the matching #220 top failures [report|https://ci-cassandra.apache.org/job/Cassandra-devbranch/220/testReport/junit/org.apache.cassandra.cql3.validation.operations/TTLTest/testCapNoWarnExpirationOverflowPolicy/] If out, timestamps and failing tests list don't match I'd bet there is some jenkins funnies going on somewhere? was (Author: bereng): [~mck] I was looking into this and saw some problems. Let me know if I am holding the wrong end of the stick though: - Take run [#220|https://ci-cassandra.apache.org/job/Cassandra-devbranch/220/] reporting 3 failures - On it's console out you can see it runs [Cassandra-devbranch-test #198|https://ci-cassandra.apache.org/job/Cassandra-devbranch/220/console] with [2 failures|https://ci-cassandra.apache.org/job/Cassandra-devbranch-test/198/] - org.apache.cassandra.transport.frame.checksum.ChecksummingTransformerTest.corruptionCausesFailure is missing from the top #220 failures repot and timestamps and [out|https://ci-cassandra.apache.org/job/Cassandra-devbranch-test/198/testReport/junit/org.apache.cassandra.cql3.validation.operations/TTLTest/testCapNoWarnExpirationOverflowPolicy/] from that failure doesn't match that of the matching #220 top failures [report|https://ci-cassandra.apache.org/job/Cassandra-devbranch/220/testReport/junit/org.apache.cassandra.cql3.validation.operations/TTLTest/testCapNoWarnExpirationOverflowPolicy/] If out, timestamps and failing tests list don't match I'd bet there is some jenkins funnies going on somewhere? > Jenkins pipeline can copy wrong test report artefacts from stage builds > ----------------------------------------------------------------------- > > Key: CASSANDRA-15925 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15925 > Project: Cassandra > Issue Type: Bug > Components: CI > Reporter: Michael Semb Wever > Assignee: Michael Semb Wever > Priority: Normal > Fix For: 4.0-rc > > > Spotted in > https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/196/console > Looks like copyArtifact will need to be specific to a build. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org