tag:help.appveyor.com,2012-11-13:/discussions/problems/19657-successful-builds-failing-with-code-259AppVeyor: Discussion 2019-03-31T21:58:58Ztag:help.appveyor.com,2012-11-13:Comment/468724952019-01-25T15:09:39Z2019-01-25T15:09:39ZSuccessful builds failing with code 259<div><p>We've recently had two builds that seem to fail spuriously:</p>
<ul>
<li><a href="https://ci.appveyor.com/project/rust-lang/rust/builds/21878200/job/vqa2839nswaupw99">https://ci.appveyor.com/project/rust-lang/rust/builds/21878200/job/...</a></li>
<li><a href="https://ci.appveyor.com/project/rust-lang/rust/builds/21780625/job/imgk0ynpscqfioay">https://ci.appveyor.com/project/rust-lang/rust/builds/21780625/job/...</a></li>
</ul>
<p>where both report that they're failing with exit code 259, but according to the logs it looks like the build completed successfully (and the relevant code later landed without changes and passed all tests). We noticed that on Windows 259 corresponds to <code>STILL_ACTIVE</code> which may mean that a process isn't ready for exiting and it needs to be reaped later, so we were wondering if this is a possible bug in AppVeyor's harness?</p></div>acrichtontag:help.appveyor.com,2012-11-13:Comment/468724952019-01-25T21:47:04Z2019-01-25T21:47:04ZSuccessful builds failing with code 259<div><p>Hi Alex,</p>
<p>We took a look into this issue. Let me please share our observations:</p>
<ul>
<li>
<p>Issue happens with always with the same job (<code>CI_JOB_NAME=x86_64-mingw</code>).</p>
</li>
<li>
<p>AppVeyor build worker image was last updated before this started happening.</p>
</li>
<li>
<p>There are no specific Hyper-V node where it happens.</p>
</li>
<li>
<p>External dependency downloaded are the same between recent "green" and "red" jobs.</p>
</li>
<li>
<p>Per my understanding exit code 259 means that caller started child process, and exiting without waiting that child process to complete, as described in <a href="https://social.technet.microsoft.com/Forums/systemcenter/en-US/fbccc114-3605-4363-b983-b2f7b02fe266/program-exit-code-259-in-sccm-cllient?forum=configmgrswdist">this</a> discussion.</p>
</li>
<li>
<p>AppVeyor interprets any exit code other than zero as error.</p>
</li>
</ul>
<p>It can be that some external dependency specific to this <code>CI_JOB_NAME=x86_64-mingw</code> changed. Those two builds which mention are the first ones who failed this way? Can you think of specific downloadable dependency to check?</p>
<p>As a workaround you can catch exit code 259 and return 0 as 259 is not really a failure.</p>
<p>Side note: we recently implemented <code>RE-RUN INCOMPLETE</code> button so you can rerun build failed this way and only failed and cancelled jobs will be executed.</p>
<p>Ilya.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-01-25T22:46:11Z2019-01-25T22:46:11ZSuccessful builds failing with code 259<div><p>Hm interesting, thanks for the info! Since this is a spurious error, it may also be the case that a previous update to the image didn't show up until now. Looking more into this though, we print the "test run finished successfully" message at the end, and then the sequence of events are:</p>
<ul>
<li>The Python interpreter which ran the whole test suite exits, hopefully with error code 0</li>
<li>An invocation of <code>sh -x -c "$FOO"</code> is now unblocked that <code>$FOO</code> (the python interpreter) has exited</li>
<li>An invocation of <code>bash src/ci/run.sh</code> is then unblocked as the CI run script exits</li>
<li>After that, control is yielded back to AppVeyor as we don't have any further items configured in the <code>test_script</code> section of our <code>appveyor.yml</code>.</li>
</ul>
<p>The three components which are reaping processes <em>after</em> the success message is printed are <code>sh.exe</code>, <code>bash.exe</code>, and AppVeyor's runner as well (I think maybe <code>cmd.exe</code> for us?). It's probably not a bug in <code>cmd.exe</code>, so this may just be a bug in <code>sh.exe</code> or <code>bash.exe</code> which we haven't ever run into before.</p>
<p>I think we're using <code>sh.exe</code> and <code>bash.exe</code> from the environment by putting <code>C:\msys64\usr\bin</code>, do you know if those have changed at all recently?</p>
<p>Apart from that I'm not really sure where this could be showing up :(. AFAIK nothing we download could have changed to have caused this, but I've been wrong before!</p></div>acrichtontag:help.appveyor.com,2012-11-13:Comment/468724952019-01-29T03:44:37Z2019-01-29T03:44:56ZSuccessful builds failing with code 259<div><p>Can you try to check and print exit code of <code>sh -x -c "$FOO"</code>? It is <a href="https://github.com/rust-lang/rust/blob/auto/src/ci/run.sh#L124">here</a>, correct?</p>
<p>Side note: Two jobs in latest build (<a href="https://ci.appveyor.com/project/rust-lang/rust/builds/21954146">https://ci.appveyor.com/project/rust-lang/rust/builds/21954146</a>) failed because of issue on our side. Sorry for the trouble. Can you please use <code>RE-BUILD INCOMPLETE</code> button to rerun those jobs?</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-01-29T15:47:40Z2019-01-29T15:47:40ZSuccessful builds failing with code 259<div><p>Sure yeah, I've <a href="https://github.com/rust-lang/rust/pull/57975">added some debugging</a> to hopefully see what comes out.</p>
<p>Ah I was a bit slow on those reruns! Our infrastructure workflow isn't currently architected well enough to take advantage of that, but we'll be sure to keep that in mind :)</p></div>acrichtontag:help.appveyor.com,2012-11-13:Comment/468724952019-01-29T22:15:27Z2019-01-29T22:15:27ZSuccessful builds failing with code 259<div><p>You can use <a href="https://www.appveyor.com/docs/api/projects-builds/#re-run-build">this API</a> with <code>reRunIncomplete: True</code>.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-02-04T18:36:53Z2019-02-27T23:08:18ZSuccessful builds failing with code 259<div><p>Hi! I'm Pietro from the Rust infrastructure team.</p>
<p>After we <a href="https://github.com/rust-lang/rust/pull/57975">added the debugging code</a> we hit the same failure again in <a href="https://ci.appveyor.com/project/rust-lang/rust/builds/22108226/job/3xfgih9g5xx3oa42#L25098">https://ci.appveyor.com/project/rust-lang/rust/builds/22108226/job/...</a>. The relevant log messages are:</p>
<pre>
<code>Build completed successfully in 2:59:39
script exited with 0
Command exited with code 259</code>
</pre>
<p>So that's not the problem. I opened another PR to <a href="https://github.com/rust-lang/rust/pull/58162">add the same debugging code to appveyor.yml</a> if we can get relevant information outside of it.</p></div>pietroalbinitag:help.appveyor.com,2012-11-13:Comment/468724952019-02-04T21:44:47Z2019-02-04T21:44:47ZSuccessful builds failing with code 259<div><p>Hi Pietro,</p>
<p>Thanks a lot for the update. I would also ask to add the following commands into the end of <code>run.sh</code> file:</p>
<pre>
<code>tasklist
where sh</code>
</pre>
<p>We would compare <code>tasklist</code> output between "good" and "bad" builds in hope to get some idea what is the process spawned by <code>sh</code> not closed by the end of it's run (probable reason for exit code 259).</p>
<p><code>where sh</code> should display us where shell is being called from. Your configuration is quite involved and it is better to double-check which <code>sh.exe</code> is running.</p>
<p>Ilya.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-02-05T08:23:40Z2019-02-27T23:08:19ZSuccessful builds failing with code 259<div><p>Thanks! Added the two commands at the bot of <code>run.sh</code>, let's see how it goes.</p>
<p>Pietro.</p></div>pietroalbinitag:help.appveyor.com,2012-11-13:Comment/468724952019-02-06T13:53:58Z2019-02-27T23:08:19ZSuccessful builds failing with code 259<div><p>We added the code to our CI, but comparing <a href="https://ci.appveyor.com/project/rust-lang/rust/builds/22160798/job/1ba9276qcta1r1dm">a good build</a>'s tasklist and <a href="https://ci.appveyor.com/project/rust-lang/rust/builds/22130039/job/rrcldbj9re8q6asm">a bad build</a>'s tasklist doesn't show anything useful (it's the same list of processes). The output of <code>which sh</code> is:</p>
<pre>
<code>C:\msys64\usr\bin\sh.exe
C:\Program Files\Git\usr\bin\sh.exe</code>
</pre></div>pietroalbinitag:help.appveyor.com,2012-11-13:Comment/468724952019-02-13T00:02:19Z2019-02-13T00:02:19ZSuccessful builds failing with code 259<div><p>Hi Pietro,</p>
<p>My apologies, missed this message. Do you still have this issue? Did it happen during last day (asking in hope that <a href="https://www.appveyor.com/updates/2019/02/11/">recent update</a> somehow fixed it)? And can you try to use <code>C:\Program Files\Git\usr\bin\sh.exe</code> (which is default on AppVeyor image) to execute <code>run.sh</code>.</p>
<p>Sorry for "try this and that" approach -- It is the kind of issue we have no clear idea...</p>
<p>Ilya.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-02-13T18:55:11Z2019-02-13T18:55:11ZSuccessful builds failing with code 259<div><p>We had a build <a href="https://ci.appveyor.com/project/rust-lang/rust/builds/22312647/job/8emwwm2idrbu3dd5">fail yesterday</a> which I think was after the update, so unfortunately looks like that didn't fix it. I'll switch over to git's <code>sh.exe</code> and see how that works.</p>
<p>No worries as well, I'm just glad you've got ideas of how we can try different things because we ran out!</p></div>acrichtontag:help.appveyor.com,2012-11-13:Comment/468724952019-02-14T14:33:58Z2019-02-14T14:33:58ZSuccessful builds failing with code 259<div><p>I'm certainly no expert on <code>sh.exe</code> on Windows, but <a href="https://ci.appveyor.com/project/rust-lang/rust/builds/22356904/job/5fpl4d9p9j280hy3">this error we got</a> looks like <code>sh.exe</code> from git is incompatible with also having msys64 items in PATH unfortunately :(</p></div>acrichtontag:help.appveyor.com,2012-11-13:Comment/468724952019-02-15T19:53:34Z2019-02-15T19:53:34ZSuccessful builds failing with code 259<div><p>Hmm, when this error happened first time?</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-02-15T22:19:05Z2019-02-15T22:19:05ZSuccessful builds failing with code 259<div><p>Searching back a bit, and this is by no means exhaustive, the earliest instance I could fine was <a href="https://ci.appveyor.com/project/rust-lang/rust/builds/21780625/job/imgk0ynpscqfioay">25 days ago</a></p></div>acrichtontag:help.appveyor.com,2012-11-13:Comment/468724952019-02-19T05:22:29Z2019-02-19T05:22:29ZSuccessful builds failing with code 259<div><p>Hi Alex,</p>
<p>Can it be about the same time you switched to Hyper-V from GCE? Can you please try to switch back to GCE again for a while to see how it is going to behave?</p>
<p>Sorry once again for back-and-forth...</p>
<p>Ilya.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-02-20T18:03:00Z2019-02-20T18:03:00ZSuccessful builds failing with code 259<div><p>A good point! We're trying that with <a href="https://github.com/rust-lang/rust/pull/58597">https://github.com/rust-lang/rust/pull/58597</a> and we'll watch for a few days to see if a spurious error crops up</p></div>acrichtontag:help.appveyor.com,2012-11-13:Comment/468724952019-02-27T23:10:16Z2019-02-27T23:10:16ZSuccessful builds failing with code 259<div><p>Happened again after switching back to GCE:<br>
<a href="https://ci.appveyor.com/project/rust-lang/rust/builds/22698401/job/9isfhkwxoym4qf5x">https://ci.appveyor.com/project/rust-lang/rust/builds/22698401/job/...</a><br>
Do you recommend switching back to Hyper-V?</p>
<p>Pietro.</p></div>pietroalbinitag:help.appveyor.com,2012-11-13:Comment/468724952019-02-28T23:50:55Z2019-02-28T23:50:55ZSuccessful builds failing with code 259<div><p>Yes, let us please switch back to Hyper-V then. It's a shame, but can I propose to catch and swallow this exit code (as it is not actually an error)?</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-03-01T14:55:25Z2019-03-01T14:55:25ZSuccessful builds failing with code 259<div><p>We're switching over in <a href="https://github.com/rust-lang/rust/pull/58832">https://github.com/rust-lang/rust/pull/58832</a> back to Hyper-V</p></div>acrichtontag:help.appveyor.com,2012-11-13:Comment/468724952019-03-01T14:57:48Z2019-03-01T14:57:48ZSuccessful builds failing with code 259<div><p>FWIW we still also don't really know where code 259 comes from. Given the <a href="https://docs.microsoft.com/en-us/windows/desktop/api/processthreadsapi/nf-processthreadsapi-getexitcodeprocess">documentation on <code>GetExitCodeProcess</code></a> of how <code>STILL_ACTIVE</code> maps to 259 and it's easily confused I suspect that very few tools in the wild end up using 259 as an actual exit code.</p>
<p>One of the worrisome parts, though, is that this still looks like <em>something</em> in the stack isn't actually waiting for a process to exit and is getting <code>STILL_ACTIVE</code> instead of a real exit code, so presumably if 259 was accepted as an 'ok status code' it could both mean that the build exited successfully but it could also mean that it failed in theory with the real erroneous status code not yet learned...</p></div>acrichtontag:help.appveyor.com,2012-11-13:Comment/468724952019-03-04T14:17:17Z2019-03-04T14:17:18ZSuccessful builds failing with code 259<div><p>This job just failed with the same error code as well:<br>
<a href="https://ci.appveyor.com/project/rust-lang/rust/builds/22799667/job/op9t2fuk0d4u7skb">https://ci.appveyor.com/project/rust-lang/rust/builds/22799667/job/...</a></p></div>Tim Diekmanntag:help.appveyor.com,2012-11-13:Comment/468724952019-03-05T18:49:27Z2019-03-05T18:49:28ZSuccessful builds failing with code 259<div><p>We did some more brainstorming on this issue, and we noticed two things: all the failures we could find happened after 3 hours, and we have <a href="https://github.com/rust-lang/rust/blob/f22dca0a1bef4141e75326caacc3cd59f3d5be8e/src/ci/run.sh#L78-L82">a daemon that stops exactly after 3 hours</a>. We sent a PR that increases its shutdown time to 10 hours, so <em>hopefully</em> that will fix it...</p>
<p>We'll keep you posted.</p></div>pietroalbinitag:help.appveyor.com,2012-11-13:Comment/468724952019-03-05T21:09:33Z2019-03-05T21:09:33ZSuccessful builds failing with code 259<div><p>Thanks a lot for keeping us in touch! Yes, this feels like a promising change.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-03-06T19:13:51Z2019-03-06T19:13:53ZSuccessful builds failing with code 259<div><p>Aaaaand... the PR increasing the sccache stop time failed with exit code 259. Great.<br>
We're trying to contact some friends at Microsoft to see if we can get at the bottom of this.</p>
<p>Pietro</p></div>pietroalbinitag:help.appveyor.com,2012-11-13:Comment/468724952019-03-06T21:20:20Z2019-03-06T21:20:22ZSuccessful builds failing with code 259<div><p>@Ilya seems like no build longer than 3 hours passed in the last two months, and most of them failed with 259. Could there be an "hidden" timeout for the test_script phase that causes the 259 after 3 hours?</p></div>pietroalbinitag:help.appveyor.com,2012-11-13:Comment/468724952019-03-07T00:42:23Z2019-03-07T00:42:23ZSuccessful builds failing with code 259<div><p>There are actually successful builds builds longer than 3 hours like <a href="https://ci.appveyor.com/project/rust-lang/rust/build/1.0.11012/job/g9d41uboaoktkb9m">this</a> and <a href="https://ci.appveyor.com/project/rust-lang/rust/build/1.0.11014/job/a5w9e45t1j7xm3w2">this</a>... But I think you meant not the whole build, but time taken by <code>run.sh</code>. In this case I agree.</p>
<p>We do not have any hidden build-stage-specific timeouts.</p>
<p>Did you try to see if this can be commit-specific? With <code>RE-RUN INCOMPLETE</code> button you can rerun only failed (and cancelled) build jobs in the matrix without consuming build jobs unnecessary. Chances that it is commit specific are slim, but I would try just to ensure.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-03-07T14:57:26Z2019-03-07T14:57:27ZSuccessful builds failing with code 259<div><p>We did some more digging into this, and apparently a builder that installs some programs (an oversight on our end, we forgot to remove the steps before testing) and then sleeps for 3.5 hours still causes a 259:</p>
<p><a href="https://ci.appveyor.com/project/rust-lang/rust/build/job/ts7uftc0csamtsak">https://ci.appveyor.com/project/rust-lang/rust/build/job/ts7uftc0cs...</a></p>
<p>We're going to dig into this a bit more, but I'm pretty confident this is a bug on your end.</p></div>pietroalbinitag:help.appveyor.com,2012-11-13:Comment/468724952019-03-07T18:37:46Z2019-03-07T18:37:46ZSuccessful builds failing with code 259<div><p><strong>@pietroalbini</strong>: I started the same experiment but with your script re-written in PowerShell:</p>
<ul>
<li>build: <a href="https://ci.appveyor.com/project/IlyaFinkelshteyn/test-project/builds/22907755">https://ci.appveyor.com/project/IlyaFinkelshteyn/test-project/build...</a></li>
<li>script: <a href="https://github.com/IlyaFinkelshteyn/test-project/blob/master/run.ps1">https://github.com/IlyaFinkelshteyn/test-project/blob/master/run.ps1</a></li>
</ul>
<p>Doing this to check if this bash-specific issue or not. I start suspecting that it is bash-specific and can be related to the MSYS2 update we deployed in November:</p>
<ul>
<li>issue: <a href="https://github.com/appveyor/ci/issues/2703">https://github.com/appveyor/ci/issues/2703</a></li>
<li>update: <a href="https://www.appveyor.com/updates/2018/11/09/">https://www.appveyor.com/updates/2018/11/09/</a></li>
</ul>
<p>Is timing of this update fits start of those issues?</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-03-07T20:13:37Z2019-03-07T20:13:39ZSuccessful builds failing with code 259<div><p>Ok, our tests finished and the build that does a 200 minute long sleep failed with 259, while the build that does two 100 minute long sleeps succeeded (the third job is just a failsafe designed to timeout regardless, to avoid merging that PR by accident).</p>
<p><a href="https://ci.appveyor.com/project/rust-lang/rust/builds/22904977/job/nd52fmf5vv44bkp7">https://ci.appveyor.com/project/rust-lang/rust/builds/22904977/job/...</a><br>
<a href="https://ci.appveyor.com/project/rust-lang/rust/build/job/7gap4tqrv577ng8i">https://ci.appveyor.com/project/rust-lang/rust/build/job/7gap4tqrv5...</a></p>
<p>Let's wait to see what your build shows.</p>
<blockquote>
<p>Is timing of this update fits start of those issues?</p>
</blockquote>
<p>I don't <em>remember</em> seeing those back in November, but I don't have any data to confirm this :(</p></div>pietroalbinitag:help.appveyor.com,2012-11-13:Comment/468724952019-03-07T20:16:45Z2019-03-07T20:16:45ZSuccessful builds failing with code 259<div><p>We have another theory (purely our side thing, the way we start external processes like <code>sh</code>) which we are investigating meanwhile. Will keep you updated today. Thanks a lot for the clear repro!</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-03-08T00:05:17Z2019-03-08T00:06:28ZSuccessful builds failing with code 259<div><p>PowerShell-based test did not return this error. However similar internal test based on <code>cmd</code> (not <code>sh</code>) returned 259. So we are convinced that it is an issue on our side, in the way we treat process external to the PowerShell. We will deploy a fix today later.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-03-08T02:20:19Z2019-03-08T02:20:19ZSuccessful builds failing with code 259<div><p>Fix has been deployed. You can re-run your 200-minutes-sleep repro, or simple restore your <code>appveyor.yml</code> and <code>build.sh</code>.</p>
<p>Sorry it took so long to realize the bug -- thanks to your repro.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-03-08T06:53:02Z2019-03-08T06:53:03ZSuccessful builds failing with code 259<div><p>Thank you! I reopened our queue so a PR is now testing, I'll let you know of the results.</p>
<p>Pietro.</p></div>pietroalbinitag:help.appveyor.com,2012-11-13:Comment/468724952019-03-08T16:00:34Z2019-03-08T16:00:36ZSuccessful builds failing with code 259<div><p>Yep, we had a build going over 3 hours and it didn't fail \o/</p>
<p><a href="https://ci.appveyor.com/project/rust-lang/rust/builds/22921540">https://ci.appveyor.com/project/rust-lang/rust/builds/22921540</a></p>
<p>Thanks!<br>
Pietro.</p></div>pietroalbinitag:help.appveyor.com,2012-11-13:Comment/468724952019-03-08T18:14:18Z2019-03-08T18:14:18ZSuccessful builds failing with code 259<div><p>Thanks so much for your persistence, and sorry once again it took this long to check some specific place in our system. Please feel free to ping anytime :)</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-03-11T20:15:08Z2019-03-11T20:15:08ZSuccessful builds failing with code 259<div><p>I don't believe we've seen this in the past few days, so I'm gonna go ahead and close this from our end.</p></div>acrichtontag:help.appveyor.com,2012-11-13:Comment/468724952019-03-29T18:20:32Z2019-03-29T18:20:34ZSuccessful builds failing with code 259<div><p>We just had another build failing with the 259 error code.</p>
<p><a href="https://ci.appveyor.com/project/rust-lang/rust/builds/23456316/job/8jm7me4fhgcks5pi">https://ci.appveyor.com/project/rust-lang/rust/builds/23456316/job/...</a></p>
<p>The symptoms are the same as the previous failures, as this happened after 3 hours and the build otherwise passed, so I guess the repro would also be the same. We don't have the spare capacity on our account to run it though.</p></div>pietroalbinitag:help.appveyor.com,2012-11-13:Comment/468724952019-03-29T19:28:50Z2019-03-29T19:28:50ZSuccessful builds failing with code 259<div><p>Hmm... Let me please explain how we apply hotfixes to build workers. Each build image update we bake latest build agent bits into VHD. However updating image for quick fixes is too hard way to go. So we have a code which check if newer build agent available and replace it during VM start. If it cannot be downloaded, default one (baked in the image) works. I afraid this happens here -- non-patched agent run this specific build. If I am right, this is unlikely to happen again. And in any case we will release new image with this fix baked in a week or so. Sorry for the trouble.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-03-29T20:01:45Z2019-03-29T20:01:46ZSuccessful builds failing with code 259<div><p>That's reassuring, thanks for the clarification!</p>
<p>Pietro.</p></div>pietroalbinitag:help.appveyor.com,2012-11-13:Comment/468724952019-03-31T21:52:27Z2019-03-31T21:52:27ZSuccessful builds failing with code 259<div><p>Pietro: can you please add <code>appveyor version</code> command sometime in the beginning of the build (say <code>init</code> or <code>install</code>) so in case it happen again (hope not) we check the agent version?</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/468724952019-03-31T21:58:55Z2019-03-31T21:58:58ZSuccessful builds failing with code 259<div><p>Sure! <a href="https://github.com/rust-lang/rust/pull/59593">Sent a PR</a> to add it, it will land in a few days max.</p>
<p>Pietro.</p></div>pietroalbini