rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2019-07-27	tests: Move run-pass tests without naming conflicts to ui	Vadim Petrochenkov	-85/+0

2019-07-27	tests: Add missing run-pass annotations	Vadim Petrochenkov	-0/+1

2019-05-16	Added ignore-sgx for appropriate tests	Dario Gonzalez	-0/+1

2018-12-25	Remove licenses	Mark Rousskov	-10/+0

2018-01-02	Add 'ignore-cloudabi' to tests that don't and won't build on CloudABI.	Ed Schouten	-0/+1
	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.
2017-10-17	test: Update Emscripten failures/passing	Alex Crichton	-1/+1
	All tests should now have annotation for why they're ignored on emscripten. A few tests no longer need such an annotation as well! Closes #41299
2017-01-19	travis: Get an emscripten builder online	Alex Crichton	-0/+2
	This commit adds a new entry to the Travis matrix which will execute emscripten test suites. Along the way it updates a few bits of the test suite to continue passing on emscripten, such as: * Ignoring i128/u128 tests as they're presumably just not working (didn't investigate as to why) * Disabling a few process tests (not working on emscripten) * Ignore some num tests in libstd (#39119) * Fix some warnings when compiling
2017-01-04	std: Don't pass overlapped handles to processes	Alex Crichton	-0/+90
	This commit fixes a mistake introduced in #31618 where overlapped handles were leaked to child processes on Windows. On Windows once a handle is in overlapped mode it should always have I/O executed with an instance of `OVERLAPPED`. Most child processes, however, are not prepared to have their stdio handles in overlapped mode as they don't use `OVERLAPPED` on reads/writes to the handle. Now we haven't had any odd behavior in Rust up to this point, and the original bug was introduced almost a year ago. I believe this is because it turns out that if you don't pass an `OVERLAPPED` then the system will [supply one for you][link]. In this case everything will go awry if you concurrently operate on the handle. In Rust, however, the stdio handles are always locked, and there's no way to not use them unlocked in libstd. Due to that change we've always had synchronized access to these handles, which means that Rust programs typically "just work". Conversely, though, this commit fixes the test case included, which exhibits behavior that other programs Rust spawns may attempt to execute. Namely, the stdio handles may be concurrently used and having them in overlapped mode wreaks havoc. [link]: https://blogs.msdn.microsoft.com/oldnewthing/20121012-00/?p=6343 Closes #38811