Google Git
Sign in
bazel / bazel / 48e940f18d4f75bd6ba79415abfbac088687a1fa
commit48e940f18d4f75bd6ba79415abfbac088687a1fa[log] [tgz]
authorZhongpeng Lin <zplin@uber.com>Tue Oct 22 03:26:35 2024 -0700
committerCopybara-Service <copybara-worker@google.com>Tue Oct 22 03:28:11 2024 -0700
treeeb26d5fa0a8f9b46ab502258a8e4914b9501cde2
parent6e04ebacd075eae730e2275778d0af69adc2a74f [diff]
Reporting skipped test cases

`<skipped>` is a valid and common test case status supported by JUnit XML. Reporting skipped test cases as "passed" hides potential broken test cases. This PR reports them when `--test_summary=detailed`.

Before the fix:

```
INFO: Found 1 target and 1 test target...
INFO: Elapsed time: 103.095s, Critical Path: 43.23s
INFO: 476 processes: 36 internal, 440 darwin-sandbox.
INFO: Build completed successfully, 476 total actions
//foo/collect:go_default_test    PASSED in 0.6s
    PASSED  collect.TestCollect (0.0s)
    PASSED  collect.TestCollectBuildFailure (0.0s)
    PASSED  collect.TestFindComponentTestPaths (0.0s)
    PASSED  collect.TestFindComponentTestPaths/component_tests_dir_does_not_exist_in_directory_tree (0.0s)
    PASSED  collect.TestFindComponentTestPaths/component_tests_dir_does_not_exist_in_provided_directory (0.0s)
    PASSED  collect.TestFindComponentTestPaths/component_tests_dir_exists_in_directory_tree (0.0s)
    PASSED  collect.TestFindComponentTestPaths/component_tests_dir_exists_in_provided_directory (0.0s)
    PASSED  collect.TestFindComponentTestPaths/component_tests_dir_should_be_the_same (0.0s)
    PASSED  collect.TestFindComponentTestPaths/directory_above_service_root (0.0s)
    PASSED  collect.TestFindComponentTestPaths/in_component_tests_directory (0.0s)
    PASSED  collect.TestFindComponentTestPaths/multiple_component_tests_dirs (0.0s)
    PASSED  collect.TestFindPythonTestPath (0.0s)
    PASSED  collect.TestFindPythonTestPath/not_a_python_package (0.0s)
    PASSED  collect.TestFindPythonTestPath/python_tests_path_does_not_exist (0.0s)
    PASSED  collect.TestFindPythonTestPath/python_tests_path_exists (0.0s)
    PASSED  collect.TestRunComponentTests (0.0s)
    PASSED  collect.TestSetTest (0.0s)
    PASSED  collect.TestSetTest/component (0.0s)
    PASSED  collect.TestSetTest/fail (0.0s)
    PASSED  collect.TestSetTest/unit (0.0s)
    PASSED  collect.TestString (0.0s)
    PASSED  collect.TestString/should_be_component (0.0s)
    PASSED  collect.TestString/should_be_unit (0.0s)
Test cases: finished with 23 passing and 0 failing out of 23 test cases

Executed 1 out of 1 test: 1 test passes.
```

After the fix:

```
INFO: Found 1 target and 1 test target...
INFO: Elapsed time: 147.787s, Critical Path: 42.03s
INFO: 476 processes: 36 internal, 440 darwin-sandbox.
INFO: Build completed successfully, 476 total actions
//foo/collect:go_default_test    PASSED in 0.7s
    PASSED  collect.TestCollectBuildFailure (0.0s)
    PASSED  collect.TestFindComponentTestPaths (0.0s)
    PASSED  collect.TestFindComponentTestPaths/component_tests_dir_does_not_exist_in_directory_tree (0.0s)
    PASSED  collect.TestFindComponentTestPaths/component_tests_dir_does_not_exist_in_provided_directory (0.0s)
    PASSED  collect.TestFindComponentTestPaths/component_tests_dir_exists_in_directory_tree (0.0s)
    PASSED  collect.TestFindComponentTestPaths/component_tests_dir_exists_in_provided_directory (0.0s)
    PASSED  collect.TestFindComponentTestPaths/component_tests_dir_should_be_the_same (0.0s)
    PASSED  collect.TestFindComponentTestPaths/directory_above_service_root (0.0s)
    PASSED  collect.TestFindComponentTestPaths/in_component_tests_directory (0.0s)
    PASSED  collect.TestFindComponentTestPaths/multiple_component_tests_dirs (0.0s)
    PASSED  collect.TestFindPythonTestPath (0.0s)
    PASSED  collect.TestFindPythonTestPath/not_a_python_package (0.0s)
    PASSED  collect.TestFindPythonTestPath/python_tests_path_does_not_exist (0.0s)
    PASSED  collect.TestFindPythonTestPath/python_tests_path_exists (0.0s)
    PASSED  collect.TestRunComponentTests (0.0s)
    PASSED  collect.TestSetTest (0.0s)
    PASSED  collect.TestSetTest/component (0.0s)
    PASSED  collect.TestSetTest/fail (0.0s)
    PASSED  collect.TestSetTest/unit (0.0s)
    PASSED  collect.TestString (0.0s)
    PASSED  collect.TestString/should_be_component (0.0s)
    PASSED  collect.TestString/should_be_unit (0.0s)
    SKIPPED collect.TestCollect (0.0s)
Test cases: finished with 22 passing, 1 skipped and 0 failing out of 23 test cases

Executed 1 out of 1 test: 1 test passes.
```

Closes #23766.

PiperOrigin-RevId: 688477216
Change-Id: I4353d1dd4801a19ec56aae40d632d9f1061cfdbe
7 files changed
tree: eb26d5fa0a8f9b46ab502258a8e4914b9501cde2
  1. .bazelci/
  2. .github/
  3. examples/
  4. scripts/
  5. site/
  6. src/
  7. third_party/
  8. tools/
  9. .bazelrc
  10. .bazelversion
  11. .gitattributes
  12. .gitignore
  13. AUTHORS
  14. bazel_downloader.cfg
  15. BUILD
  16. CHANGELOG.md
  17. CODE_OF_CONDUCT.md
  18. CODEOWNERS
  19. combine_distfiles.py
  20. combine_distfiles_to_tar.sh
  21. compile.sh
  22. CONTRIBUTING.md
  23. CONTRIBUTORS
  24. distdir.bzl
  25. extensions.bzl
  26. LICENSE
  27. maven_install.json
  28. MODULE.bazel
  29. MODULE.bazel.lock
  30. rbe_extension.bzl
  31. README.md
  32. repositories.bzl
  33. requirements.txt
  34. SECURITY.md
  35. workspace_deps.bzl
README.md

Bazel

{Fast, Correct} - Choose two

Build and test software of any size, quickly and reliably.

  • Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.

  • One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.

  • Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.

  • Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.

Getting Started

Documentation

Reporting a Vulnerability

To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.

Contributing to Bazel

See CONTRIBUTING.md

Build status