Repository navigation
Feature Request: mark tests flaky on FIPS #14746
Copy link
Copy link
Closed
Labels
cryptoIssues and PRs related to the crypto subsystem.Issues and PRs related to the crypto subsystem.feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.pythonPRs and issues that require attention from people who are familiar with Python.PRs and issues that require attention from people who are familiar with Python.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.toolsIssues and PRs related to the tools directory.Issues and PRs related to the tools directory.wipIssues and PRs that are still a work in progress.Issues and PRs that are still a work in progress.
Description
Activity
- addedfeature requestIssues requesting new Node.js features.Issues requesting new Node.js features.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.toolsIssues and PRs related to the tools directory.Issues and PRs related to the tools directory.
on Aug 10, 2017 - addedcryptoIssues and PRs related to the crypto subsystem.Issues and PRs related to the crypto subsystem.
on Aug 10, 2017 - addedpythonPRs and issues that require attention from people who are familiar with Python.PRs and issues that require attention from people who are familiar with Python.
on Aug 10, 2017 If the buildbots were to set a NODE_BUILDBOT_TYPE environment variable, you could do this:
env = { # ... 'type': os.getenv('NODE_BUILDBOT_TYPE', 'default'), }
Would that work?
Well for the fips check you could just do
node -p process.versions.openssl.includes('fips'). That would work in local builds as well.I was thinking more about how to structure the
envvariable in python.@komawar please go ahead and open a PR. That is always best.
- addedwipIssues and PRs that are still a work in progress.Issues and PRs that are still a work in progress.
on Oct 10, 2017 - added 2 commits that reference this issue
on Dec 19, 2017 - added a commit that references this issue
on Jul 27, 2026
Metadata
Metadata
Assignees
Labels
cryptoIssues and PRs related to the crypto subsystem.Issues and PRs related to the crypto subsystem.feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.pythonPRs and issues that require attention from people who are familiar with Python.PRs and issues that require attention from people who are familiar with Python.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.toolsIssues and PRs related to the tools directory.Issues and PRs related to the tools directory.wipIssues and PRs that are still a work in progress.Issues and PRs that are still a work in progress.
See 8fae1e6#commitcomment-23583689
Currently
tools/test.pyonly compares againstenv, which is defined asWhere mode is release/debug, system is OS, and arch is ARCH.
We'd need to also have an option for FIPS, I guess that should be in
env. Maybe atype? Type could bedefault,fips, orsharedlib(if we end up building a shared library as well we might want asharedlibtype).cc/ @Trott @bajtos