[
https://issues.apache.org/jira/browse/CASSANDRA-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17093858#comment-17093858
]
David Capwell commented on CASSANDRA-15729:
-------------------------------------------
Cassandra Changes
*
https://github.com/thelastpickle/cassandra/commit/ed0a7e7e2f3e2a67825b8d560ee9ffbb60983336#diff-90e40e02845884b66e9006b25250ea5cR49.
Why comment out the ant jar command?
Build Changes
*
https://github.com/apache/cassandra-builds/compare/master...thelastpickle:mck/jenkins-test-report-format#diff-ed43728c5b4a5f326dc69a04e9cf57edR9
should we install this outside the build? feels wrong to me to install
packages as part of a build.
*
https://github.com/apache/cassandra-builds/compare/master...thelastpickle:mck/jenkins-test-report-format#diff-ed43728c5b4a5f326dc69a04e9cf57edR27
dead block?
*
https://github.com/apache/cassandra-builds/compare/master...thelastpickle:mck/jenkins-test-report-format#diff-a76ac7fa36779199fe7e4fe917ac41bcR233
will unified file be accessible cross builds, or only able to view the
workspace for the last build? in the linked build I don't have access to look
at the file (if it was generated)
For the build-scripts/cassandra-test-report.xsl file, I need to go learn that
in order to review it... right now I can only black box review by trying to
look at the output.
cassandra-test-report.txt is limited to 900KB, which leaves just under 100KB
for
https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/trunk_15729#diff-9b83915ce4a53a5b3cc01b9f39d6a984R357-R367.
ran a hacky test to show that 100KB is roughly 5000 times "this is just a
test", so if we assume all test have a name of 4x that, that leaves 1,250 space
for changes, so this looks fine to me. I assume though Jenkins won't know the
email was rejected since I normally expect that to be a reply back email...
> Jenkins Test Results Report in plaintext for ASF ML
> ---------------------------------------------------
>
> Key: CASSANDRA-15729
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15729
> Project: Cassandra
> Issue Type: Task
> Components: Build, CI
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Normal
> Labels: Jenkins
> Fix For: 4.0-beta
>
>
> The Jenkins pipeline builds now aggregate all test reports.
> For example:
> - https://ci-cassandra.apache.org/job/Cassandra-trunk/68/testReport/
> -
> https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-trunk/detail/Cassandra-trunk/68/tests
> But Jenkins can only keep a limited amount of build history, so those links
> are not permanent, can't be used as references, and don't help for bisecting
> and blame on regressions (and flakey tests) over a longer period of time.
> The builds@ ML can provide a permanent record of test results.
> This was first brought up in these two threads:
> -
> https://lists.apache.org/thread.html/re8122e4fdd8629e7fbca2abf27d72054b3bc0e3690ece8b8e66f618b%40%3Cdev.cassandra.apache.org%3E
> -
> https://lists.apache.org/thread.html/ra5f6aeea89546825fe7ccc4a80898c62f8ed57decabf709d81d9c720%40%3Cdev.cassandra.apache.org%3E
> An example plaintext report, to demonstrate feasibility, is available here:
> https://lists.apache.org/thread.html/r80d13f7af706bf8dfbf2387fab46004c1fbd3917b7bc339c49e69aa8%40%3Cbuilds.cassandra.apache.org%3E
> Hurdles:
> - the ASF mailing lists won't accept html, attachments, or any message body
> over 1MB.
> - packages are used as a differentiator in the final aggregated report. The
> cqlsh and dtests currently don't specify it. It needs to be added as a
> "dot-separated" prefix to the testsuite and testcase name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
