这是indexloc提供的服务,不要输入任何密码
Skip to content

[Bug] Bazel test is not discovering the test suite #988

@abbywh

Description

@abbywh

Steps To Reproduce

bazel test --nocache_test_results //spark:test_test_suite_src_test_scala_ai_chronon_spark_test_FetcherTest.scala --test_output=all

% bazel test --nocache_test_results //spark:test_test_suite_src_test_scala_ai_chronon_spark_test_FetcherTest.scala --test_output=all
INFO: Analyzed target //spark:test_test_suite_src_test_scala_ai_chronon_spark_test_FetcherTest.scala (0 packages loaded, 0 targets configured).
INFO: Found 1 test target...
INFO: From Testing //spark:test_test_suite_src_test_scala_ai_chronon_spark_test_FetcherTest.scala:
==================== Test output for //spark:test_test_suite_src_test_scala_ai_chronon_spark_test_FetcherTest.scala:
Discovery starting.
Discovery completed in 28 milliseconds.
Run starting. Expected test count is: 0
DiscoverySuite:
Run completed in 41 milliseconds.
Total number of tests run: 0
Suites: completed 1, aborted 0
Tests: succeeded 0, failed 0, canceled 0, ignored 0, pending 0
No tests were executed.
================================================================================
Target //spark:test_test_suite_src_test_scala_ai_chronon_spark_test_FetcherTest.scala up-to-date:
  bazel-bin/spark/test_test_suite_src_test_scala_ai_chronon_spark_test_FetcherTest.scala.jar
  bazel-bin/spark/test_test_suite_src_test_scala_ai_chronon_spark_test_FetcherTest.scala
INFO: Elapsed time: 0.806s, Critical Path: 0.70s
INFO: 2 processes: 1 internal, 1 local.
INFO: Build completed successfully, 2 total actions
//spark:test_test_suite_src_test_scala_ai_chronon_spark_test_FetcherTest.scala PASSED in 0.7s

Executed 1 out of 1 test: 1 test passes.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see which ones these are.

You can see this is happening on most tests with bazel test //... --test_output=all.

I'm pretty sure it's because the bazel rule is configured for ScalaTest but the package is using JUnit. We have a starter PR to start cutting it over but ran into dependency issues.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions