Skip to content

Running configure twice will most likely cause test failures #23352

Closed
@danbev

Description

@danbev
  • Version: v11.0.0-pre
  • Platform: Darwin MacBook-Pro-3.local 17.7.0 Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64
  • Subsystem: build

Currently when running configure without any options and running the test suite will pass successfully. If one the runs configure again but this time with an option, for example --debug-nghttp2 the will be test failures. The same goes for other options like --without-ssl.

I think this might be related to 6dd4a07. I've reverted this locally to test and that does resolve the issue but wanted to see if this could perhaps be fixed without reverting first.

Metadata

Metadata

Assignees

No one assigned

    Labels

    buildIssues and PRs related to build files or the CI.regressionIssues related to regressions.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions