
After recent changes to the Docker image, all hell broke loose and the CI started failing. This patch marks a few tests as unsupported until we can figure out what the issues are and fix them. In the future, it would be ideal if the nodes could pick up the Dockerfile present in the revision being tested, which would allow us to test changes to the Dockerfile in the CI, like we do for all other code changes. Differential Revision: https://reviews.llvm.org/D112737
36 lines
939 B
C++
36 lines
939 B
C++
//===----------------------------------------------------------------------===//
|
|
//
|
|
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
// See https://llvm.org/LICENSE.txt for license information.
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
//
|
|
// UNSUPPORTED: libcpp-has-no-monotonic-clock
|
|
|
|
// TODO(ldionne): This test fails on Ubuntu Focal on our CI nodes (and only there), in 32 bit mode.
|
|
// UNSUPPORTED: linux && 32bits-on-64bits
|
|
|
|
// <chrono>
|
|
|
|
// steady_clock
|
|
|
|
// static time_point now();
|
|
|
|
#include <chrono>
|
|
#include <cassert>
|
|
|
|
#include "test_macros.h"
|
|
|
|
int main(int, char**)
|
|
{
|
|
typedef std::chrono::steady_clock C;
|
|
C::time_point t1 = C::now();
|
|
C::time_point t2 = C::now();
|
|
assert(t2 >= t1);
|
|
// make sure t2 didn't wrap around
|
|
assert(t2 > std::chrono::time_point<C>());
|
|
|
|
return 0;
|
|
}
|