Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-18130

Log hardware and container params during test runs to help troubleshoot intermittent failures

    XMLWordPrintableJSON

Details

    • Quality Assurance
    • Normal
    • All
    • None
    • Hide

      CI (manual paste of jenkinsfile in replay action)

      Show
      CI (manual paste of jenkinsfile in replay action)

    Description

      We’ve long had flakiness in our containerized ASF CI environment that we don’t see in circleci. The environment itself is both containerized and heterogenous, so there are differences in both the hardware environment and the software environment in which it executes. For reference, see: https://github.com/apache/cassandra-builds/blob/trunk/ASF-jenkins-agents.md#current-agents
       
      We should log a variety of hardware, container, and software environment details to help get to the bottom of where some test failures may be occurring. As we don’t have shell access to the machines it’ll be easier to have this information logged / retrieved during test runs than to try and profile each host independently.

      Attachments

        Issue Links

          Activity

            People

              mck Michael Semb Wever
              jmckenzie Josh McKenzie
              Josh McKenzie, Michael Semb Wever
              Josh McKenzie
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: