cli reporter not working for failing test when using retry() in scenario level

[AramSol]

What are you trying to achieve?

we try to get cli report about failing scenario [its only work without retry()]

What do you get instead?

as soon as i add the retry Option, no cli report will be logged on console for failing scenarios.

Details

• CodeceptJS version:3.3.0
• NodeJS Version:16.14.2
• Operating System:windows 10
• webdriverio

config

const settings = {
    window: {
        width: 1920,
        height: 1080
    }
};

exports.config = {
    tests: "./*/**/*.js",
    helpers: {
        WebDriver: {
            url: "http://localhost:8070",
            browser: "chrome",
            windowSize: `${settings.window.width}x${settings.window.height}`,
            waitForTimeout: 20000,
            disableScreenshots: true,
            desiredCapabilities: {
                chromeOptions: {
                    binary: require("chromium").path,
                    args: [
                        "--headless",
                        "--lang=en",
                        "--log-level=3",
                        "--disable-gpu",
                        "--disable-dev-shm-usage",
                        "--no-sandbox",
                        `--window-size=${settings.window.width},${settings.window.height}`
                    ]
                }
            }
        },
        myHelper: {
            require: "./helper.js",
        },
    },
    include: {
        I: "./custom-steps.js"
    },
    multiple: {
        parallel: {
            chunks: 10
        }
    },
    output: "../../../.output-ui-tests"
};

[AramSol]

hi @kobenguyent ,

The problem regarding the reporting of failed tests in the scenario has been resolved. However, when attempting to execute the UI test with the "--multiple" parameter to run all UI tests, the steps of the failed test are not displayed as previously noted in this reported issue

[kobenguyent]

May you try this retry configuration

https://codecept.io/basics/#retry-configuration

[AramSol]

@kobenguyent , we still face the same issue.
we use --multiple parameter