<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>src/doc/man/includes/options-keep-going.md - fork/cargo @ home-0.5.12</title>
<meta name="description" content="src/doc/man/includes/options-keep-going.md in fork/cargo at home-0.5.12.">
<meta property="og:title" content="src/doc/man/includes/options-keep-going.md - fork/cargo @ home-0.5.12">
<meta property="og:description" content="src/doc/man/includes/options-keep-going.md in fork/cargo at home-0.5.12.">
<meta property="og:type" content="website">
<meta property="og:site_name" content="git.julia.blue">
<link rel="stylesheet" href="/css/style.css?v=62">
<script type="module" src="/js/main.js?v=62"></script>
</head>
<body>
<main data-ref="home-0.5.12" data-tip="4f15cc8882fb34bf70c945e9c8ae91d6c8c91757">
<noscript>
  <div class="callout">
    <p>
      hey! this is a static git repo viewer. commit diffs, file history,
      older commits and other revisions won't load without javascript.
    </p>
    <p>
      you are still able to view source files on branch/tag tips,
      but the experience is degraded.
    </p>
  </div>
</noscript>
<header class="repo"><div>
<h1>fork/cargo</h1>
</div>
<pre class="clone">git clone https://git.julia.blue/fork/cargo</pre>
</header>
<p class="snapshot-commit"><span class="commit-author">bors</span><span class="commit-message" data-commit="2a6f7f6efe118ed9b82dfff4591fac70b4bca790">Auto merge of #12568 - dtolnay-contrib:keepgoing, r=weihanglo</span><span class="snapshot-sha sha" data-commit="2a6f7f6efe118ed9b82dfff4591fac70b4bca790">2a6f7f6ef</span><time datetime="2023-08-26T20:44:24+00:00" title="2023-08-26 20:44:24 +0000">2023-08-26</time></p>
<header class="topbar"><details class="switcher"><summary>home-0.5.12</summary><div class="menu"><strong>branches</strong><a href="/fork/cargo/ref/master/">master</a><strong>tags</strong><a href="/fork/cargo/ref/0.87.0/">0.87.0</a><a href="/fork/cargo/ref/0.88.0/">0.88.0</a><a href="/fork/cargo/ref/0.89.0/">0.89.0</a><a href="/fork/cargo/ref/0.90.0/">0.90.0</a><a href="/fork/cargo/ref/0.91.0/">0.91.0</a><a href="/fork/cargo/ref/0.92.0/">0.92.0</a><a href="/fork/cargo/ref/0.93.0/">0.93.0</a><a class="current" href="/fork/cargo/ref/home-0.5.12/">home-0.5.12</a><a class="all" href="/fork/cargo/refs">all refs →</a></div></details><nav class="crumbs"><a href="/fork/cargo/">cargo</a> / <a href="/fork/cargo/ref/home-0.5.12/tree/src/">src</a> / <a href="/fork/cargo/ref/home-0.5.12/tree/src/doc/">doc</a> / <a href="/fork/cargo/ref/home-0.5.12/tree/src/doc/man/">man</a> / <a href="/fork/cargo/ref/home-0.5.12/tree/src/doc/man/includes/">includes</a> / <span class="cur">options-keep-going.md</span></nav>
<span class="view-stats"><span>527 B</span><span>10 lines</span></span><span class="actions"><a class="raw" href="/fork/cargo/raw/928c7f67a7facd3db0625df636bd3852f97cc6a1/src/doc/man/includes/options-keep-going.md">raw</a></span></header>
<div class="markdown-view"><input type="radio" name="markdown-view" id="markdown-rendered" checked><label for="markdown-rendered">rendered</label><input type="radio" name="markdown-view" id="markdown-code"><label for="markdown-code">code</label><section class="readme rendered"><p>{{#option "<code>--keep-going</code>"}}
Build as many crates in the dependency graph as possible, rather than aborting
the build on the first one that fails to build.</p>
<p>For example if the current package depends on dependencies <code>fails</code> and <code>works</code>,
one of which fails to build, <code>cargo {{command}} -j1</code> may or may not build the
one that succeeds (depending on which one of the two builds Cargo picked to run
first), whereas <code>cargo {{command}} -j1 --keep-going</code> would definitely run both
builds, even if the one run first fails.
{{/option}}</p>
</section><div class="code-panel"><pre class="code src language-markdown"><span class="code-line"><a class="ln" id="L1" href="#L1">1</a><span class="code-text">{{#option &quot;`--keep-going`&quot;}}</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L2" href="#L2">2</a><span class="code-text">Build as many crates in the dependency graph as possible, rather than aborting</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L3" href="#L3">3</a><span class="code-text">the build on the first one that fails to build.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L4" href="#L4">4</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L5" href="#L5">5</a><span class="code-text">For example if the current package depends on dependencies `fails` and `works`,</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L6" href="#L6">6</a><span class="code-text">one of which fails to build, `cargo {{command}} -j1` may or may not build the</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L7" href="#L7">7</a><span class="code-text">one that succeeds (depending on which one of the two builds Cargo picked to run</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L8" href="#L8">8</a><span class="code-text">first), whereas `cargo {{command}} -j1 --keep-going` would definitely run both</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L9" href="#L9">9</a><span class="code-text">builds, even if the one run first fails.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L10" href="#L10">10</a><span class="code-text">{{/option}}</span></span></pre></div></div>
</main>
</body>
</html>
