Skip to content

Conversation

@tbhagwat16
Copy link

Test case gets failed if the testing function name is too long.

Description

I have faced an issue when I have imported NewDockerCluster for creating vault client. My testing function name was too long [more than 64 characters] So I was getting below error.

TODO only if you're a HashiCorp employee

  • Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch.
    • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
  • Jira: If this change has an associated Jira, it's referenced either in the PR description, commit message, or branch name.
  • RFC: If this change has an associated RFC, please link it in the description.

PCI review checklist

  • I have documented a clear reason for, and description of, the change I am making.
  • If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
  • If applicable, I've documented the impact of any changes to security controls.

Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

Test case gets failed if the testing function name is too long.
@tbhagwat16 tbhagwat16 requested a review from a team as a code owner February 10, 2026 03:39
@vercel
Copy link

vercel bot commented Feb 10, 2026

@tbhagwat16 is attempting to deploy a commit to the HashiCorp Team on Vercel.

A member of the Team first needs to authorize it.

@hashicorp-cla-app
Copy link

hashicorp-cla-app bot commented Feb 10, 2026

CLA assistant check
All committers have signed the CLA.

@hashicorp-cla-app
Copy link

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

Have you signed the CLA already but the status is still pending? Recheck it.

@heatherezell heatherezell added bug Used to indicate a potential bug test labels Feb 10, 2026
@heatherezell
Copy link
Contributor

Hello! Thanks for this submission. Please review and sign the CLA as well. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Used to indicate a potential bug test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants