2015-03-30 14:51:34 -04:00
|
|
|
// Copyright 2015 The Crashpad Authors. All rights reserved.
|
|
|
|
//
|
|
|
|
// 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.
|
|
|
|
|
|
|
|
#include "util/thread/thread_log_messages.h"
|
|
|
|
|
|
|
|
#include <string.h>
|
2016-01-06 12:22:50 -05:00
|
|
|
#include <sys/types.h>
|
2015-03-30 14:51:34 -04:00
|
|
|
|
|
|
|
#include "base/logging.h"
|
2019-01-04 16:57:57 -05:00
|
|
|
#include "base/stl_util.h"
|
2015-03-30 14:51:34 -04:00
|
|
|
#include "base/strings/stringprintf.h"
|
|
|
|
#include "gtest/gtest.h"
|
2015-05-13 14:05:57 -04:00
|
|
|
#include "util/thread/thread.h"
|
2015-03-30 14:51:34 -04:00
|
|
|
|
|
|
|
namespace crashpad {
|
|
|
|
namespace test {
|
|
|
|
namespace {
|
|
|
|
|
|
|
|
TEST(ThreadLogMessages, Empty) {
|
|
|
|
ThreadLogMessages thread_log_messages;
|
|
|
|
|
|
|
|
const std::vector<std::string>& log_messages =
|
|
|
|
thread_log_messages.log_messages();
|
|
|
|
|
|
|
|
EXPECT_TRUE(log_messages.empty());
|
|
|
|
}
|
|
|
|
|
|
|
|
// For a message formatted like "[preamble] message\n", returns just "message".
|
2020-05-06 20:39:19 -04:00
|
|
|
// If the message is not formatted as expected, a Google Test expectation
|
|
|
|
// failure will be recorded and this function will return an empty string.
|
2015-03-30 14:51:34 -04:00
|
|
|
std::string MessageString(const std::string& log_message) {
|
|
|
|
if (log_message.size() < 1) {
|
|
|
|
EXPECT_GE(log_message.size(), 1u);
|
|
|
|
return std::string();
|
|
|
|
}
|
|
|
|
|
2017-07-25 19:15:48 -04:00
|
|
|
constexpr char kStartChar = '[';
|
2015-03-30 14:51:34 -04:00
|
|
|
if (log_message[0] != kStartChar) {
|
test: Use (actual, [un]expected) in gtest {ASSERT,EXPECT}_{EQ,NE}
gtest used to require (expected, actual) ordering for arguments to
EXPECT_EQ and ASSERT_EQ, and in failed test assertions would identify
each side as “expected” or “actual.” Tests in Crashpad adhered to this
traditional ordering. After a gtest change in February 2016, it is now
agnostic with respect to the order of these arguments.
This change mechanically updates all uses of these macros to (actual,
expected) by reversing them. This provides consistency with our use of
the logging CHECK_EQ and DCHECK_EQ macros, and makes for better
readability by ordinary native speakers. The rough (but working!)
conversion tool is
https://chromium-review.googlesource.com/c/466727/1/rewrite_expectassert_eq.py,
and “git cl format” cleaned up its output.
EXPECT_NE and ASSERT_NE never had a preferred ordering. gtest never made
a judgment that one side or the other needed to provide an “unexpected”
value. Consequently, some code used (unexpected, actual) while other
code used (actual, unexpected). For consistency with the new EXPECT_EQ
and ASSERT_EQ usage, as well as consistency with CHECK_NE and DCHECK_NE,
this change also updates these use sites to (actual, unexpected) where
one side can be called “unexpected” as, for example, std::string::npos
can be. Unfortunately, this portion was a manual conversion.
References:
https://github.com/google/googletest/blob/master/googletest/docs/Primer.md#binary-comparison
https://github.com/google/googletest/commit/77d6b173380332b1c1bc540532641f410ec82d65
https://github.com/google/googletest/pull/713
Change-Id: I978fef7c94183b8b1ef63f12f5ab4d6693626be3
Reviewed-on: https://chromium-review.googlesource.com/466727
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-04-04 00:35:21 -04:00
|
|
|
EXPECT_EQ(log_message[0], kStartChar);
|
2015-03-30 14:51:34 -04:00
|
|
|
return std::string();
|
|
|
|
}
|
|
|
|
|
2017-07-25 13:34:04 -04:00
|
|
|
static constexpr char kFindString[] = "] ";
|
2015-03-30 14:51:34 -04:00
|
|
|
size_t pos = log_message.find(kFindString);
|
|
|
|
if (pos == std::string::npos) {
|
test: Use (actual, [un]expected) in gtest {ASSERT,EXPECT}_{EQ,NE}
gtest used to require (expected, actual) ordering for arguments to
EXPECT_EQ and ASSERT_EQ, and in failed test assertions would identify
each side as “expected” or “actual.” Tests in Crashpad adhered to this
traditional ordering. After a gtest change in February 2016, it is now
agnostic with respect to the order of these arguments.
This change mechanically updates all uses of these macros to (actual,
expected) by reversing them. This provides consistency with our use of
the logging CHECK_EQ and DCHECK_EQ macros, and makes for better
readability by ordinary native speakers. The rough (but working!)
conversion tool is
https://chromium-review.googlesource.com/c/466727/1/rewrite_expectassert_eq.py,
and “git cl format” cleaned up its output.
EXPECT_NE and ASSERT_NE never had a preferred ordering. gtest never made
a judgment that one side or the other needed to provide an “unexpected”
value. Consequently, some code used (unexpected, actual) while other
code used (actual, unexpected). For consistency with the new EXPECT_EQ
and ASSERT_EQ usage, as well as consistency with CHECK_NE and DCHECK_NE,
this change also updates these use sites to (actual, unexpected) where
one side can be called “unexpected” as, for example, std::string::npos
can be. Unfortunately, this portion was a manual conversion.
References:
https://github.com/google/googletest/blob/master/googletest/docs/Primer.md#binary-comparison
https://github.com/google/googletest/commit/77d6b173380332b1c1bc540532641f410ec82d65
https://github.com/google/googletest/pull/713
Change-Id: I978fef7c94183b8b1ef63f12f5ab4d6693626be3
Reviewed-on: https://chromium-review.googlesource.com/466727
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-04-04 00:35:21 -04:00
|
|
|
EXPECT_NE(pos, std::string::npos);
|
2015-03-30 14:51:34 -04:00
|
|
|
return std::string();
|
|
|
|
}
|
|
|
|
|
|
|
|
std::string message_string = log_message.substr(pos + strlen(kFindString));
|
|
|
|
if (message_string.size() < 1) {
|
|
|
|
EXPECT_GE(message_string.size(), 1u);
|
|
|
|
return std::string();
|
|
|
|
}
|
|
|
|
|
2017-07-25 19:15:48 -04:00
|
|
|
constexpr char kEndChar = '\n';
|
2015-03-30 14:51:34 -04:00
|
|
|
if (message_string[message_string.size() - 1] != kEndChar) {
|
|
|
|
EXPECT_NE(message_string[message_string.size() - 1], kEndChar);
|
|
|
|
return std::string();
|
|
|
|
}
|
|
|
|
|
|
|
|
message_string.resize(message_string.size() - 1);
|
|
|
|
return message_string;
|
|
|
|
}
|
|
|
|
|
|
|
|
TEST(ThreadLogMessages, Basic) {
|
|
|
|
// Logging must be enabled at least at this level for this test to work.
|
|
|
|
ASSERT_TRUE(LOG_IS_ON(INFO));
|
|
|
|
|
|
|
|
{
|
2017-07-25 13:34:04 -04:00
|
|
|
static constexpr const char* kMessages[] = {
|
2015-03-30 14:51:34 -04:00
|
|
|
"An info message",
|
|
|
|
"A warning message",
|
|
|
|
"An error message",
|
|
|
|
};
|
|
|
|
|
|
|
|
ThreadLogMessages thread_log_messages;
|
|
|
|
|
|
|
|
LOG(INFO) << kMessages[0];
|
|
|
|
LOG(WARNING) << kMessages[1];
|
|
|
|
LOG(ERROR) << kMessages[2];
|
|
|
|
|
|
|
|
const std::vector<std::string>& log_messages =
|
|
|
|
thread_log_messages.log_messages();
|
|
|
|
|
2019-01-04 16:57:57 -05:00
|
|
|
EXPECT_EQ(log_messages.size(), base::size(kMessages));
|
|
|
|
for (size_t index = 0; index < base::size(kMessages); ++index) {
|
test: Use (actual, [un]expected) in gtest {ASSERT,EXPECT}_{EQ,NE}
gtest used to require (expected, actual) ordering for arguments to
EXPECT_EQ and ASSERT_EQ, and in failed test assertions would identify
each side as “expected” or “actual.” Tests in Crashpad adhered to this
traditional ordering. After a gtest change in February 2016, it is now
agnostic with respect to the order of these arguments.
This change mechanically updates all uses of these macros to (actual,
expected) by reversing them. This provides consistency with our use of
the logging CHECK_EQ and DCHECK_EQ macros, and makes for better
readability by ordinary native speakers. The rough (but working!)
conversion tool is
https://chromium-review.googlesource.com/c/466727/1/rewrite_expectassert_eq.py,
and “git cl format” cleaned up its output.
EXPECT_NE and ASSERT_NE never had a preferred ordering. gtest never made
a judgment that one side or the other needed to provide an “unexpected”
value. Consequently, some code used (unexpected, actual) while other
code used (actual, unexpected). For consistency with the new EXPECT_EQ
and ASSERT_EQ usage, as well as consistency with CHECK_NE and DCHECK_NE,
this change also updates these use sites to (actual, unexpected) where
one side can be called “unexpected” as, for example, std::string::npos
can be. Unfortunately, this portion was a manual conversion.
References:
https://github.com/google/googletest/blob/master/googletest/docs/Primer.md#binary-comparison
https://github.com/google/googletest/commit/77d6b173380332b1c1bc540532641f410ec82d65
https://github.com/google/googletest/pull/713
Change-Id: I978fef7c94183b8b1ef63f12f5ab4d6693626be3
Reviewed-on: https://chromium-review.googlesource.com/466727
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-04-04 00:35:21 -04:00
|
|
|
EXPECT_EQ(MessageString(log_messages[index]), kMessages[index])
|
2015-03-30 14:51:34 -04:00
|
|
|
<< "index " << index;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
{
|
2017-07-25 13:34:04 -04:00
|
|
|
static constexpr char kMessage[] = "Sample error message";
|
2015-03-30 14:51:34 -04:00
|
|
|
|
|
|
|
ThreadLogMessages thread_log_messages;
|
|
|
|
|
|
|
|
LOG(ERROR) << kMessage;
|
|
|
|
|
|
|
|
const std::vector<std::string>& log_messages =
|
|
|
|
thread_log_messages.log_messages();
|
|
|
|
|
test: Use (actual, [un]expected) in gtest {ASSERT,EXPECT}_{EQ,NE}
gtest used to require (expected, actual) ordering for arguments to
EXPECT_EQ and ASSERT_EQ, and in failed test assertions would identify
each side as “expected” or “actual.” Tests in Crashpad adhered to this
traditional ordering. After a gtest change in February 2016, it is now
agnostic with respect to the order of these arguments.
This change mechanically updates all uses of these macros to (actual,
expected) by reversing them. This provides consistency with our use of
the logging CHECK_EQ and DCHECK_EQ macros, and makes for better
readability by ordinary native speakers. The rough (but working!)
conversion tool is
https://chromium-review.googlesource.com/c/466727/1/rewrite_expectassert_eq.py,
and “git cl format” cleaned up its output.
EXPECT_NE and ASSERT_NE never had a preferred ordering. gtest never made
a judgment that one side or the other needed to provide an “unexpected”
value. Consequently, some code used (unexpected, actual) while other
code used (actual, unexpected). For consistency with the new EXPECT_EQ
and ASSERT_EQ usage, as well as consistency with CHECK_NE and DCHECK_NE,
this change also updates these use sites to (actual, unexpected) where
one side can be called “unexpected” as, for example, std::string::npos
can be. Unfortunately, this portion was a manual conversion.
References:
https://github.com/google/googletest/blob/master/googletest/docs/Primer.md#binary-comparison
https://github.com/google/googletest/commit/77d6b173380332b1c1bc540532641f410ec82d65
https://github.com/google/googletest/pull/713
Change-Id: I978fef7c94183b8b1ef63f12f5ab4d6693626be3
Reviewed-on: https://chromium-review.googlesource.com/466727
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-04-04 00:35:21 -04:00
|
|
|
EXPECT_EQ(log_messages.size(), 1u);
|
|
|
|
EXPECT_EQ(MessageString(log_messages[0]), kMessage);
|
2015-03-30 14:51:34 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
{
|
|
|
|
ThreadLogMessages thread_log_messages;
|
|
|
|
|
|
|
|
LOG(INFO) << "I can't believe I " << "streamed" << " the whole thing.";
|
|
|
|
|
|
|
|
const std::vector<std::string>& log_messages =
|
|
|
|
thread_log_messages.log_messages();
|
|
|
|
|
test: Use (actual, [un]expected) in gtest {ASSERT,EXPECT}_{EQ,NE}
gtest used to require (expected, actual) ordering for arguments to
EXPECT_EQ and ASSERT_EQ, and in failed test assertions would identify
each side as “expected” or “actual.” Tests in Crashpad adhered to this
traditional ordering. After a gtest change in February 2016, it is now
agnostic with respect to the order of these arguments.
This change mechanically updates all uses of these macros to (actual,
expected) by reversing them. This provides consistency with our use of
the logging CHECK_EQ and DCHECK_EQ macros, and makes for better
readability by ordinary native speakers. The rough (but working!)
conversion tool is
https://chromium-review.googlesource.com/c/466727/1/rewrite_expectassert_eq.py,
and “git cl format” cleaned up its output.
EXPECT_NE and ASSERT_NE never had a preferred ordering. gtest never made
a judgment that one side or the other needed to provide an “unexpected”
value. Consequently, some code used (unexpected, actual) while other
code used (actual, unexpected). For consistency with the new EXPECT_EQ
and ASSERT_EQ usage, as well as consistency with CHECK_NE and DCHECK_NE,
this change also updates these use sites to (actual, unexpected) where
one side can be called “unexpected” as, for example, std::string::npos
can be. Unfortunately, this portion was a manual conversion.
References:
https://github.com/google/googletest/blob/master/googletest/docs/Primer.md#binary-comparison
https://github.com/google/googletest/commit/77d6b173380332b1c1bc540532641f410ec82d65
https://github.com/google/googletest/pull/713
Change-Id: I978fef7c94183b8b1ef63f12f5ab4d6693626be3
Reviewed-on: https://chromium-review.googlesource.com/466727
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-04-04 00:35:21 -04:00
|
|
|
EXPECT_EQ(log_messages.size(), 1u);
|
|
|
|
EXPECT_EQ(MessageString(log_messages[0]),
|
|
|
|
"I can't believe I streamed the whole thing.");
|
2015-03-30 14:51:34 -04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
class LoggingTestThread : public Thread {
|
|
|
|
public:
|
|
|
|
LoggingTestThread() : thread_number_(0), start_(0), count_(0) {}
|
|
|
|
~LoggingTestThread() override {}
|
|
|
|
|
|
|
|
void Initialize(size_t thread_number, int start, int count) {
|
|
|
|
thread_number_ = thread_number;
|
|
|
|
start_ = start;
|
|
|
|
count_ = count;
|
|
|
|
}
|
|
|
|
|
|
|
|
private:
|
|
|
|
void ThreadMain() override {
|
|
|
|
ThreadLogMessages thread_log_messages;
|
|
|
|
|
|
|
|
std::vector<std::string> expected_messages;
|
2015-03-30 17:58:12 -04:00
|
|
|
for (int index = start_; index < start_ + count_; ++index) {
|
2015-03-30 14:51:34 -04:00
|
|
|
std::string message = base::StringPrintf("message %d", index);
|
|
|
|
expected_messages.push_back(message);
|
|
|
|
LOG(WARNING) << message;
|
|
|
|
}
|
|
|
|
|
|
|
|
const std::vector<std::string>& log_messages =
|
|
|
|
thread_log_messages.log_messages();
|
|
|
|
|
test: Use (actual, [un]expected) in gtest {ASSERT,EXPECT}_{EQ,NE}
gtest used to require (expected, actual) ordering for arguments to
EXPECT_EQ and ASSERT_EQ, and in failed test assertions would identify
each side as “expected” or “actual.” Tests in Crashpad adhered to this
traditional ordering. After a gtest change in February 2016, it is now
agnostic with respect to the order of these arguments.
This change mechanically updates all uses of these macros to (actual,
expected) by reversing them. This provides consistency with our use of
the logging CHECK_EQ and DCHECK_EQ macros, and makes for better
readability by ordinary native speakers. The rough (but working!)
conversion tool is
https://chromium-review.googlesource.com/c/466727/1/rewrite_expectassert_eq.py,
and “git cl format” cleaned up its output.
EXPECT_NE and ASSERT_NE never had a preferred ordering. gtest never made
a judgment that one side or the other needed to provide an “unexpected”
value. Consequently, some code used (unexpected, actual) while other
code used (actual, unexpected). For consistency with the new EXPECT_EQ
and ASSERT_EQ usage, as well as consistency with CHECK_NE and DCHECK_NE,
this change also updates these use sites to (actual, unexpected) where
one side can be called “unexpected” as, for example, std::string::npos
can be. Unfortunately, this portion was a manual conversion.
References:
https://github.com/google/googletest/blob/master/googletest/docs/Primer.md#binary-comparison
https://github.com/google/googletest/commit/77d6b173380332b1c1bc540532641f410ec82d65
https://github.com/google/googletest/pull/713
Change-Id: I978fef7c94183b8b1ef63f12f5ab4d6693626be3
Reviewed-on: https://chromium-review.googlesource.com/466727
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-04-04 00:35:21 -04:00
|
|
|
ASSERT_EQ(log_messages.size(), static_cast<size_t>(count_));
|
2015-03-30 14:51:34 -04:00
|
|
|
for (size_t index = 0; index < log_messages.size(); ++index) {
|
test: Use (actual, [un]expected) in gtest {ASSERT,EXPECT}_{EQ,NE}
gtest used to require (expected, actual) ordering for arguments to
EXPECT_EQ and ASSERT_EQ, and in failed test assertions would identify
each side as “expected” or “actual.” Tests in Crashpad adhered to this
traditional ordering. After a gtest change in February 2016, it is now
agnostic with respect to the order of these arguments.
This change mechanically updates all uses of these macros to (actual,
expected) by reversing them. This provides consistency with our use of
the logging CHECK_EQ and DCHECK_EQ macros, and makes for better
readability by ordinary native speakers. The rough (but working!)
conversion tool is
https://chromium-review.googlesource.com/c/466727/1/rewrite_expectassert_eq.py,
and “git cl format” cleaned up its output.
EXPECT_NE and ASSERT_NE never had a preferred ordering. gtest never made
a judgment that one side or the other needed to provide an “unexpected”
value. Consequently, some code used (unexpected, actual) while other
code used (actual, unexpected). For consistency with the new EXPECT_EQ
and ASSERT_EQ usage, as well as consistency with CHECK_NE and DCHECK_NE,
this change also updates these use sites to (actual, unexpected) where
one side can be called “unexpected” as, for example, std::string::npos
can be. Unfortunately, this portion was a manual conversion.
References:
https://github.com/google/googletest/blob/master/googletest/docs/Primer.md#binary-comparison
https://github.com/google/googletest/commit/77d6b173380332b1c1bc540532641f410ec82d65
https://github.com/google/googletest/pull/713
Change-Id: I978fef7c94183b8b1ef63f12f5ab4d6693626be3
Reviewed-on: https://chromium-review.googlesource.com/466727
Reviewed-by: Scott Graham <scottmg@chromium.org>
2017-04-04 00:35:21 -04:00
|
|
|
EXPECT_EQ(MessageString(log_messages[index]), expected_messages[index])
|
2015-03-30 14:51:34 -04:00
|
|
|
<< "thread_number_ " << thread_number_ << ", index " << index;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
size_t thread_number_;
|
|
|
|
int start_;
|
|
|
|
int count_;
|
|
|
|
|
|
|
|
DISALLOW_COPY_AND_ASSIGN(LoggingTestThread);
|
|
|
|
};
|
|
|
|
|
|
|
|
TEST(ThreadLogMessages, Multithreaded) {
|
|
|
|
// Logging must be enabled at least at this level for this test to work.
|
|
|
|
ASSERT_TRUE(LOG_IS_ON(WARNING));
|
|
|
|
|
|
|
|
LoggingTestThread threads[20];
|
|
|
|
int start = 0;
|
2019-01-04 16:57:57 -05:00
|
|
|
for (size_t index = 0; index < base::size(threads); ++index) {
|
2015-03-30 14:51:34 -04:00
|
|
|
threads[index].Initialize(
|
|
|
|
index, static_cast<int>(start), static_cast<int>(index));
|
|
|
|
start += static_cast<int>(index);
|
|
|
|
|
|
|
|
ASSERT_NO_FATAL_FAILURE(threads[index].Start());
|
|
|
|
}
|
|
|
|
|
|
|
|
for (LoggingTestThread& thread : threads) {
|
|
|
|
thread.Join();
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
} // namespace
|
|
|
|
} // namespace test
|
|
|
|
} // namespace crashpad
|