Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

False-negative on GitHub Actions

See original GitHub issue

GitHub Actions CI supports color output. But chalk use black/white output there.

Seems like we have a false-negative detection at support-color.

I am fixing the problem with FORCE_COLOR=2 right now.

Issue Analytics

State:
Created 4 years ago
Reactions:4
Comments:19 (8 by maintainers)

Top GitHub Comments

2reactions

viceicecommented, Oct 22, 2020

I think this can be closed, as it’s fixed with v7.2

1reaction

aicommented, Dec 31, 2019

Seems like we should call @chrispat here

Top Results From Across the Web

False negative status set in github #1531

We have coveralls integrated with Github Actions and are experiencing false negative results in the Github statuses that Coveralls.io sets.

Fix false negative in VariableDeclarationDistanceUsage

Issue #11335: Fix false negative in VariableDeclarationDistanceUsage ... this execution should stay on GitHub actions due to time/ memory limits in other CI....

General issue : false negative during evaluation of UseBraces ...

We're currently evaluation the usage of cQL - see baloise/open-source#245 Description of the issue While doing that (on this very basic ...

If condition are always evaluated as true when containing ...

An if condition in a step definition that includes expression syntax in condition body is always evaluated as false positive or is ignored....

Fixed the false negative in the rule ClassMemberImpliedModifier

name: "no-exception testing". on: pull_request: branches: [ master ]. jobs: # this execution should stay on GitHub actions due to time/ memory limits...