Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test container:hashtablez_force_sampling_test fails on OSX 10.14.2 #268

Closed
kkiningh opened this issue Feb 27, 2019 · 4 comments
Closed

Test container:hashtablez_force_sampling_test fails on OSX 10.14.2 #268

kkiningh opened this issue Feb 27, 2019 · 4 comments
Assignees

Comments

@kkiningh
Copy link

kkiningh commented Feb 27, 2019

Test command:

$ bazel test //absl/container:hashtablez_force_sampling_test
INFO: Invocation ID: e51fd711-88c7-422c-ae24-4f4e90d588f3
INFO: Analysed target //absl/container:hashtablez_force_sampling_test (0 packages loaded, 0 targets configured).
INFO: Found 1 test target...
FAIL: //absl/container:hashtablez_force_sampling_test (see /private/var/tmp/_bazel_kkiningh/ccf5c17c3d69615a2c80e87264add296/execroot/com_google_absl/bazel-out/darwin-fastbuild/testlogs/absl/container/hashtablez_force_sampling_test/test.log)
Target //absl/container:hashtablez_force_sampling_test up-to-date:
  bazel-bin/absl/container/hashtablez_force_sampling_test
INFO: Elapsed time: 0.267s, Critical Path: 0.10s
INFO: 1 process: 1 darwin-sandbox.
INFO: Build completed, 1 test FAILED, 2 total actions
//absl/container:hashtablez_force_sampling_test                          FAILED in 0.1s
  /private/var/tmp/_bazel_kkiningh/ccf5c17c3d69615a2c80e87264add296/execroot/com_google_absl/bazel-out/darwin-fastbuild/testlogs/absl/container/hashtablez_force_sampling_test/test.log

INFO: Build completed, 1 test FAILED, 2 total actions

Log:

$ cat /private/var/tmp/_bazel_kkiningh/ccf5c17c3d69615a2c80e87264add296/execroot/com_google_absl/bazel-out/darwin-fastbuild/testlogs/absl/container/hashtablez_force_sampling_test/test.log
exec ${PAGER:-/usr/bin/less} "$0" || exit 1
Executing tests from //absl/container:hashtablez_force_sampling_test
-----------------------------------------------------------------------------
Running main() from gmock_main.cc
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from kAbslContainerInternalSampleEverything
[ RUN      ] kAbslContainerInternalSampleEverything.Works
absl/container/internal/hashtablez_force_sampling_test.cc:52: Failure
Value of: samples
Expected: only contains elements that is equal to true
  Actual: { false, false, false } (of type bool [3]), whose element #0 doesn't match
absl/container/internal/hashtablez_force_sampling_test.cc:55: Failure
Value of: HashtablezInfoHandlePeer::IsSampled(Sample())
  Actual: false
Expected: true
[  FAILED  ] kAbslContainerInternalSampleEverything.Works (0 ms)
[----------] 1 test from kAbslContainerInternalSampleEverything (0 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (0 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] kAbslContainerInternalSampleEverything.Works

Mac version:

$ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.14.2
BuildVersion:   18C54

abseil commit:

$ git rev-parse HEAD
b312c3cb53a0aad75a85ac2bf57c4a614fbd48d4
@kkiningh
Copy link
Author

kkiningh commented Feb 27, 2019

I see this test is tagged no_test_darwin_x86_64, but it still runs when I run all tests as recommended in the quickstart guide (bazel test //absel/...).

@derekmauro
Copy link
Member

Thanks for the report. This test should probably never have been released and the failures should be safe to ignore. I'll look into having it removed.

@derekmauro derekmauro self-assigned this Feb 27, 2019
@JonathanDCohen
Copy link
Contributor

I see this test is tagged no_test_darwin_x86_64, but it still runs when I run all tests as recommended in the quickstart guide (bazel test //absel/...).

That's expected behavior. Those tags are only functional for our own CI scripts, which are unfortunately internal only. You do something like bazel test --build_tag_filters=-no_test_darwin_x86_64 blahblahblah(relevant documentation) in order to skip all the tests which aren't supported on macos.

@derekmauro
Copy link
Member

I see this test is tagged no_test_darwin_x86_64, but it still runs when I run all tests as recommended in the quickstart guide (bazel test //absel/...).

That's expected behavior. Those tags are only functional for our own CI scripts, which are unfortunately internal only. You do something like bazel test --build_tag_filters=-no_test_darwin_x86_64 blahblahblah(relevant documentation) in order to skip all the tests which aren't supported on macos.

Actually it's not the expected behavior. Everything we release is supposed to be portable. The library in question is an internal hack that wasn't supposed to be released. I'm removing all the no_test_* filters from our CI scripts. We only use those tags for internal tests.

4s5t2os41n added a commit to 4s5t2os41n/abseil-cpp that referenced this issue Jul 4, 2024
--
92e1bd6dc9e64163659028b640427d6d8573e41c by Abseil Team <absl-team@google.com>:

Don't enable ABSL_HAVE_STD_IS_TRIVIALLY_ASSIGNABLE with MSVC when used with nvcc.

With nvcc on Windows __has_trivial_assign(int) is false; that leads to a failure of the check in is_trivially_copy_assignable. A better solution would probably be to use the std-provided check in this case, but that seems like a more intrusive change.

PiperOrigin-RevId: 236135209

--
26cee4a7e647076b4e2f88375b4848d1469e55ed by Derek Mauro <dmauro@google.com>:

Remove hashtablez_force_sampling from the open-source release.
This should not have been released. It is internal-only and not portable.

Fixes abseil/abseil-cpp#268

PiperOrigin-RevId: 235978666

--
935a885ec0e108963014f1bb79f00102da8f3871 by CJ Johnson <johnsoncj@google.com>:

Internal change

PiperOrigin-RevId: 235976027

--
1c148c89de6064031f1ad9f2eeac0331bd77b7b0 by Tom Manshreck <shreck@google.com>:

Add design note for absl::from_chars to abseil.io

Fixes #165

PiperOrigin-RevId: 235975923
GitOrigin-RevId: 92e1bd6dc9e64163659028b640427d6d8573e41c
Change-Id: I220b0bbb46742070ea8c2a94b06007ecae76fe0f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants