Skip to content
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

python: fix missing flake8-formatter-junit-xml dependency #10341

Merged
merged 1 commit into from
Jan 13, 2025

Conversation

emersion
Copy link
Member

In CI we use the following command:

poetry run pflake8 --config ./pyproject.toml --output-file flake8.xml --format junit-xml

Unfortunately, when flake8 doesn't recognize a predefined format, it silently interprets it as a format string. As a result the output file flake8.xml contained a single line with the raw string "junit-xml".

Example: /~https://github.com/OpenRailAssociation/osrd/actions/runs/12713432631/job/35441321986?pr=10325#step:6:3

@emersion emersion requested a review from a team as a code owner January 13, 2025 13:53
@github-actions github-actions bot added the area:railjson Work on Proposed Unified Rail Assets Data Exchange Format label Jan 13, 2025
In CI we use the following command:

    poetry run pflake8 --config ./pyproject.toml --output-file flake8.xml --format junit-xml

Unfortunately, when flake8 doesn't recognize a predefined format,
it silently interprets it as a format string. As a result the
output file flake8.xml contained a single line with the raw
string "junit-xml".

Signed-off-by: Simon Ser <contact@emersion.fr>
@emersion emersion force-pushed the emr/fix-missing-flake8-junit-xml branch from 6e072df to 8ee0426 Compare January 13, 2025 13:55
@emersion emersion added this pull request to the merge queue Jan 13, 2025
Merged via the queue into dev with commit 3b04b6c Jan 13, 2025
27 checks passed
@emersion emersion deleted the emr/fix-missing-flake8-junit-xml branch January 13, 2025 14:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:railjson Work on Proposed Unified Rail Assets Data Exchange Format
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants