bazelbuild/bazel

Duplicate timestamp in the output of "bazel version"

Open

#28,847 opened on Mar 1, 2026

View on GitHub
 (3 comments) (0 reactions) (1 assignee)Java (4,465 forks)batch import
P3help wantedteam-ExternalDepstype: bug

Repository metrics

Stars
 (25,384 stars)
PR merge metrics
 (Avg merge 11d 12h) (44 merged PRs in 30d)

Description

Description of the bug:

Output:

Bazelisk version: v1.28.1 Build label: 8.6.0 Build target: @@//src/main/java/com/google/devtools/build/lib/bazel:BazelServer Build time: Thu Feb 26 19:55:20 2026 (1772135720) Build timestamp: 1772135720 Build timestamp as int: 1772135720

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.

No response

Which operating system are you running Bazel on?

Linux

What is the output of bazel info release?

release 8.6.0

If bazel info release returns development 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 ?

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

Any other information, logs, or outputs that you want to share?

No response

Contributor guide

Research direction
Look at the Bazel version command implementation; likely in src/main/java/com/google/devtools/build/lib/bazel/BazelVersion.java or similar, find where Build timestamp and Build timestamp as int are both printed, and remove the duplicate.
Tech stack
java
Domain
build system
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Java
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85