Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-710

Separated per-test and per-container log files.

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Unresolved
    • Major
    • None
    • 1.0.0.CR7
    • Base Implementation
    • None

    Description

      What's the best way to separate server and client log messages?

      Currently, log messages can either go to the console, and Arquillian "forwards" them to Surefire, which causes mixed client and server messages.
      Or, messages can go to the server log file as usually. Which ends up in tens of megabytes long log files.

      So, either arq can log to an arbitrary file, or Surefire could have support for multiple logs.
      The later won't happen any soon I guess Arq just forwards anything to surefire.

      So, let's say I want to have separated log files in surefire-reports dir:

      • org.jboss.FooBarTestCase-client,
      • org.jboss.FooBarTestCase-server1,
      • org.jboss.FooBarTestCase-server2, ...

      This feature is quite important for large testsuites which produce tons of log messages,
      and even more for multi-node tests.

      Attachments

        Issue Links

          blocks

          Sub-task - The sub-task of the issue WFLY-601 TS: Logging issues (tracking)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-576 Testsuite tasks (tracking)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is blocked by

          Sub-task - The sub-task of the issue ARQ-722 Set ${arq.currentTest} and ${arq.server} for AS7 instances (using management).

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Feature Request - Feature requests from customers and/or users LOGMGR-36 FileHandler which rolls the file when a system property changes.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open
          is incorporated by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. AS7-4067 AS7 Testsuite post-7.1.1 ideas (tracking)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              ozizka_jira Ondrej Zizka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: