2022-09-06 19:14:07 -04:00
|
|
|
|
// Copyright 2015 The Crashpad Authors
|
2015-03-09 15:13:13 -04:00
|
|
|
|
//
|
|
|
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
|
// you may not use this file except in compliance with the License.
|
|
|
|
|
// You may obtain a copy of the License at
|
|
|
|
|
//
|
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
|
//
|
|
|
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
|
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
|
// See the License for the specific language governing permissions and
|
|
|
|
|
// limitations under the License.
|
|
|
|
|
|
2017-04-03 13:53:11 -04:00
|
|
|
|
#include "test/test_paths.h"
|
2015-03-09 15:13:13 -04:00
|
|
|
|
|
|
|
|
|
#include <stdlib.h>
|
|
|
|
|
#include <sys/stat.h>
|
|
|
|
|
|
2023-11-06 13:34:26 -08:00
|
|
|
|
#include "base/check.h"
|
2015-03-09 15:13:13 -04:00
|
|
|
|
#include "base/logging.h"
|
|
|
|
|
#include "build/build_config.h"
|
2017-04-03 13:53:11 -04:00
|
|
|
|
#include "util/misc/paths.h"
|
2015-03-09 15:13:13 -04:00
|
|
|
|
|
|
|
|
|
namespace crashpad {
|
|
|
|
|
namespace test {
|
|
|
|
|
|
|
|
|
|
namespace {
|
|
|
|
|
|
|
|
|
|
bool IsTestDataRoot(const base::FilePath& candidate) {
|
|
|
|
|
const base::FilePath marker_path =
|
test: Move util/test to its own top-level directory, test.
After 9e79ea1da719, it no longer makes sense for crashpad_util_test_lib
to “hide” in util/util_test.gyp. All of util/test is moved to its own
top-level directory, test, which all other test code is allowed to
depend on. test, too, is allowed to depend on all other non-test code.
In a future change, when crashpad_util_test_lib gains a dependency on
crashpad_client, it won’t look so weird for something in util (even
though it’s in util/test) to depend on something in client, because the
thing that needs to depend on client will live in test, not util.
BUG=crashpad:33
R=scottmg@chromium.org
Review URL: https://codereview.chromium.org/1051533002
2015-03-31 17:44:14 -04:00
|
|
|
|
candidate.Append(FILE_PATH_LITERAL("test"))
|
2017-04-03 13:53:11 -04:00
|
|
|
|
.Append(FILE_PATH_LITERAL("test_paths_test_data_root.txt"));
|
2015-03-09 15:13:13 -04:00
|
|
|
|
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#if !BUILDFLAG(IS_WIN)
|
2015-03-09 15:13:13 -04:00
|
|
|
|
struct stat stat_buf;
|
|
|
|
|
int rv = stat(marker_path.value().c_str(), &stat_buf);
|
|
|
|
|
#else
|
|
|
|
|
struct _stat stat_buf;
|
|
|
|
|
int rv = _wstat(marker_path.value().c_str(), &stat_buf);
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
return rv == 0;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
base::FilePath TestDataRootInternal() {
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#if BUILDFLAG(IS_FUCHSIA)
|
2019-02-21 12:06:55 -08:00
|
|
|
|
base::FilePath asset_path("/pkg/data");
|
2017-12-05 10:52:44 -08:00
|
|
|
|
if (!IsTestDataRoot(asset_path)) {
|
2020-04-17 10:37:15 -04:00
|
|
|
|
LOG(WARNING) << "test data root seems invalid, continuing anyway";
|
2017-12-05 10:52:44 -08:00
|
|
|
|
}
|
|
|
|
|
return asset_path;
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#else // BUILDFLAG(IS_FUCHSIA)
|
|
|
|
|
#if !BUILDFLAG(IS_WIN)
|
2015-03-09 15:13:13 -04:00
|
|
|
|
const char* environment_value = getenv("CRASHPAD_TEST_DATA_ROOT");
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#else // BUILDFLAG(IS_WIN)
|
2015-03-09 15:13:13 -04:00
|
|
|
|
const wchar_t* environment_value = _wgetenv(L"CRASHPAD_TEST_DATA_ROOT");
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
if (environment_value) {
|
|
|
|
|
// It was specified explicitly, so use it even if it seems incorrect.
|
|
|
|
|
if (!IsTestDataRoot(base::FilePath(environment_value))) {
|
|
|
|
|
LOG(WARNING) << "CRASHPAD_TEST_DATA_ROOT seems invalid, honoring anyway";
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return base::FilePath(environment_value);
|
|
|
|
|
}
|
|
|
|
|
|
2017-04-03 13:53:11 -04:00
|
|
|
|
base::FilePath executable_path;
|
|
|
|
|
if (Paths::Executable(&executable_path)) {
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#if BUILDFLAG(IS_IOS) || BUILDFLAG(IS_ANDROID)
|
2020-04-17 10:37:15 -04:00
|
|
|
|
// On Android and iOS, test data is in a crashpad_test_data directory
|
|
|
|
|
// adjacent to the main executable. On iOS, this refers to the main
|
|
|
|
|
// executable file inside the .app bundle, so crashpad_test_data is also
|
|
|
|
|
// inside the bundle.
|
2020-03-23 13:26:03 -07:00
|
|
|
|
base::FilePath candidate = executable_path.DirName()
|
|
|
|
|
.Append("crashpad_test_data");
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#else // BUILDFLAG(IS_IOS) || BUILDFLAG(IS_ANDRID)
|
2020-04-17 10:37:15 -04:00
|
|
|
|
// In a standalone build, the test executable is usually at
|
|
|
|
|
// out/{Debug,Release} relative to the Crashpad root.
|
2017-04-03 13:53:11 -04:00
|
|
|
|
base::FilePath candidate =
|
|
|
|
|
base::FilePath(executable_path.DirName()
|
|
|
|
|
.Append(base::FilePath::kParentDirectory)
|
|
|
|
|
.Append(base::FilePath::kParentDirectory));
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#endif // BUILDFLAG(IS_IOS) || BUILDFLAG(IS_ANDROID)
|
2017-04-03 13:53:11 -04:00
|
|
|
|
if (IsTestDataRoot(candidate)) {
|
|
|
|
|
return candidate;
|
|
|
|
|
}
|
2015-03-09 15:13:13 -04:00
|
|
|
|
|
2017-04-03 13:53:11 -04:00
|
|
|
|
// In an in-Chromium build, the test executable is usually at
|
|
|
|
|
// out/{Debug,Release} relative to the Chromium root, and the Crashpad root
|
|
|
|
|
// is at third_party/crashpad/crashpad relative to the Chromium root.
|
|
|
|
|
candidate = candidate.Append(FILE_PATH_LITERAL("third_party"))
|
|
|
|
|
.Append(FILE_PATH_LITERAL("crashpad"))
|
|
|
|
|
.Append(FILE_PATH_LITERAL("crashpad"));
|
|
|
|
|
if (IsTestDataRoot(candidate)) {
|
|
|
|
|
return candidate;
|
|
|
|
|
}
|
2015-03-09 15:13:13 -04:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// If nothing else worked, use the current directory, issuing a warning if it
|
|
|
|
|
// doesn’t seem right.
|
|
|
|
|
if (!IsTestDataRoot(base::FilePath(base::FilePath::kCurrentDirectory))) {
|
|
|
|
|
LOG(WARNING) << "could not locate a valid test data root";
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return base::FilePath(base::FilePath::kCurrentDirectory);
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#endif // BUILDFLAG(IS_FUCHSIA)
|
2015-03-09 15:13:13 -04:00
|
|
|
|
}
|
|
|
|
|
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#if BUILDFLAG(IS_WIN) && defined(ARCH_CPU_64_BITS)
|
2017-11-01 10:37:01 -04:00
|
|
|
|
|
|
|
|
|
// Returns the pathname of a directory containing 32-bit test build output.
|
|
|
|
|
//
|
|
|
|
|
// It would be better for this to be named 32BitOutputDirectory(), but that’s
|
|
|
|
|
// not a legal name.
|
|
|
|
|
base::FilePath Output32BitDirectory() {
|
|
|
|
|
const wchar_t* environment_value = _wgetenv(L"CRASHPAD_TEST_32_BIT_OUTPUT");
|
|
|
|
|
if (!environment_value) {
|
|
|
|
|
return base::FilePath();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return base::FilePath(environment_value);
|
|
|
|
|
}
|
|
|
|
|
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#endif // BUILDFLAG(IS_WIN) && defined(ARCH_CPU_64_BITS)
|
2017-11-01 10:37:01 -04:00
|
|
|
|
|
2015-03-09 15:13:13 -04:00
|
|
|
|
} // namespace
|
|
|
|
|
|
|
|
|
|
// static
|
2017-04-03 13:53:11 -04:00
|
|
|
|
base::FilePath TestPaths::Executable() {
|
|
|
|
|
base::FilePath executable_path;
|
|
|
|
|
CHECK(Paths::Executable(&executable_path));
|
fuchsia: Work around lack of packaging in Fuchsia tree build
Packaged test running seems to be a ways off, but with a bit of path
fiddling in test_paths.cc we can actually use the paths where the tests
are copied, so do that instead to get all the tests re-enabled. The
setup in BUILD.gn should be mostly-useful once packaging is working as
all helper/data files will need to specified there anyway.
Also, attempted fix to flaky behaviour in
ProcessReaderFuchsia.ChildThreads exposed because the tests are now
being run. zx_object_wait_many() waits on *any* of the objects, not
*all* of them. Derp!
And finally, for the same test, work around some unintuitive behaviour
in zx_task_suspend(), in particular that the thread will not be
suspended for the purpose of reading registers right away, but instead
only "sometime later", which appears in pratice to be after the next
context switch. Have ScopedTaskSuspend block for a while to try to
ensure the registers become readble, and if they don't, at least fail
noisily at that point.
Bug: crashpad:196
Change-Id: I01fb3590ede96301c941c2a88eba47fdbfe74ea7
Reviewed-on: https://chromium-review.googlesource.com/1053797
Reviewed-by: Joshua Peraza <jperaza@chromium.org>
Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-05-10 10:27:58 -07:00
|
|
|
|
#if defined(CRASHPAD_IS_IN_FUCHSIA)
|
2019-02-21 12:06:55 -08:00
|
|
|
|
executable_path = base::FilePath("/pkg/bin/app");
|
fuchsia: Work around lack of packaging in Fuchsia tree build
Packaged test running seems to be a ways off, but with a bit of path
fiddling in test_paths.cc we can actually use the paths where the tests
are copied, so do that instead to get all the tests re-enabled. The
setup in BUILD.gn should be mostly-useful once packaging is working as
all helper/data files will need to specified there anyway.
Also, attempted fix to flaky behaviour in
ProcessReaderFuchsia.ChildThreads exposed because the tests are now
being run. zx_object_wait_many() waits on *any* of the objects, not
*all* of them. Derp!
And finally, for the same test, work around some unintuitive behaviour
in zx_task_suspend(), in particular that the thread will not be
suspended for the purpose of reading registers right away, but instead
only "sometime later", which appears in pratice to be after the next
context switch. Have ScopedTaskSuspend block for a while to try to
ensure the registers become readble, and if they don't, at least fail
noisily at that point.
Bug: crashpad:196
Change-Id: I01fb3590ede96301c941c2a88eba47fdbfe74ea7
Reviewed-on: https://chromium-review.googlesource.com/1053797
Reviewed-by: Joshua Peraza <jperaza@chromium.org>
Commit-Queue: Scott Graham <scottmg@chromium.org>
2018-05-10 10:27:58 -07:00
|
|
|
|
#endif
|
2017-04-03 13:53:11 -04:00
|
|
|
|
return executable_path;
|
|
|
|
|
}
|
|
|
|
|
|
2017-11-01 10:46:35 -04:00
|
|
|
|
// static
|
|
|
|
|
base::FilePath TestPaths::ExpectedExecutableBasename(
|
|
|
|
|
const base::FilePath::StringType& name) {
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#if BUILDFLAG(IS_FUCHSIA)
|
2018-02-15 13:31:10 -08:00
|
|
|
|
// Apps in Fuchsia packages are always named "app".
|
|
|
|
|
return base::FilePath("app");
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#else // BUILDFLAG(IS_FUCHSIA)
|
2017-12-18 14:35:55 -08:00
|
|
|
|
#if defined(CRASHPAD_IS_IN_CHROMIUM)
|
2017-11-01 10:46:35 -04:00
|
|
|
|
base::FilePath::StringType executable_name(
|
|
|
|
|
FILE_PATH_LITERAL("crashpad_tests"));
|
2017-12-18 14:35:55 -08:00
|
|
|
|
#else // CRASHPAD_IS_IN_CHROMIUM
|
2017-11-01 10:46:35 -04:00
|
|
|
|
base::FilePath::StringType executable_name(name);
|
2017-12-18 14:35:55 -08:00
|
|
|
|
#endif // CRASHPAD_IS_IN_CHROMIUM
|
2017-11-01 10:46:35 -04:00
|
|
|
|
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#if BUILDFLAG(IS_WIN)
|
2017-11-01 10:46:35 -04:00
|
|
|
|
executable_name += FILE_PATH_LITERAL(".exe");
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#endif // BUILDFLAG(IS_WIN)
|
2017-11-01 10:46:35 -04:00
|
|
|
|
|
|
|
|
|
return base::FilePath(executable_name);
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#endif // BUILDFLAG(IS_FUCHSIA)
|
2017-11-01 10:46:35 -04:00
|
|
|
|
}
|
|
|
|
|
|
2017-04-03 13:53:11 -04:00
|
|
|
|
// static
|
|
|
|
|
base::FilePath TestPaths::TestDataRoot() {
|
2015-03-09 15:13:13 -04:00
|
|
|
|
static base::FilePath* test_data_root =
|
|
|
|
|
new base::FilePath(TestDataRootInternal());
|
|
|
|
|
return *test_data_root;
|
|
|
|
|
}
|
|
|
|
|
|
2017-11-01 10:37:01 -04:00
|
|
|
|
// static
|
|
|
|
|
base::FilePath TestPaths::BuildArtifact(
|
|
|
|
|
const base::FilePath::StringType& module,
|
|
|
|
|
const base::FilePath::StringType& artifact,
|
|
|
|
|
FileType file_type,
|
|
|
|
|
Architecture architecture) {
|
|
|
|
|
base::FilePath directory;
|
|
|
|
|
switch (architecture) {
|
|
|
|
|
case Architecture::kDefault:
|
|
|
|
|
directory = Executable().DirName();
|
|
|
|
|
break;
|
|
|
|
|
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#if BUILDFLAG(IS_WIN) && defined(ARCH_CPU_64_BITS)
|
2017-11-01 10:37:01 -04:00
|
|
|
|
case Architecture::k32Bit:
|
|
|
|
|
directory = Output32BitDirectory();
|
|
|
|
|
CHECK(!directory.empty());
|
|
|
|
|
break;
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#endif // BUILDFLAG(IS_WIN) && ARCH_CPU_64_BITS
|
2017-11-01 10:37:01 -04:00
|
|
|
|
}
|
win: Dynamically disable WoW64 tests absent explicit 32-bit build output
Rather than having the 64-bit build assume that it lives in
out\{Debug,Release}_x64 and that it can find 32-bit build output in
out\{Debug,Release}, require the location of 32-bit build output to be
provided explicitly via the CRASHPAD_TEST_32_BIT_OUTPUT environment
variable. If this variable is not set, 64-bit tests that require 32-bit
test build output will dynamically disable themselves at runtime.
In order for this to work, a new DISABLED_TEST() macro is added to
support dynamically disabled tests. gtest does not have its own
first-class support for this
(https://groups.google.com/d/topic/googletestframework/Nwh3u7YFuN4,
https://github.com/google/googletest/issues/490) so this local solution
is used instead.
For tests via Crashpad’s own build\run_tests.py, which is how Crashpad’s
own buildbots and trybots invoke tests, CRASHPAD_TEST_32_BIT_OUTPUT is
set to a locaton compatible with the paths expected for the GYP-based
build. No test coverage is lost on Crashpad’s own buildbots and trybots.
For Crashpad tests in Chromium’s buildbots and trybots, this environment
variable will not be set, causing these tests to be dynamically
disabled.
Bug: crashpad:203, chromium:743139, chromium:777924
Change-Id: I3c0de2bf4f835e13ed5a4adda5760d6fed508126
Reviewed-on: https://chromium-review.googlesource.com/739795
Commit-Queue: Mark Mentovai <mark@chromium.org>
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-10-26 13:48:01 -04:00
|
|
|
|
|
2017-11-01 10:37:01 -04:00
|
|
|
|
base::FilePath::StringType test_name =
|
|
|
|
|
FILE_PATH_LITERAL("crashpad_") + module + FILE_PATH_LITERAL("_test");
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#if !defined(CRASHPAD_IS_IN_CHROMIUM) && !BUILDFLAG(IS_FUCHSIA)
|
2017-11-01 10:37:01 -04:00
|
|
|
|
CHECK(Executable().BaseName().RemoveFinalExtension().value() == test_name);
|
2017-12-18 14:35:55 -08:00
|
|
|
|
#endif // !CRASHPAD_IS_IN_CHROMIUM
|
2017-11-01 10:37:01 -04:00
|
|
|
|
|
|
|
|
|
base::FilePath::StringType extension;
|
|
|
|
|
switch (file_type) {
|
|
|
|
|
case FileType::kNone:
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case FileType::kExecutable:
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#if BUILDFLAG(IS_WIN)
|
2017-11-01 10:37:01 -04:00
|
|
|
|
extension = FILE_PATH_LITERAL(".exe");
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#elif BUILDFLAG(IS_FUCHSIA)
|
2018-01-17 14:03:39 -08:00
|
|
|
|
directory = base::FilePath(FILE_PATH_LITERAL("/pkg/bin"));
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#endif // BUILDFLAG(IS_WIN)
|
2017-11-01 10:37:01 -04:00
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case FileType::kLoadableModule:
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#if BUILDFLAG(IS_WIN)
|
2017-11-01 10:37:01 -04:00
|
|
|
|
extension = FILE_PATH_LITERAL(".dll");
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#else // BUILDFLAG(IS_WIN)
|
2017-11-01 10:37:01 -04:00
|
|
|
|
extension = FILE_PATH_LITERAL(".so");
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#endif // BUILDFLAG(IS_WIN)
|
2018-01-17 14:03:39 -08:00
|
|
|
|
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#if BUILDFLAG(IS_FUCHSIA)
|
2018-02-15 13:31:10 -08:00
|
|
|
|
// TODO(scottmg): .so files are currently deployed into /boot/lib, where
|
|
|
|
|
// they'll be found (without a path) by the loader. Application packaging
|
|
|
|
|
// infrastructure is in progress, so this will likely change again in the
|
|
|
|
|
// future.
|
|
|
|
|
directory = base::FilePath();
|
2018-01-17 14:03:39 -08:00
|
|
|
|
#endif
|
2017-11-01 10:37:01 -04:00
|
|
|
|
break;
|
2018-05-29 12:51:41 -07:00
|
|
|
|
|
|
|
|
|
case FileType::kCertificate:
|
2018-06-13 20:14:43 -07:00
|
|
|
|
#if defined(CRASHPAD_IS_IN_FUCHSIA)
|
2019-02-21 12:06:55 -08:00
|
|
|
|
directory = base::FilePath(FILE_PATH_LITERAL("/pkg/data"));
|
2018-06-13 20:14:43 -07:00
|
|
|
|
#endif
|
2018-05-29 12:51:41 -07:00
|
|
|
|
extension = FILE_PATH_LITERAL(".pem");
|
|
|
|
|
break;
|
win: Dynamically disable WoW64 tests absent explicit 32-bit build output
Rather than having the 64-bit build assume that it lives in
out\{Debug,Release}_x64 and that it can find 32-bit build output in
out\{Debug,Release}, require the location of 32-bit build output to be
provided explicitly via the CRASHPAD_TEST_32_BIT_OUTPUT environment
variable. If this variable is not set, 64-bit tests that require 32-bit
test build output will dynamically disable themselves at runtime.
In order for this to work, a new DISABLED_TEST() macro is added to
support dynamically disabled tests. gtest does not have its own
first-class support for this
(https://groups.google.com/d/topic/googletestframework/Nwh3u7YFuN4,
https://github.com/google/googletest/issues/490) so this local solution
is used instead.
For tests via Crashpad’s own build\run_tests.py, which is how Crashpad’s
own buildbots and trybots invoke tests, CRASHPAD_TEST_32_BIT_OUTPUT is
set to a locaton compatible with the paths expected for the GYP-based
build. No test coverage is lost on Crashpad’s own buildbots and trybots.
For Crashpad tests in Chromium’s buildbots and trybots, this environment
variable will not be set, causing these tests to be dynamically
disabled.
Bug: crashpad:203, chromium:743139, chromium:777924
Change-Id: I3c0de2bf4f835e13ed5a4adda5760d6fed508126
Reviewed-on: https://chromium-review.googlesource.com/739795
Commit-Queue: Mark Mentovai <mark@chromium.org>
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-10-26 13:48:01 -04:00
|
|
|
|
}
|
|
|
|
|
|
2017-11-01 10:37:01 -04:00
|
|
|
|
return directory.Append(test_name + FILE_PATH_LITERAL("_") + artifact +
|
|
|
|
|
extension);
|
|
|
|
|
}
|
|
|
|
|
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#if BUILDFLAG(IS_WIN) && defined(ARCH_CPU_64_BITS)
|
2017-11-01 10:37:01 -04:00
|
|
|
|
|
|
|
|
|
// static
|
|
|
|
|
bool TestPaths::Has32BitBuildArtifacts() {
|
|
|
|
|
return !Output32BitDirectory().empty();
|
win: Dynamically disable WoW64 tests absent explicit 32-bit build output
Rather than having the 64-bit build assume that it lives in
out\{Debug,Release}_x64 and that it can find 32-bit build output in
out\{Debug,Release}, require the location of 32-bit build output to be
provided explicitly via the CRASHPAD_TEST_32_BIT_OUTPUT environment
variable. If this variable is not set, 64-bit tests that require 32-bit
test build output will dynamically disable themselves at runtime.
In order for this to work, a new DISABLED_TEST() macro is added to
support dynamically disabled tests. gtest does not have its own
first-class support for this
(https://groups.google.com/d/topic/googletestframework/Nwh3u7YFuN4,
https://github.com/google/googletest/issues/490) so this local solution
is used instead.
For tests via Crashpad’s own build\run_tests.py, which is how Crashpad’s
own buildbots and trybots invoke tests, CRASHPAD_TEST_32_BIT_OUTPUT is
set to a locaton compatible with the paths expected for the GYP-based
build. No test coverage is lost on Crashpad’s own buildbots and trybots.
For Crashpad tests in Chromium’s buildbots and trybots, this environment
variable will not be set, causing these tests to be dynamically
disabled.
Bug: crashpad:203, chromium:743139, chromium:777924
Change-Id: I3c0de2bf4f835e13ed5a4adda5760d6fed508126
Reviewed-on: https://chromium-review.googlesource.com/739795
Commit-Queue: Mark Mentovai <mark@chromium.org>
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-10-26 13:48:01 -04:00
|
|
|
|
}
|
|
|
|
|
|
2022-01-19 15:00:24 -05:00
|
|
|
|
#endif // BUILDFLAG(IS_WIN) && defined(ARCH_CPU_64_BITS)
|
win: Dynamically disable WoW64 tests absent explicit 32-bit build output
Rather than having the 64-bit build assume that it lives in
out\{Debug,Release}_x64 and that it can find 32-bit build output in
out\{Debug,Release}, require the location of 32-bit build output to be
provided explicitly via the CRASHPAD_TEST_32_BIT_OUTPUT environment
variable. If this variable is not set, 64-bit tests that require 32-bit
test build output will dynamically disable themselves at runtime.
In order for this to work, a new DISABLED_TEST() macro is added to
support dynamically disabled tests. gtest does not have its own
first-class support for this
(https://groups.google.com/d/topic/googletestframework/Nwh3u7YFuN4,
https://github.com/google/googletest/issues/490) so this local solution
is used instead.
For tests via Crashpad’s own build\run_tests.py, which is how Crashpad’s
own buildbots and trybots invoke tests, CRASHPAD_TEST_32_BIT_OUTPUT is
set to a locaton compatible with the paths expected for the GYP-based
build. No test coverage is lost on Crashpad’s own buildbots and trybots.
For Crashpad tests in Chromium’s buildbots and trybots, this environment
variable will not be set, causing these tests to be dynamically
disabled.
Bug: crashpad:203, chromium:743139, chromium:777924
Change-Id: I3c0de2bf4f835e13ed5a4adda5760d6fed508126
Reviewed-on: https://chromium-review.googlesource.com/739795
Commit-Queue: Mark Mentovai <mark@chromium.org>
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-10-26 13:48:01 -04:00
|
|
|
|
|
2015-03-09 15:13:13 -04:00
|
|
|
|
} // namespace test
|
|
|
|
|
} // namespace crashpad
|