Skip to content

Conversation

robsdedude
Copy link
Member

@robsdedude robsdedude commented Aug 1, 2023

The CI has been failing too often recently because of changes in pip and
dependencies. Those failures were mostly irrelevant warning that we turned into
errors for better visibility. However, so far there was never any action we
needed to take other than muting that warning on or the other way.

Therefore, this commit changes it so that all pip installation calls are run
without treating warnings as error.

Backport of #947

The CI has been failing too often recently because of changes in pip and
dependencies. Those failures were mostly irrelevant warning that we turned into
errors for better visibility. However, so far there was never any action we
needed to take other than muting that warning on or the other way.

Therefore, this commit changes it so that all pip installation calls are run
without treating warning as error.
Copy link
Contributor

@bigmontz bigmontz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💯

@robsdedude robsdedude changed the title Reduce scope of pip warnings as errors [4.4] Reduce scope of pip warnings as errors Aug 2, 2023
@robsdedude robsdedude merged commit 307349e into neo4j:4.4 Aug 2, 2023
@robsdedude robsdedude deleted the fix-pip-warning-4.4 branch August 2, 2023 08:38
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