You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"There were tests whose specified size is too big" shown by default when adding a new test, following the tutorial. We should change the default size parameter to "small" to encourage people to write quick unit tests, and force people to annotate when they write slower tests.
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
meteorcloudy
added
team-Local-Exec
Issues and PRs for the Execution (Local) team
and removed
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
labels
Jan 20, 2025
Description of the bug:
"There were tests whose specified size is too big" shown by default when adding a new test, following the tutorial. We should change the default size parameter to "small" to encourage people to write quick unit tests, and force people to annotate when they write slower tests.
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Reproduced by the tutorial https://bazel.build/start/go#test-project
Which operating system are you running Bazel on?
No response
What is the output of
bazel info release
?No response
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD
?No response
If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: