Open kekxv opened 3 years ago
We need complete instructions on how you setup your environment before we can look into this.
buildfarm.example.com:8980 is [https://github.com/bazelbuild/bazel-buildfarm](https://github.com/bazelbuild/bazel-buildfarm)
on ubuntu and install mingw-w64
like apt install mingw-w64 -y
test file :
# com_google_googletest
http_archive(
name = "com_google_googletest",
strip_prefix = "googletest-release-1.10.0",
url = "https://github.com/google/googletest/archive/release-1.10.0.tar.gz",
sha256 = "9dc9157a9a1551ec7a7e43daea9a694a0bb5fb8bec81235d8a1e6ef64c716dcb",
)
cpp-base64 bazel test //...
INFO: Invocation ID: d6c9e1bd-7e09-4b32-9fa5-e29d814b42f7
INFO: Build options --cpu, --crosstool_top, and --run_under have changed, discarding analysis cache.
INFO: Analyzed 11 targets (0 packages loaded, 619 targets configured).
INFO: Found 10 targets and 1 test target...
FAIL: //:cpp-base64-test (see /private/var/tmp/_bazel_caesar/839a9831350a6e0f7600951b0b45d845/execroot/cpp-base64/bazel-out/mingw32-fastbuild/testlogs/cpp-base64-test/test.log)
INFO: Elapsed time: 16.876s, Critical Path: 15.86s
INFO: 24 processes: 16 remote cache hit, 2 internal, 6 remote.
INFO: Build completed, 1 test FAILED, 24 total actions
//:cpp-base64-test FAILED in 1.5s
/private/var/tmp/_bazel_caesar/839a9831350a6e0f7600951b0b45d845/execroot/cpp-base64/bazel-out/mingw32-fastbuild/testlogs/cpp-base64-test/test.log
INFO: Build completed, 1 test FAILED, 24 total actions
cpp-base64 cat /private/var/tmp/_bazel_caesar/839a9831350a6e0f7600951b0b45d845/execroot/cpp-base64/bazel-out/mingw32-fastbuild/testlogs/cpp-base64-test/test.log
exec ${PAGER:-/usr/bin/less} "$0" || exit 1
Executing tests from //:cpp-base64-test
-----------------------------------------------------------------------------
Running main() from gmock_main.cc
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from Base64
[ RUN ] Base64.encode
encoded:
UmVuw6kgTnlmZmVuZWdnZXIKaHR0cDovL3d3dy5yZW5lbnlmZmVuZWdnZXIuY2gKcGFzc2lvbiBmb3IgZGF0YQo=
decoded:
René Nyffenegger
http://www.renenyffenegger.ch
passion for data
encoded: YWJj
reference: YWJj
decoded: abc
encoded: YWJjZA==
reference: YWJjZA==
decoded: abcd
encoded: YWJjZGU=
reference: YWJjZGU=
decoded: abcde
[ OK ] Base64.encode (0 ms)
[----------] 1 test from Base64 (0 ms total)
[----------] Global test environment tear-down
[ FATAL ] external/com_google_googletest/googletest/src/gtest.cc:194:: Unable to open file "Z:\tmp\worker\default_memory_instance\operations\28ca6321-cf4c-4e91-badf-4dceeb537615\bazel-out\mingw32-fastbuild\bin\cpp-base64-test.exe.runfiles\cpp-base64\tmp\worker\default_memory_instance\operations\28ca6321-cf4c-4e91-badf-4dceeb537615\bazel-out\mingw32-fastbuild\testlogs\cpp-base64-test\test.xml"
cpp-base64
cpp-base64 cat .bazelrc
build:remote --remote_executor=grpc://buildfarm.example.com:8980
build:remote --remote_cache=grpc://buildfarm.example.com:8980
build:localhost_remote --remote_executor=grpc://localhost:8980
build:localhost_remote --remote_cache=grpc://localhost:8980
build:rpi --crosstool_top=//toolchain:clang_suite
build:rpi --cpu=armv7hf
build:rpi --host_crosstool_top=@bazel_tools//tools/cpp:toolchain
build:ubuntu --crosstool_top=//toolchain:clang_suite
build:ubuntu --cpu=k8
build:ubuntu --host_crosstool_top=@bazel_tools//tools/cpp:toolchain
build:ubuntu_remote --config=remote
build:ubuntu_remote --config=ubuntu
build:mingw32 --crosstool_top=//toolchain:clang_suite
build:mingw32 --cpu=mingw32
build:mingw32 --host_crosstool_top=@bazel_tools//tools/cpp:toolchain
test:mingw32 --run_under=wine
run:mingw32 --run_under=wine
build:mingw32_remote --config=remote
build:mingw32_remote --config=mingw32
# build --config=ubuntu_remote
build --config=mingw32_remote
Is there any fix for this issue? Because we are unable to mock fopen calls for test cases.
test was pass,but [ FATAL ] external/com_google_googletest/googletest/src/gtest.cc:194:: Unable to open file "text.xml"
use
i686-w64-mingw32-