<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/src/test/run-pass/weird-exit-code.rs, branch 1.31.0</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=1.31.0</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=1.31.0'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2018-01-02T13:11:41+00:00</updated>
<entry>
<title>Add 'ignore-cloudabi' to tests that don't and won't build on CloudABI.</title>
<updated>2018-01-02T13:11:41+00:00</updated>
<author>
<name>Ed Schouten</name>
<email>ed@nuxi.nl</email>
</author>
<published>2018-01-02T13:11:41+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=3f880912e90825a88b0a25e235dd43b24da1055b'/>
<id>urn:sha1:3f880912e90825a88b0a25e235dd43b24da1055b</id>
<content type='text'>
It looks like many of these tests are already disabled on emscripten,
which also doesn't seem to support environment variables and subprocess
spawning. Just add a similar tag for CloudABI. While there, sort some of
the lists of operating systems alphabetically.
</content>
</entry>
<entry>
<title>std: Refactor process exit code handling slightly</title>
<updated>2015-11-06T22:40:43+00:00</updated>
<author>
<name>Alex Crichton</name>
<email>alex@alexcrichton.com</email>
</author>
<published>2015-10-29T20:45:56+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=94aee5b7e6d1eda4c872133787ba238cbe29ecb4'/>
<id>urn:sha1:94aee5b7e6d1eda4c872133787ba238cbe29ecb4</id>
<content type='text'>
* Store the native representation directly in the `ExitStatus` structure instead
  of a "parsed version" (mostly for Unix).
* On Windows, be more robust against processes exiting with the status of 259.
  Unfortunately this exit code corresponds to `STILL_ACTIVE`, causing libstd to
  think the process was still alive, causing an infinite loop. Instead the loop
  is removed altogether and `WaitForSingleObject` is used to wait for the
  process to exit.
</content>
</entry>
</feed>
