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

Define CLICOLOR_FORCE=1 env var in CI runs #631

Merged
merged 2 commits into from
Nov 26, 2022

Conversation

MisterDA
Copy link
Contributor

This env var is supported by some tools to force them to emit ANSI escape sequences corresponding to colors even if they detect that they're not running in tty, which is th case for CI jobs.

It is going to be supported in Dune 3.6.0, and perhaps other compilers and build systems.

@MisterDA
Copy link
Contributor Author

@smorimoto how do I rebuild the action to make the CI succeed?

@smorimoto
Copy link
Member

Could you add a changelog entry?

This env var is supported by some tools to force them to emit ANSI
escape sequences corresponding to colors even if they detect that
they're not running in tty, which is th case for CI jobs.

It is going to be supported in Dune 3.6.0, and perhaps other compilers
and build systems.

Signed-off-by: Antonin Décimo <[email protected]>
@MisterDA
Copy link
Contributor Author

MisterDA commented Nov 8, 2022

I've applied your suggestion, added a changelog entry, and rebuild the action.

@MisterDA
Copy link
Contributor Author

Dune 3.6 was just released with support for this feature!

Signed-off-by: Antonin Décimo <[email protected]>
@smorimoto smorimoto merged commit fc27600 into ocaml:master Nov 26, 2022
@MisterDA MisterDA deleted the define-CLICOLOR_FORCE-true branch November 26, 2022 22:52
emillon added a commit to emillon/dune that referenced this pull request Nov 30, 2022
Since ocaml#6340 we're considering `CLICOLOR_FORCE` to determine whether
stderr supports color. However this changes behavior observable from the
test suite, so `CLICOLOR_FORCE=1 make test` fails (this is tracked as
ocaml#6607).

The issue is that ocaml/setup-ocaml#631, this variable is set in the CI
environment. So we disable it until the situation is fixed (and this
variable does not have observable changes anymore).

Signed-off-by: Etienne Millon <[email protected]>
emillon added a commit to emillon/dune that referenced this pull request Nov 30, 2022
Since ocaml#6340 we're considering `CLICOLOR_FORCE` to determine whether
stderr supports color. However this changes behavior observable from the
test suite, so `CLICOLOR_FORCE=1 make test` fails (this is tracked as
ocaml#6607).

The issue is that ocaml/setup-ocaml#631, this variable is set in the CI
environment. So we disable it until the situation is fixed (and this
variable does not have observable changes anymore).

Signed-off-by: Etienne Millon <[email protected]>
emillon added a commit to emillon/dune that referenced this pull request Nov 30, 2022
Since ocaml#6340 we're considering `CLICOLOR_FORCE` to determine whether
stderr supports color. However this changes behavior observable from the
test suite, so `CLICOLOR_FORCE=1 make test` fails (this is tracked as
ocaml#6607).

The issue is that ocaml/setup-ocaml#631, this variable is set in the CI
environment. So we disable it until the situation is fixed (and this
variable does not have observable changes anymore).

Signed-off-by: Etienne Millon <[email protected]>
emillon added a commit to emillon/dune that referenced this pull request Nov 30, 2022
Since ocaml#6340 we're considering `CLICOLOR_FORCE` to determine whether
stderr supports color. However this changes behavior observable from the
test suite, so `CLICOLOR_FORCE=1 make test` fails (this is tracked as
ocaml#6607).

The issue is that ocaml/setup-ocaml#631, this variable is set in the CI
environment. So we disable it until the situation is fixed (and this
variable does not have observable changes anymore).

Signed-off-by: Etienne Millon <[email protected]>
emillon added a commit to emillon/dune that referenced this pull request Nov 30, 2022
Since ocaml#6340 we're considering `CLICOLOR_FORCE` to determine whether
stderr supports color. However this changes behavior observable from the
test suite, so `CLICOLOR_FORCE=1 make test` fails (this is tracked as
ocaml#6607).

The issue is that ocaml/setup-ocaml#631, this variable is set in the CI
environment. So we disable it until the situation is fixed (and this
variable does not have observable changes anymore).

Signed-off-by: Etienne Millon <[email protected]>
emillon added a commit to ocaml/dune that referenced this pull request Nov 30, 2022
* Set CLICOLOR_FORCE=0

Since #6340 we're considering `CLICOLOR_FORCE` to determine whether
stderr supports color. However this changes behavior observable from the
test suite, so `CLICOLOR_FORCE=1 make test` fails (this is tracked as
#6607).

The issue is that ocaml/setup-ocaml#631, this variable is set in the CI
environment. So we disable it until the situation is fixed (and this
variable does not have observable changes anymore).

Signed-off-by: Etienne Millon <[email protected]>
moyodiallo pushed a commit to moyodiallo/dune that referenced this pull request Dec 2, 2022
* Set CLICOLOR_FORCE=0

Since ocaml#6340 we're considering `CLICOLOR_FORCE` to determine whether
stderr supports color. However this changes behavior observable from the
test suite, so `CLICOLOR_FORCE=1 make test` fails (this is tracked as
ocaml#6607).

The issue is that ocaml/setup-ocaml#631, this variable is set in the CI
environment. So we disable it until the situation is fixed (and this
variable does not have observable changes anymore).

Signed-off-by: Etienne Millon <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants