Verify Troubleshooting

The Verify command may return one of the error messages listed below. See detailed explanations and suggested remedies.
OS is not supported
Incompatible Operating System
Incompatible operating system, the current OS is: {SYS_PLATFORM}, the required OS are: macOS, Linux or Windows.
Redefine does not support the machine's operating system.
You can find the list of supported OS here: Supported Operating Systems​
Python or Pytest is unsupported
Python version not found
No python versions found.
This can be an issue due to one of the following:
Python is not configured in the path environment variable
Redefine was run outside of a virtual environment. In this case, make sure to run from the virtual environment shell or use your favorite virtual environment command line tool to run redefine via Python, i.e - poetry run python -m redefine <cmd>
Python is not installed on the machine
Python Version Problem
All python versions found {versions} are not supported - The minimal supported Python version is 3.6
Redefine supports only python version 3.6 and above, please make sure to install a python version higher or equal to 3.6
Python Installation Problem
Pytest is not installed or cannot be imported, the supported versions are 5.4.0 or higher.
This can be an issue due to one of the following:
Redefine was run outside of a virtual environment. In this case, make sure to run from the virtual environment shell or use your favorite virtual environment command line tool to run redefine via Python, i.e - poetry run python -m redefine <cmd>
Pytest is not installed in the current environment. Redefine pytest integration requires pytest to run. Please make sure you are installing pytest in your ci (via pip install pytest or other methods such as requirements.txt file
Incompatible Pytest Version
The current Pytest version is {pytest_version} - the supported versions are 5.4.0 or higher.
Redefine supports pytest version 5.4.0 and above, please make sure to install pytest with a version higher then 5.4.0
Pip Installation Problem
Pip is not installed or cannot be imported
pip is not installed, please make sure you have pip installed in your environment (by running python3 -m pip or python -m pip)
Pip Version Problem
Incompatible Pip version. The current Pip version is {pip_version} - The supported versions are 9.0.1 or higher.
pip version is incompatible, Redefine supports pip version higher than 9.0.1, please make sure to upgrade your pip, by running pip install -U pip
Javascript or Cypress is unsupported
Node version not found
No node versions found
This can be an issue due to one of the following:
Node is not installed on the machine
Node is not configured in the path environment variable
npm/npx not installed
npm is not installed or cannot be imported / npx is not installed or cannot be imported
npm/npx is not installed, please make sure you have the package manager installed in your environment (by running sudo apt install npm)
Incompatible Cypress Version
Incompatible cypress version. The current Cypress version is {cypress_version} - the supported versions are 10.11.0 or higher.
Redefine supports pytest version 10.11.0  and above, please make sure to install pytest with a version higher than 10.11.0.
Cypress is not installed or cannot be imported.
Cypress is not installed or cannot be imported.
Cypress is not installed, please run npm install cypress --save-dev.
​
Redefine System Requirements Issue
Package Version Problem
Package {customer_pkg.name} version is {customer_pkg.version} - the minimal supported version is {supported_pkg.version}
Redefine supports the package that is in the message only from the written version and above. If it is possible please upgrade the version to {} and above. If it is problematic please contact us for support.
CI Configuration Problem
CI platform-specific environment variables are missing - Make sure to you are running Redefine in your CI platform and it has access to the CI's environment variables
Redefine relies on environment variables delivered from the CI platform. Depending on your CI architecture, this may not be automatically available, for example -
Running docker container in your CI - you will have to pass the environment variables from your CI platform to your docker image - see
Running redefine in a process with clean environment variables - make sure to pass the parent's environment variables to the process running redefine"
Please make sure your CI is supported Supported Technologies​
Problem Locating Branch
No merge base found between any {source} and {stable_branch_str} - Make sure the branches have a common ancestor
For Redefine to perform test prediction, it needs to perform git operations based on the changes you've performed in your branch. If no merge base is found between your branch and the stable branch, that could be due to the following:
Your branch hasn't originated from the stable branch (Ex. Branched out of main when the stable is defined to develop)
Your branch is too far from the stable branch - Currently, redefine supports a depth range of up to 100. This is usually due to running redefine on a separate long-running branch without adapting the stable branch configuration (i.e, running redefine on dev itself when a stable branch is configured for main)
Pytest Plugin Problem
Redefine pytest plugin requires {requirement.name} ({requirement.specifier}), upgrading the current version: {version}
Redefine requires a higher versioned package, and will upgrade it to version {version} when Redefine will be installed.
Package Problem
Package {plugin} is not officially supported
Currently, the package is not officially supported or tested in Redefine. It is not expected to cause issues, but we recommend being aware of it and contacting us at [email protected] in case of any problem.
Stable Branch Not Configured
Stable branch is not configured, can't verify git - Make sure to configure stable branch using Redefine config set stable_branch=<your_branch>
You did not configure your Redefine stable branch, please make sure to configure it by running Redefine config set stable_branch=<your_stable_branch>qu
For more information see Broken link​
Git Verification Problem
Can't detect branch from CI environment variables, cannot verify git!
Redefine relies on environment variables delivered from the CI platform. Depending on your CI architecture, this may not be automatically available, for example -
Running docker container in your CI - you will have to pass the environment variables from your CI platform to your docker image - see
Running redefine in a process with clean environment variables - make sure to pass the parent's environment variables to the process running redefine"
Please make sure your CI is supported Supported Technologies​
Git Remote Name Invalid
Git remote name is invalid
Please make sure your git remote is valid (https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes)
Missing Parameter
{param} (env name: {env}): Missing!
A param named {param_name} is missing and could not be auto-detected.
for example: source_branch, source_commit, git repo, job_name, pipeline_name, ci_run_id.
make sure you are running on a valid CI platform.
Git configuration issue
Git Directory Problem
Current directory ({current_directory}) is not a git repository.
The current directory is not a git repository, please make sure you run the verify command inside your git repository.
Commit-Related Problem
{commit} is not a valid commit
Please make sure the checked-out commit is a valid commit in your git history
Problem Locating Commit
Can't find commit {commit} - Make sure it exists in the repository
Please make sure the checked-out commit is a valid commit in your git history
Commit History Problem
Commit {commit} is shallow - Make sure the commit's branch has sufficient history
For Redefine to perform test prediction, it needs to perform git operations that require sufficient git history. If your commit is shallow (depth=1) or doesn't have sufficient depth (<100) redefine will not be able to perform quality test prediction.
To fix the issue, please make sure git clone is not shallow. if --depth is used, it has to be >100"
Commit Depth Problem
Can't get depth of commit {commit} - Make sure it exists in the repository
For Redefine to perform test prediction, it needs to perform git operations that require sufficient git history. If your commit is shallow (depth=1) or doesn't have sufficient depth (<100) redefine will not be able to perform quality test prediction.
To fix the issue, please make sure git clone is not shallow. if --depth is used, it has to be >100"
Git Remote Branches Problem
Can't find remote branches for repository {git_repo} - Make sure the repository is valid and has remote
Please make sure your current machine has permission to the remote repository, and you can fetch the remote repository.
Problem Fetching Branch
Branch {branch} is {exc.args[0]}, failed fetch - Make sure the branch has sufficient historyquo
Please make sure your current machine has permission to the remote repository, and you can fetch the remote branch history.
Stable Branch Missing
Stable branch {exc.args[0]} is missing - Make sure it exists in the repository
Please make sure your current machine has permission to the remote repository, and you can fetch the configured stable branch
Remote Branch Problem
Can't find remote branches for repository {git_repo} - Make sure the repository is valid and has remoteso
Please make sure your current machine has permission to the remote repository, and you can fetch the configured stable branch.
Problem Fetching Stable Branch
Stable branch {exc.args[0]} is {exc.args[1]}, failed fetch - Make sure the branch has sufficient history
Please make sure your current machine has permission to the remote repository, and you can fetch the configured stable branch.
Stable Branch Depth Problem
Can't get depth of stable branch - Make sure it exists in the repository
Please make sure your current machine has permission to the remote repository, and the configured stable branch exists.
Merge Base Problem
No merge base found between any {source} and {stable_branch_str} - Make sure the branches have a common ancestor
Please make sure your configured source (source_commit/source_branch) is a branch/commit which has a common ancestor with the configured stable branch.
Multiple Stable Branches Defined
More than one stable branch specified in config - Please specify only one by running Redefine config set stable_branch=<branch_name>"
Redefine does not support multiple stable branches, please make sure you have only 1 configured stable branch
Multiple Remote Origins
More than one remote found
Redefine uses the git remote to verify that it performs git operations on the latest version of a branch. By having more than one git remote, redefine will not be able to determine which remote to work with. Please contact us at [email protected] for solutions.
Coralogix Configuration Issue
Found the python package coralogix-logger is installed, if you encounter any issues, make sure to set Redefine config set pytest_coralogix_disabled=true
Redefine detected the package coralogix-logger is installed, this can cause conflicts with your current logger, if you are running one if you do face those issues, please make sure to run Redefine config set pytest_coralogix_disabled=true
Git Remote Problem
Unable to find remote
Redefine was unable to find a configured git remote, please make sure you have a valid configured git remote (see https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes)
Redefine authorization problem
Authorization Variable Problem
REDEFINE_AUTH environment variable not set - Make sure to export it correctly, Make sure to set it with the API_KEY you were provided by Redefine.dev If you haven't, please contact us at [email protected]
Redefine requires a REDEFINE_AUTH env to be exported for authentication.
The required format for the variable is: <client_id>::<client_secret>
for secrets storing best practices see GitHub Actions | GitLab CI | Jenkins | CircleCI | TeamCity​
If you haven’t received Redefine credentials, contact us at https://www.redefine.dev/demo.
Authorization Variable Improperly Formatted
REDEFINE_AUTH environment variable is not in the format client_id::client_secret
Redefine requires a REDEFINE_AUTH env to be exported with the format: <client_id>::<client_secret>, please make sure to export it in the correct format, or contact support if you don't know what is your Redefine auth
Authentication Generation Problem
Failed to generate authentication token, please contact Redefine support at [email protected]
If Redefine fails to authenticate for an unknown reason, contact Redefine support
Server connection problem
Server Connection Problem
Unable to connect to Redefine server - Make sure you have access to Redefine.dev and its sub-domains, and outgoing rule for port 443/50500
Redefine uses ports 443/50500 to perform gRPC access to the Redefine Cloud. If this access is blocked, Redefine will not be able to operate. Please make sure the access isn't blocked by a firewall or other means.
Last modified 6d ago