bazel: test_verbose_timeout_warnings giving strange results

I ran the test below with --runs_per_test=3 --test_verbose_timeout_warnings.

The test is sized medium, which is documented to expect to fall within 30s-300s. Yet you can see below that it ran in 61.8 seconds, and I’m still getting a warning.

Also, the warning always states that the test ran in 0.0s. This is what it shows for every test, no matter how long it actually took.

//tests/java/com/urbancompass/listing:mongo                              PASSED in 61.8s
  Stats over 3 runs: max = 61.8s, min = 61.7s, avg = 61.8s, dev = 0.0s
  WARNING: //tests/java/com/urbancompass/listing:mongo: Test execution time (0.0s excluding execution overhead) outside of range for MODERATE tests. Consider setting timeout="short" or size="small".
  WARNING: //tests/java/com/urbancompass/listing:mongo: Test execution time (0.0s excluding execution overhead) outside of range for MODERATE tests. Consider setting timeout="short" or size="small".
  WARNING: //tests/java/com/urbancompass/listing:mongo: Test execution time (0.0s excluding execution overhead) outside of range for MODERATE tests. Consider setting timeout="short" or size="small".

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 17 (14 by maintainers)

Commits related to this issue

Most upvoted comments

I think I have a fix.