about summary refs log tree commit diff
path: root/src/test/ui/process
AgeCommit message (Collapse)AuthorLines
2023-01-11Move /src/test to /testsAlbert Larsan-1149/+0
2022-12-09Fix process-panic-after-fork.rs to pass on newer versions of Android.Peter Collingbourne-36/+41
The test process-panic-after-fork.rs was checking that abort() resulted in SIGSEGV on Android. This non-standard behavior was fixed back in 2013, so let's fix the test to also accept the standard behavior on Android.
2022-10-18Rollup merge of #103023 - andrewpollack:i-fuchsia-finals, r=tmandryYuki Okushi-0/+1
Adding `fuchsia-ignore` and `needs-unwind` to compiler test cases Final tests covering missing privileges r? ``@tmandry`` cc. ``@djkoloski``
2022-10-13Adding fuchsia-ignore and needs-unwind to compiler test casesAndrew Pollack-0/+1
2022-10-07Ensure the correct tombstone file is openedFlorian Bartels-11/+11
2022-10-06Ensure crash is caused by libc::abortFlorian Bartels-4/+22
2022-10-06Fix whitespaceFlorian Bartels-1/+3
2022-10-06Fix test for AndroidFlorian Bartels-0/+22
2022-10-06Enable test on AndroidFlorian Bartels-1/+0
2022-10-03Ignore fuchsia on two compiler testsAndrew Pollack-0/+1
2022-09-27Stabilize bench_black_boxUrgau-1/+0
2022-09-22Rollup merge of #102032 - andrewpollack:bad-signal-compiler-tests, r=tmandryYuki Okushi-0/+1
Adding ignore fuchsia tests for signal interpretation cases Tests where Signal interpreting is required. Since Fuchsia currently does not return signals of type `libc::SIGSEGV` etc., instead, use generalized `!status.success()` case. cc. `@djkoloski` r? `@tmandry`
2022-09-21Adding ignore fuchsia tests for signal casesAndrew Pollack-0/+1
2022-09-19Adding ignore fuchsia tests for Backtrace, ErrorKind casesAndrew Pollack-0/+1
2022-09-12Adding ignore-fuchsia arg to non-applicable compiler ui testsAndrew Pollack-0/+4
2022-07-27Fix process-spawn-nonexistent on WSLNilstrieb-5/+7
If appendWindowsPath is set to true (the default IIRC), running invalid commands returns PermissionDenied instead of NotFound.
2022-07-20Use non-relocatable code in nofile-limit.rs testTomasz Miąsko-1/+1
To avoid using static-pie which is not essential to the test but which was reported to cause problems on Void Linux where glibc is build without support for static-pie.
2022-06-10Auto merge of #96837 - tmiasko:stdio-fcntl, r=joshtriplettbors-0/+46
Use `fcntl(fd, F_GETFD)` to detect if standard streams are open In the previous implementation, if the standard streams were open, but the RLIMIT_NOFILE value was below three, the poll would fail with EINVAL: > ERRORS: EINVAL The nfds value exceeds the RLIMIT_NOFILE value. Switch to the existing fcntl based implementation to avoid the issue. Fixes #96621.
2022-05-20Move testsCaio-0/+39
2022-05-11Use `fcntl(fd, F_GETFD)` to detect if standard streams are openTomasz Miąsko-0/+46
In the previous implementation, if the standard streams were open, but the RLIMIT_NOFILE value was below three, the poll would fail with EINVAL: > ERRORS: EINVAL The nfds value exceeds the RLIMIT_NOFILE value. Switch to the existing fcntl based implementation to avoid the issue.
2022-05-08Move some tests to more reasonable placesCaio-0/+19
2022-03-19Add needs-unwind directive to tests where necessarybjorn3-0/+1
2021-11-18Move some tests to more reasonable directoriesCaio-0/+323
2021-11-14Move some tests to more reasonable directoriesCaio-0/+115
2021-11-10Rollup merge of #89930 - cuviper:avoid-clone3, r=joshtriplettMatthias Krüger-16/+1
Only use `clone3` when needed for pidfd In #89522 we learned that `clone3` is interacting poorly with Gentoo's `sandbox` tool. We only need that for the unstable pidfd extensions, so otherwise avoid that and use a normal `fork`. This is a re-application of beta #89924, now that we're aware that we need more than just a temporary release fix. I also reverted 12fbabd27f700, as that was just fallout from using `clone3` instead of `fork`. r? `@Mark-Simulacrum` cc `@joshtriplett`
2021-11-06Move some tests to more reasonable directoriesCaio-0/+102
2021-11-05Revert "Do not call getpid wrapper after fork in tests"Josh Stone-16/+1
This reverts commit 12fbabd27f700a59d0e7031f0839b220c3514bcb. It was only needed because of using raw `clone3` instead of `fork`, but we only do that now when a pidfd is requested.
2021-08-01Do not call getpid wrapper after fork in testsDominik Stolz-1/+16
The test calls libc::getpid() in the pre_exec hook and asserts that the returned value is different from the PID of the parent. However, libc::getpid() returns the wrong value. Before version 2.25, glibc caches the PID of the current process with the goal of avoiding additional syscalls. The cached value is only updated when the wrapper functions for fork or clone are called. In PR #81825 we switch to directly using the clone3 syscall. Thus, the cache is not updated and getpid returns the PID of the parent. source: https://man7.org/linux/man-pages/man2/getpid.2.html#NOTES
2021-05-14panic abort after fork test: Disable on androidIan Jackson-0/+1
And link to the issue. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
2021-05-13Tolerate SIGTRAP for panic abort after panic::always_abortIan Jackson-1/+1
Some platforma (eg ARM64) apparently generate SIGTRAP for panic abort! See eg https://github.com/rust-lang/rust/pull/81858#issuecomment-840702765 This is probably a bug, but we don't want to entangle this MR with it. When it's fixed, this commit should be reverted. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
2021-05-13Use SIGUSR1 rather than SIGTRAP for "allocated after fork"Ian Jackson-2/+2
Some platforma (eg ARM64) apparently generate SIGTRAP for panic abort! See eg https://github.com/rust-lang/rust/pull/81858#issuecomment-840702765 This is probably a bug, but (i) we want to avoid that bug rather than trying to fix it now and (ii) it would better to use a signal that is less at risk of strangeness. I grepped the rust-lang/rut codebase for SIGUSR and there were no hits. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
2021-05-07panic ui test: Provide comprehensive test for panic after forkIan Jackson-0/+150
This tests that we can indeed safely panic after fork, both a raw libc::fork and in a Command pre_exec hook. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk> Co-authored-by: Mara Bos <m-ou.se@m-ou.se>
2020-11-22Drop support for cloudabi targetsLzu Tao-8/+0
2020-05-08Skip tests on emscriptenYuki Okushi-0/+1
2020-05-06Move tests from `test/run-fail` to UIYuki Okushi-0/+11
2019-07-31issue-2214.rs: lgamma is lgamma on vxWorksBaoshan Pang-0/+2
ignore process-envs.rs and process-remove-from-env.rs as there is no 'env' on vxWorks
2019-07-28bypass x86stdcall.rs for vxworksBaoshan Pang-0/+1
ignore wait-forked-but-failed-child.rs as there is no command 'ps' on vxWorks ignore process-sigpipe.rs as there is no 'sh' on vxWorks ignore core-run-destroy.rs as there is no 'cat' and 'sleep' on vxWorks
2019-07-27tests: Move run-pass tests without naming conflicts to uiVadim Petrochenkov-0/+291
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-01-15 14:00:23 +0000