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] test failure in otlp_file_exporter_test #3025

Closed
marcalff opened this issue Aug 13, 2024 · 0 comments · Fixed by #3031
Closed

[TEST] test failure in otlp_file_exporter_test #3025

marcalff opened this issue Aug 13, 2024 · 0 comments · Fixed by #3031
Labels
bug Something isn't working triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@marcalff
Copy link
Member

The following test fails with bazel + valgrind:

FAIL: //exporters/otlp:otlp_file_exporter_test (see /home/runner/.cache/bazel/e6b8d6759295e14b76bc8cb98b604748/execroot/_main/bazel-out/k8-fastbuild/testlogs/exporters/otlp/otlp_file_exporter_test/test.log)
INFO: From Testing //exporters/otlp:otlp_file_exporter_test:
==================== Test output for //exporters/otlp:otlp_file_exporter_test:
==11== Memcheck, a memory error detector
==11== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==11== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==11== Command: exporters/otlp/otlp_file_exporter_test
==11== 
Running main() from gmock_main.cc
[==========] Running 2 tests from 2 test suites.
[----------] Global test environment set-up.
[----------] 1 test from OtlpFileExporterTest
[ RUN      ] OtlpFileExporterTest.Shutdown
Error:  File: exporters/otlp/src/otlp_file_exporter.cc:55 [OTLP TRACE FILE Exporter] ERROR: Export 0 trace span(s) failed, exporter is shutdown
[       OK ] OtlpFileExporterTest.Shutdown (87 ms)
[----------] 1 test from OtlpFileExporterTest (93 ms total)

[----------] 1 test from OtlpFileExporterTestPeer
[ RUN      ] OtlpFileExporterTestPeer.ExportJsonIntegrationTestSync
unknown file: Failure
C++ exception with description "[json.exception.type_error.305] cannot use operator[] with a string argument with discarded" thrown in the test body.

[  FAILED  ] OtlpFileExporterTestPeer.ExportJsonIntegrationTestSync (2717 ms)
[----------] 1 test from OtlpFileExporterTestPeer (2720 ms total)

[----------] Global test environment tear-down
[==========] 2 tests from 2 test suites ran. (2869 ms total)
[  PASSED  ] 1 test.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] OtlpFileExporterTestPeer.ExportJsonIntegrationTestSync

 1 FAILED TEST
==11== 
==11== HEAP SUMMARY:
==11==     in use at exit: 0 bytes in 0 blocks
==11==   total heap usage: 8,401 allocs, 8,401 frees, 711,058 bytes allocated
==11== 
==11== All heap blocks were freed -- no leaks are possible
==11== 
==11== For lists of detected and suppressed errors, rerun with: -s
==11== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
================================================================================
@marcalff marcalff added the bug Something isn't working label Aug 13, 2024
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Aug 13, 2024
@marcalff marcalff added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant