-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci(*): Run flaky tests with --verbose and use ci profile #3063
Conversation
Also fix building of tests to use --profile ci which is used to run the tests. The test run did not trigger a re-build. So mosly likely the profile is not encoded in the build artifacts and we were running tests on the normal dev profile rather than the ci profile.
Documentation for this PR has been generated and is available at: https://n0-computer.github.io/iroh/pr/3063/docs/iroh/ Last updated: 2024-12-19T16:26:53Z |
Seems like this is a nextest profile, not a cargo profile. Goodness.
.github/workflows/tests.yaml
Outdated
@@ -111,7 +111,7 @@ jobs: | |||
- name: run tests | |||
run: | | |||
mkdir -p output | |||
cargo nextest run --workspace ${{ env.FEATURES }} --lib --bins --tests --profile ci --run-ignored ${{ inputs.flaky && 'all' || 'default' }} --no-fail-fast --message-format ${{ inputs.flaky && 'libtest-json' || 'human' }} > output/${{ matrix.name }}_${{ matrix.features }}_${{ matrix.rust }}.json | |||
cargo nextest run --workspace ${{ env.FEATURES }} --lib --bins --tests --profile ci --run-ignored ${{ inputs.flaky && 'all' || 'default' }} ${{ inputs.flaky && '--verbose' }} --no-fail-fast --message-format ${{ inputs.flaky && 'libtest-json' || 'human' }} > output/${{ matrix.name }}_${{ matrix.features }}_${{ matrix.rust }}.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fyi in the test suite this renders as "false" for the CLI command, think you need to add || ''
so it returns an empty string when evaluating to false
. Which I think is the reason the tests fail.
Description
Also fix building of tests to use --profile ci which is used to run
the tests. The test run did not trigger a re-build. So mosly likely
the profile is not encoded in the build artifacts and we were running
tests on the normal dev profile rather than the ci profile.
Breaking Changes
Notes & open questions
Change checklist