Run pytest with --color=yes to force GitHub Actions logs to have color#3330
Run pytest with --color=yes to force GitHub Actions logs to have color#3330
--color=yes to force GitHub Actions logs to have color#3330Conversation
GitHub Actions does not show colour outputs for pytest by default (pytest-dev/pytest#7443), but it can be enabled using `--color=yes` flag.
|
Can we add it directly to Line 169 in 97a6f30 |
We could do that yes. I'm just not sure how everyone's terminals works with color output. |
Maybe |
Should be auto by default already I think. It's just that |
--color=yes to force color output logs in GitHub Actions
--color=yes to force color output logs in GitHub Actions--color=yes to force GitHub Actions logs to have color
|
Ok, switched to putting |
CodSpeed Performance ReportMerging #3330 will improve performances by 38.95%Comparing Summary
Benchmarks breakdown
|
|
So much performance improvement from adding colour 🤣 Pytest log output looks colored at https://github.com/GenericMappingTools/pygmt/actions/runs/9950591916/job/27488697947?pr=3330#step:7:106 |
To fix `TypeError: ufunc 'create_collection' not supported for the input types, and the inputs could not be safely coerced to any supported types according to the casting rule ''safe''`. Xref shapely/shapely#2098 * Add --color=yes to test_no_images addopts Xref #3330

Description of proposed changes
GitHub Actions does not show colour outputs for pytest by default (pytest-dev/pytest#7443), but it can be enabled using
--color=yesflag.Enables color output for pytest on:
Fixes #
Reminders
make formatandmake checkto make sure the code follows the style guide.doc/api/index.rst.Slash Commands
You can write slash commands (
/command) in the first line of a comment to performspecific operations. Supported slash command is:
/format: automatically format and lint the code