mirror of
https://github.com/bitcoin/bitcoin.git
synced 2025-02-10 10:52:31 -05:00
3c2e16be22
std::chrono::system_clock.time_since_epoch and time_t(0) are not guaranteed to use the Unix epoch timestamp, but in practice they almost certainly will. Any differing behavior will be assumed to be an error, unless certain platforms prove to consistently deviate, at which point we'll cope with it by adding offsets. Do a quick runtime check to verify that time_t(0) == std::chrono::system_clock's epoch time == unix epoch. Co-authored-by: Anthony Towns <aj@erisian.com.au>
22 lines
763 B
C++
22 lines
763 B
C++
// Copyright (c) 2012-2020 The Bitcoin Core developers
|
|
// Distributed under the MIT software license, see the accompanying
|
|
// file COPYING or http://www.opensource.org/licenses/mit-license.php.
|
|
|
|
#include <compat/sanity.h>
|
|
#include <key.h>
|
|
#include <test/util/setup_common.h>
|
|
#include <util/time.h>
|
|
|
|
#include <boost/test/unit_test.hpp>
|
|
|
|
BOOST_FIXTURE_TEST_SUITE(sanity_tests, BasicTestingSetup)
|
|
|
|
BOOST_AUTO_TEST_CASE(basic_sanity)
|
|
{
|
|
BOOST_CHECK_MESSAGE(glibc_sanity_test() == true, "libc sanity test");
|
|
BOOST_CHECK_MESSAGE(glibcxx_sanity_test() == true, "stdlib sanity test");
|
|
BOOST_CHECK_MESSAGE(ECC_InitSanityCheck() == true, "secp256k1 sanity test");
|
|
BOOST_CHECK_MESSAGE(ChronoSanityCheck() == true, "chrono epoch test");
|
|
}
|
|
|
|
BOOST_AUTO_TEST_SUITE_END()
|