You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Robbie Gemmell (Jira)" <ji...@apache.org> on 2024/06/26 17:17:00 UTC
[jira] [Comment Edited] (ARTEMIS-4832) direct test output to file by default
[ https://issues.apache.org/jira/browse/ARTEMIS-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860204#comment-17860204 ]
Robbie Gemmell edited comment on ARTEMIS-4832 at 6/26/24 5:16 PM:
------------------------------------------------------------------
{quote}
commit 68155867b6947a8fb41ba11b14f6bac79e8f3c20
Author: Robbie Gemmell
Date: Fri Jun 21 14:05:06 2024 +0100
ARTEMIS-4832: direct test output to file, make results more visible
Archive test logs upon GHA CI job failure to allow inspection.
Output to console can be enabled on request with e.g:
mvn test -Dmaven.test.redirectTestOutputToFile=false
{quote}
https://github.com/apache/activemq-artemis/commit/68155867b6947a8fb41ba11b14f6bac79e8f3c20
was (Author: gemmellr):
{quote}
commit 68155867b6947a8fb41ba11b14f6bac79e8f3c20
Author: Robbie Gemmell
Date: Fri Jun 21 14:05:06 2024 +0100
ARTEMIS-4832: direct test output to file, make results more visible
Archive test logs upon GHA CI job failure to allow inspection.
Output to console can be enabled on request with e.g:
mvn test -Dmaven.test.redirectTestOutputToFile=false
{quote}
> direct test output to file by default
> -------------------------------------
>
> Key: ARTEMIS-4832
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4832
> Project: ActiveMQ Artemis
> Issue Type: Task
> Components: Tests
> Affects Versions: 2.35.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Major
> Fix For: 2.36.0
>
>
> Currently the artemis build prints all the test stdout to the console. This can make it difficult to see individual results as they occur or look back either while the suite is running or afterwards (previously even more of an issue prior to ARTEMIS-4831).
> Many of the tests generate _a lot_ of output. As a result, even the small subset used in the PR checks is already enough to overflow the limit GitHub allows to occur before truncating all outpu{{monospaced text}}t and requiring downloading the job logs, which you need to wait until after the run has finished to see. Redirecting the output will allow seeing specific results more easily, and also relative progress of the job prior to completion. The PR subset is but a small fraction of the total, so e.g when running the wider test suite locally with lots more integration tests this is actually even worse as the console will typically exceed its buffer so you simply cant see most results at all without e.g generating the surefire report later.
> Surefire already has a dedicated property to control this behaviour, easily configurable via the pom (already there) or the CLI: {_}maven.test.redirectTestOutputToFile{_}. Set this true such that the test output is directed to file by default, leaving results succinctly visible on the console. Archive the surefire log output whenever the GHA CI job fails so the test output can still be inspected for a period if needed.
> Anyone that does specifically wish to have the test output still sent to the console can get this on request by configuring surefire when running, e.g:
> {noformat}
> mvn test -Dmaven.test.redirectTestOutputToFile=false
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact