Move timing reports to target/cargo-timings

This avoids dropping them wherever Cargo happens to run from, and
instead places them under the target directory.

This has the advantage, and disadvantage, that `cargo clean` will remove
them.

src/cargo/core/compiler/job_queue.rs

@@ -839,7 +839,7 @@ impl<'cfg> DrainState<'cfg> {
         }
 
         let time_elapsed = util::elapsed(cx.bcx.config.creation_time().elapsed());
-        if let Err(e) = self.timings.finished(cx.bcx, &error) {
+        if let Err(e) = self.timings.finished(cx, &error) {
             if error.is_some() {
                 crate::display_error(&e, &mut cx.bcx.config.shell());
             } else {

src/cargo/core/compiler/timings.rs

@@ -4,7 +4,7 @@
 //! long it takes for different units to compile.
 use super::{CompileMode, Unit};
 use crate::core::compiler::job_queue::JobId;
-use crate::core::compiler::{BuildContext, TimingOutput};
+use crate::core::compiler::{BuildContext, Context, TimingOutput};
 use crate::core::PackageId;
 use crate::util::cpu::State;
 use crate::util::machine_message::{self, Message};
@@ -293,7 +293,7 @@ impl<'cfg> Timings<'cfg> {
     /// Call this when all units are finished.
     pub fn finished(
         &mut self,
-        bcx: &BuildContext<'_, '_>,
+        cx: &Context<'_, '_>,
         error: &Option<anyhow::Error>,
     ) -> CargoResult<()> {
         if !self.enabled {
@@ -303,21 +303,19 @@ impl<'cfg> Timings<'cfg> {
         self.unit_times
             .sort_unstable_by(|a, b| a.start.partial_cmp(&b.start).unwrap());
         if self.report_html {
-            self.report_html(bcx, error)
+            self.report_html(cx, error)
                 .with_context(|| "failed to save timing report")?;
         }
         Ok(())
     }
 
     /// Save HTML report to disk.
-    fn report_html(
-        &self,
-        bcx: &BuildContext<'_, '_>,
-        error: &Option<anyhow::Error>,
-    ) -> CargoResult<()> {
+    fn report_html(&self, cx: &Context<'_, '_>, error: &Option<anyhow::Error>) -> CargoResult<()> {
         let duration = self.start.elapsed().as_secs_f64();
         let timestamp = self.start_str.replace(&['-', ':'][..], "");
-        let filename = format!("cargo-timing-{}.html", timestamp);
+        let timings_path = cx.files().host_root().join("cargo-timings");
+        paths::create_dir_all(&timings_path)?;
+        let filename = timings_path.join(format!("cargo-timing-{}.html", timestamp));
         let mut f = BufWriter::new(paths::create(&filename)?);
         let roots: Vec<&str> = self
             .root_targets
@@ -325,7 +323,7 @@ impl<'cfg> Timings<'cfg> {
             .map(|(name, _targets)| name.as_str())
             .collect();
         f.write_all(HTML_TMPL.replace("{ROOTS}", &roots.join(", ")).as_bytes())?;
-        self.write_summary_table(&mut f, duration, bcx, error)?;
+        self.write_summary_table(&mut f, duration, cx.bcx, error)?;
         f.write_all(HTML_CANVAS.as_bytes())?;
         self.write_unit_table(&mut f)?;
         // It helps with pixel alignment to use whole numbers.
@@ -353,7 +351,8 @@ impl<'cfg> Timings<'cfg> {
                 .join(&filename)
                 .display()
         );
-        paths::link_or_copy(&filename, "cargo-timing.html")?;
+        let unstamped_filename = timings_path.join("cargo-timing.html");
+        paths::link_or_copy(&filename, &unstamped_filename)?;
         self.config
             .shell()
             .status_with_color("Timing", msg, termcolor::Color::Cyan)?;

src/doc/man/generated_txt/cargo-bench.txt

@@ -226,10 +226,11 @@ OPTIONS
            will default to --timing=html. Valid output formats:
 
            o  html: Write a human-readable file cargo-timing.html to the
-              current directory with a report of the compilation. Also write a
-              report with a timestamp in the filename if you want to look at
-              older runs. HTML output is suitable for human consumption only,
-              and does not provide machine-readable timing data.
+              target/cargo-timings directory with a report of the compilation.
+              Also write a report to the same directory with a timestamp in the
+              filename if you want to look at older runs. HTML output is
+              suitable for human consumption only, and does not provide
+              machine-readable timing data.
 
            o  json (unstable, requires -Zunstable-options): Emit
               machine-readable JSON information about timing information.

src/doc/man/generated_txt/cargo-build.txt

@@ -163,10 +163,11 @@ OPTIONS
            will default to --timing=html. Valid output formats:
 
            o  html: Write a human-readable file cargo-timing.html to the
-              current directory with a report of the compilation. Also write a
-              report with a timestamp in the filename if you want to look at
-              older runs. HTML output is suitable for human consumption only,
-              and does not provide machine-readable timing data.
+              target/cargo-timings directory with a report of the compilation.
+              Also write a report to the same directory with a timestamp in the
+              filename if you want to look at older runs. HTML output is
+              suitable for human consumption only, and does not provide
+              machine-readable timing data.
 
            o  json (unstable, requires -Zunstable-options): Emit
               machine-readable JSON information about timing information.

src/doc/man/generated_txt/cargo-check.txt

@@ -176,10 +176,11 @@ OPTIONS
            will default to --timing=html. Valid output formats:
 
            o  html: Write a human-readable file cargo-timing.html to the
-              current directory with a report of the compilation. Also write a
-              report with a timestamp in the filename if you want to look at
-              older runs. HTML output is suitable for human consumption only,
-              and does not provide machine-readable timing data.
+              target/cargo-timings directory with a report of the compilation.
+              Also write a report to the same directory with a timestamp in the
+              filename if you want to look at older runs. HTML output is
+              suitable for human consumption only, and does not provide
+              machine-readable timing data.
 
            o  json (unstable, requires -Zunstable-options): Emit
               machine-readable JSON information about timing information.

src/doc/man/generated_txt/cargo-doc.txt

@@ -147,10 +147,11 @@ OPTIONS
            will default to --timing=html. Valid output formats:
 
            o  html: Write a human-readable file cargo-timing.html to the
-              current directory with a report of the compilation. Also write a
-              report with a timestamp in the filename if you want to look at
-              older runs. HTML output is suitable for human consumption only,
-              and does not provide machine-readable timing data.
+              target/cargo-timings directory with a report of the compilation.
+              Also write a report to the same directory with a timestamp in the
+              filename if you want to look at older runs. HTML output is
+              suitable for human consumption only, and does not provide
+              machine-readable timing data.
 
            o  json (unstable, requires -Zunstable-options): Emit
               machine-readable JSON information about timing information.

src/doc/man/generated_txt/cargo-fix.txt

@@ -249,10 +249,11 @@ OPTIONS
            will default to --timing=html. Valid output formats:
 
            o  html: Write a human-readable file cargo-timing.html to the
-              current directory with a report of the compilation. Also write a
-              report with a timestamp in the filename if you want to look at
-              older runs. HTML output is suitable for human consumption only,
-              and does not provide machine-readable timing data.
+              target/cargo-timings directory with a report of the compilation.
+              Also write a report to the same directory with a timestamp in the
+              filename if you want to look at older runs. HTML output is
+              suitable for human consumption only, and does not provide
+              machine-readable timing data.
 
            o  json (unstable, requires -Zunstable-options): Emit
               machine-readable JSON information about timing information.

src/doc/man/generated_txt/cargo-install.txt

@@ -212,10 +212,11 @@ OPTIONS
            will default to --timing=html. Valid output formats:
 
            o  html: Write a human-readable file cargo-timing.html to the
-              current directory with a report of the compilation. Also write a
-              report with a timestamp in the filename if you want to look at
-              older runs. HTML output is suitable for human consumption only,
-              and does not provide machine-readable timing data.
+              target/cargo-timings directory with a report of the compilation.
+              Also write a report to the same directory with a timestamp in the
+              filename if you want to look at older runs. HTML output is
+              suitable for human consumption only, and does not provide
+              machine-readable timing data.
 
            o  json (unstable, requires -Zunstable-options): Emit
               machine-readable JSON information about timing information.

src/doc/man/generated_txt/cargo-run.txt

@@ -92,10 +92,11 @@ OPTIONS
            will default to --timing=html. Valid output formats:
 
            o  html: Write a human-readable file cargo-timing.html to the
-              current directory with a report of the compilation. Also write a
-              report with a timestamp in the filename if you want to look at
-              older runs. HTML output is suitable for human consumption only,
-              and does not provide machine-readable timing data.
+              target/cargo-timings directory with a report of the compilation.
+              Also write a report to the same directory with a timestamp in the
+              filename if you want to look at older runs. HTML output is
+              suitable for human consumption only, and does not provide
+              machine-readable timing data.
 
            o  json (unstable, requires -Zunstable-options): Emit
               machine-readable JSON information about timing information.

src/doc/man/generated_txt/cargo-rustc.txt

@@ -171,10 +171,11 @@ OPTIONS
            will default to --timing=html. Valid output formats:
 
            o  html: Write a human-readable file cargo-timing.html to the
-              current directory with a report of the compilation. Also write a
-              report with a timestamp in the filename if you want to look at
-              older runs. HTML output is suitable for human consumption only,
-              and does not provide machine-readable timing data.
+              target/cargo-timings directory with a report of the compilation.
+              Also write a report to the same directory with a timestamp in the
+              filename if you want to look at older runs. HTML output is
+              suitable for human consumption only, and does not provide
+              machine-readable timing data.
 
            o  json (unstable, requires -Zunstable-options): Emit
               machine-readable JSON information about timing information.

src/doc/man/generated_txt/cargo-rustdoc.txt

@@ -163,10 +163,11 @@ OPTIONS
            will default to --timing=html. Valid output formats:
 
            o  html: Write a human-readable file cargo-timing.html to the
-              current directory with a report of the compilation. Also write a
-              report with a timestamp in the filename if you want to look at
-              older runs. HTML output is suitable for human consumption only,
-              and does not provide machine-readable timing data.
+              target/cargo-timings directory with a report of the compilation.
+              Also write a report to the same directory with a timestamp in the
+              filename if you want to look at older runs. HTML output is
+              suitable for human consumption only, and does not provide
+              machine-readable timing data.
 
            o  json (unstable, requires -Zunstable-options): Emit
               machine-readable JSON information about timing information.

src/doc/man/generated_txt/cargo-test.txt

@@ -240,10 +240,11 @@ OPTIONS
            will default to --timing=html. Valid output formats:
 
            o  html: Write a human-readable file cargo-timing.html to the
-              current directory with a report of the compilation. Also write a
-              report with a timestamp in the filename if you want to look at
-              older runs. HTML output is suitable for human consumption only,
-              and does not provide machine-readable timing data.
+              target/cargo-timings directory with a report of the compilation.
+              Also write a report to the same directory with a timestamp in the
+              filename if you want to look at older runs. HTML output is
+              suitable for human consumption only, and does not provide
+              machine-readable timing data.
 
            o  json (unstable, requires -Zunstable-options): Emit
               machine-readable JSON information about timing information.

src/doc/man/includes/options-timings.md

@@ -4,11 +4,11 @@ information over time. Accepts an optional comma-separated list of output
 formats; `--timing` without an argument will default to `--timing=html`. Valid
 output formats:
 
-- `html`: Write a human-readable file `cargo-timing.html` to the current
-  directory with a report of the compilation. Also write a report with a
-  timestamp in the filename if you want to look at older runs. HTML output is
-  suitable for human consumption only, and does not provide machine-readable
-  timing data.
+- `html`: Write a human-readable file `cargo-timing.html` to the
+  `target/cargo-timings` directory with a report of the compilation. Also write
+  a report to the same directory with a timestamp in the filename if you want
+  to look at older runs. HTML output is suitable for human consumption only,
+  and does not provide machine-readable timing data.
 - `json` (unstable, requires `-Zunstable-options`): Emit machine-readable JSON
   information about timing information.
 {{/option}}

src/doc/src/commands/cargo-bench.md

@@ -271,11 +271,11 @@ information over time. Accepts an optional comma-separated list of output
 formats; <code>--timing</code> without an argument will default to <code>--timing=html</code>. Valid
 output formats:</p>
 <ul>
-<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine-readable
-timing data.</li>
+<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the
+<code>target/cargo-timings</code> directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine-readable timing data.</li>
 <li><code>json</code> (unstable, requires <code>-Zunstable-options</code>): Emit machine-readable JSON
 information about timing information.</li>
 </ul></dd>

src/doc/src/commands/cargo-build.md

@@ -206,11 +206,11 @@ information over time. Accepts an optional comma-separated list of output
 formats; <code>--timing</code> without an argument will default to <code>--timing=html</code>. Valid
 output formats:</p>
 <ul>
-<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine-readable
-timing data.</li>
+<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the
+<code>target/cargo-timings</code> directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine-readable timing data.</li>
 <li><code>json</code> (unstable, requires <code>-Zunstable-options</code>): Emit machine-readable JSON
 information about timing information.</li>
 </ul></dd>

src/doc/src/commands/cargo-check.md

@@ -215,11 +215,11 @@ information over time. Accepts an optional comma-separated list of output
 formats; <code>--timing</code> without an argument will default to <code>--timing=html</code>. Valid
 output formats:</p>
 <ul>
-<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine-readable
-timing data.</li>
+<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the
+<code>target/cargo-timings</code> directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine-readable timing data.</li>
 <li><code>json</code> (unstable, requires <code>-Zunstable-options</code>): Emit machine-readable JSON
 information about timing information.</li>
 </ul></dd>

src/doc/src/commands/cargo-doc.md

@@ -189,11 +189,11 @@ information over time. Accepts an optional comma-separated list of output
 formats; <code>--timing</code> without an argument will default to <code>--timing=html</code>. Valid
 output formats:</p>
 <ul>
-<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine-readable
-timing data.</li>
+<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the
+<code>target/cargo-timings</code> directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine-readable timing data.</li>
 <li><code>json</code> (unstable, requires <code>-Zunstable-options</code>): Emit machine-readable JSON
 information about timing information.</li>
 </ul></dd>

src/doc/src/commands/cargo-fix.md

@@ -295,11 +295,11 @@ information over time. Accepts an optional comma-separated list of output
 formats; <code>--timing</code> without an argument will default to <code>--timing=html</code>. Valid
 output formats:</p>
 <ul>
-<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine-readable
-timing data.</li>
+<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the
+<code>target/cargo-timings</code> directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine-readable timing data.</li>
 <li><code>json</code> (unstable, requires <code>-Zunstable-options</code>): Emit machine-readable JSON
 information about timing information.</li>
 </ul></dd>

src/doc/src/commands/cargo-install.md

@@ -242,11 +242,11 @@ information over time. Accepts an optional comma-separated list of output
 formats; <code>--timing</code> without an argument will default to <code>--timing=html</code>. Valid
 output formats:</p>
 <ul>
-<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine-readable
-timing data.</li>
+<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the
+<code>target/cargo-timings</code> directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine-readable timing data.</li>
 <li><code>json</code> (unstable, requires <code>-Zunstable-options</code>): Emit machine-readable JSON
 information about timing information.</li>
 </ul></dd>

src/doc/src/commands/cargo-run.md

@@ -124,11 +124,11 @@ information over time. Accepts an optional comma-separated list of output
 formats; <code>--timing</code> without an argument will default to <code>--timing=html</code>. Valid
 output formats:</p>
 <ul>
-<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine-readable
-timing data.</li>
+<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the
+<code>target/cargo-timings</code> directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine-readable timing data.</li>
 <li><code>json</code> (unstable, requires <code>-Zunstable-options</code>): Emit machine-readable JSON
 information about timing information.</li>
 </ul></dd>

src/doc/src/commands/cargo-rustc.md

@@ -203,11 +203,11 @@ information over time. Accepts an optional comma-separated list of output
 formats; <code>--timing</code> without an argument will default to <code>--timing=html</code>. Valid
 output formats:</p>
 <ul>
-<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine-readable
-timing data.</li>
+<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the
+<code>target/cargo-timings</code> directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine-readable timing data.</li>
 <li><code>json</code> (unstable, requires <code>-Zunstable-options</code>): Emit machine-readable JSON
 information about timing information.</li>
 </ul></dd>

src/doc/src/commands/cargo-rustdoc.md

@@ -208,11 +208,11 @@ information over time. Accepts an optional comma-separated list of output
 formats; <code>--timing</code> without an argument will default to <code>--timing=html</code>. Valid
 output formats:</p>
 <ul>
-<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine-readable
-timing data.</li>
+<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the
+<code>target/cargo-timings</code> directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine-readable timing data.</li>
 <li><code>json</code> (unstable, requires <code>-Zunstable-options</code>): Emit machine-readable JSON
 information about timing information.</li>
 </ul></dd>

src/doc/src/commands/cargo-test.md

@@ -287,11 +287,11 @@ information over time. Accepts an optional comma-separated list of output
 formats; <code>--timing</code> without an argument will default to <code>--timing=html</code>. Valid
 output formats:</p>
 <ul>
-<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine-readable
-timing data.</li>
+<li><code>html</code>: Write a human-readable file <code>cargo-timing.html</code> to the
+<code>target/cargo-timings</code> directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine-readable timing data.</li>
 <li><code>json</code> (unstable, requires <code>-Zunstable-options</code>): Emit machine-readable JSON
 information about timing information.</li>
 </ul></dd>

src/etc/man/cargo-bench.1

@@ -277,11 +277,11 @@ formats; \fB\-\-timing\fR without an argument will default to \fB\-\-timing=html
 output formats:
 .sp
 .RS 4
-\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine\-readable
-timing data.
+\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the
+\fBtarget/cargo\-timings\fR directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine\-readable timing data.
 .RE
 .sp
 .RS 4

src/etc/man/cargo-build.1

@@ -196,11 +196,11 @@ formats; \fB\-\-timing\fR without an argument will default to \fB\-\-timing=html
 output formats:
 .sp
 .RS 4
-\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine\-readable
-timing data.
+\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the
+\fBtarget/cargo\-timings\fR directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine\-readable timing data.
 .RE
 .sp
 .RS 4

src/etc/man/cargo-check.1

@@ -207,11 +207,11 @@ formats; \fB\-\-timing\fR without an argument will default to \fB\-\-timing=html
 output formats:
 .sp
 .RS 4
-\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine\-readable
-timing data.
+\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the
+\fBtarget/cargo\-timings\fR directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine\-readable timing data.
 .RE
 .sp
 .RS 4

src/etc/man/cargo-doc.1

@@ -174,11 +174,11 @@ formats; \fB\-\-timing\fR without an argument will default to \fB\-\-timing=html
 output formats:
 .sp
 .RS 4
-\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine\-readable
-timing data.
+\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the
+\fBtarget/cargo\-timings\fR directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine\-readable timing data.
 .RE
 .sp
 .RS 4

src/etc/man/cargo-fix.1

@@ -302,11 +302,11 @@ formats; \fB\-\-timing\fR without an argument will default to \fB\-\-timing=html
 output formats:
 .sp
 .RS 4
-\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine\-readable
-timing data.
+\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the
+\fBtarget/cargo\-timings\fR directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine\-readable timing data.
 .RE
 .sp
 .RS 4

src/etc/man/cargo-install.1

@@ -275,11 +275,11 @@ formats; \fB\-\-timing\fR without an argument will default to \fB\-\-timing=html
 output formats:
 .sp
 .RS 4
-\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine\-readable
-timing data.
+\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the
+\fBtarget/cargo\-timings\fR directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine\-readable timing data.
 .RE
 .sp
 .RS 4

src/etc/man/cargo-run.1

@@ -107,11 +107,11 @@ formats; \fB\-\-timing\fR without an argument will default to \fB\-\-timing=html
 output formats:
 .sp
 .RS 4
-\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine\-readable
-timing data.
+\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the
+\fBtarget/cargo\-timings\fR directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine\-readable timing data.
 .RE
 .sp
 .RS 4

src/etc/man/cargo-rustc.1

@@ -202,11 +202,11 @@ formats; \fB\-\-timing\fR without an argument will default to \fB\-\-timing=html
 output formats:
 .sp
 .RS 4
-\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine\-readable
-timing data.
+\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the
+\fBtarget/cargo\-timings\fR directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine\-readable timing data.
 .RE
 .sp
 .RS 4

src/etc/man/cargo-rustdoc.1

@@ -193,11 +193,11 @@ formats; \fB\-\-timing\fR without an argument will default to \fB\-\-timing=html
 output formats:
 .sp
 .RS 4
-\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine\-readable
-timing data.
+\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the
+\fBtarget/cargo\-timings\fR directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine\-readable timing data.
 .RE
 .sp
 .RS 4

src/etc/man/cargo-test.1

@@ -293,11 +293,11 @@ formats; \fB\-\-timing\fR without an argument will default to \fB\-\-timing=html
 output formats:
 .sp
 .RS 4
-\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the current
-directory with a report of the compilation. Also write a report with a
-timestamp in the filename if you want to look at older runs. HTML output is
-suitable for human consumption only, and does not provide machine\-readable
-timing data.
+\h'-04'\(bu\h'+02'\fBhtml\fR: Write a human\-readable file \fBcargo\-timing.html\fR to the
+\fBtarget/cargo\-timings\fR directory with a report of the compilation. Also write
+a report to the same directory with a timestamp in the filename if you want
+to look at older runs. HTML output is suitable for human consumption only,
+and does not provide machine\-readable timing data.
 .RE
 .sp
 .RS 4

tests/testsuite/timings.rs

@@ -34,7 +34,7 @@ fn timings_works() {
 [COMPILING] dep v0.1.0
 [COMPILING] foo v0.1.0 [..]
 [FINISHED] [..]
-      Timing report saved to [..]/foo/cargo-timing-[..].html
+      Timing report saved to [..]/foo/target/cargo-timings/cargo-timing-[..].html
 ",
         )
         .run();