Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-19099

WildFly image behave tests results clarification

XMLWordPrintable

      Not sure how one should interpret behave tests, e.g. https://github.com/wildfly/wildfly-s2i/actions/runs/7798267568/job/21266571019

      They are run on PRs, and always green. But when I look into logs > "Behave tests" there is a lot of ERROR log messages. Although they look like standard INFO level messages.

      I am not sure how one should find how many tests were run and how many passed and failed.

            [WFLY-19099] WildFly image behave tests results clarification

            Martin Choma added a comment -

            Thanks, now readability of failing test is much better.

            Martin Choma added a comment - Thanks, now readability of failing test is much better.

            Jean Francois Denise added a comment -

            mchoma@redhat.com , here they are. https://github.com/wildfly/wildfly-s2i/actions/runs/8848558048/job/24298619984

            Jean Francois Denise added a comment - mchoma@redhat.com , here they are. https://github.com/wildfly/wildfly-s2i/actions/runs/8848558048/job/24298619984

            Martin Choma added a comment - - edited

            Could I see some failure in new state in action?

            I see some CI failure here https://pipelinesghubeus23.actions.githubusercontent.com/plnsiPjDpn7iucrqzg6CNjMnzxSu1aFntUipsorDAqC03pApr4/_apis/pipelines/1/runs/2375/signedlogcontent/4?urlExpires=2024-05-29T12%3A28%3A52.3236928Z&urlSigningMethod=HMACV1&urlSignature=g0Tv4CZhu4r%2BY4JtMO220hVXU3gAEZ9nBc1XNhk7haM%3D but those logs are insane long.

            Martin Choma added a comment - - edited Could I see some failure in new state in action? I see some CI failure here https://pipelinesghubeus23.actions.githubusercontent.com/plnsiPjDpn7iucrqzg6CNjMnzxSu1aFntUipsorDAqC03pApr4/_apis/pipelines/1/runs/2375/signedlogcontent/4?urlExpires=2024-05-29T12%3A28%3A52.3236928Z&urlSigningMethod=HMACV1&urlSignature=g0Tv4CZhu4r%2BY4JtMO220hVXU3gAEZ9nBc1XNhk7haM%3D but those logs are insane long.

            Jean Francois Denise added a comment -

            mchoma@redhat.com ,

            Some weeks ago we have reached a resource consumption limit (no more space for logs and created docker images during test) making the workflow to be stuck.

            The execution of tests has been refactored to allow for fine grain execution allowing to purge generated docker images and collect logs.

            I have added documentation on how the behave tests are run and on how logs should be retrieved and interpreted.

             

            Jean Francois Denise added a comment - mchoma@redhat.com , Some weeks ago we have reached a resource consumption limit (no more space for logs and created docker images during test) making the workflow to be stuck. The execution of tests has been refactored to allow for fine grain execution allowing to purge generated docker images and collect logs. I have added documentation on how the behave tests are run and on how logs should be retrieved and interpreted.  

              jdenise@redhat.com Jean Francois Denise
              mchoma@redhat.com Martin Choma
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: