镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

Feature Request: mark tests flaky on FIPS #14746

Description

@gibfahn

See 8fae1e6#commitcomment-23583689

Currently tools/test.py only compares against env, which is defined as

        env = {
          'mode': mode,
          'system': utils.GuessOS(),
          'arch': vmArch,
        }

Where 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 a type? Type could be default, fips, or sharedlib (if we end up building a shared library as well we might want a sharedlib type).

cc/ @Trott @bajtos

Activity

  1. added
    feature requestIssues requesting new Node.js features.
    testIssues and PRs related to Node.js core tests and test infrastructure.
    toolsIssues and PRs related to the tools directory.
    on Aug 10, 2017
  2. added
    cryptoIssues and PRs related to the crypto subsystem.
    on Aug 10, 2017
  3. added
    pythonPRs and issues that require attention from people who are familiar with Python.
    on Aug 10, 2017
  4. bnoordhuis commented on Sep 21, 2017

    @bnoordhuis
    Member

    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?

  5. gibfahn commented on Sep 22, 2017

    @gibfahn
    MemberAuthor

    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 env variable in python.

  6. komawar commented on Oct 10, 2017

    @komawar
    Contributor

    Hello @gibfahn and others,

    I had a small conversation with @Trott offline and I think I understand this issue. I would like to help out with this one if you all are okay with it.

  7. BridgeAR commented on Oct 10, 2017

    @BridgeAR
    Member

    @komawar please go ahead and open a PR. That is always best.

  8. added
    wipIssues and PRs that are still a work in progress.
    on Oct 10, 2017
  9. self-assigned this
    on Oct 10, 2017
  10. removed their assignment
    on Oct 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    cryptoIssues and PRs related to the crypto subsystem.feature requestIssues requesting new Node.js features.pythonPRs and issues that require attention from people who are familiar with Python.testIssues and PRs related to Node.js core tests and test infrastructure.toolsIssues and PRs related to the tools directory.wipIssues and PRs that are still a work in progress.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions