|
Revision tags: 0.2.174, 0.2.173, 0.2.172, ctest-v0.4.11, ctest-v0.4.10, 0.2.171, 0.2.170, 0.2.169, 0.2.168, ctest-v0.4.9, 0.2.167, 0.2.166, 0.2.165, 0.2.164, 0.2.163, 0.2.162, 0.2.161, 0.2.160, 0.2.159 |
|
| #
f0eff998 |
| 05-Sep-2024 |
Eduardo Sánchez Muñoz <[email protected]> |
Remove unneeded `extern crate`s and imports
(backport <https://github.com/rust-lang/libc/pull/3897>)
(cherry picked from commit ba1b27f51607a64072c9ddf071cb69a143922cb6)
|
|
Revision tags: 0.2.158, 0.2.157, 0.2.156, 0.2.155, 0.2.154, ctest-v0.4.8, 0.2.153, 0.2.152, 0.2.151, 0.2.150, 0.2.149, 0.2.148, 0.2.147, ctest-v0.4.7, 0.2.146, 0.2.145, 0.2.144, 0.2.143, ctest-v0.4.6, 0.2.142, 0.2.141, 0.2.140, 0.2.139, 0.2.138, ctest-v0.4.5, 0.2.137, 0.2.136, 0.2.135, 0.2.134, 0.2.133, 0.2.132, 0.2.131, 0.2.130, 0.2.129, 0.1.128, 0.2.128, 0.2.127, 0.2.126, ctest-v0.4.4, 0.2.125, 0.2.124, 0.2.123, 0.2.122, 0.2.121, 0.2.120, 0.2.119, 0.2.118, 0.2.117, 0.2.116, 0.2.115, 0.2.114, 0.2.113, 0.2.112, 0.2.111, 0.2.110, 0.2.109, ctest-v0.4.3, 0.2.108, 0.2.107, 0.2.106, 0.2.105, ctest-v0.4.2, 0.2.104, 0.2.103, 0.2.102, 0.2.101, 0.2.100, 0.2.99, 0.2.98, 0.2.97, 0.2.96, 0.2.95, ctest-v0.4.1, 0.2.94, 0.2.93, 0.2.92, 0.2.91, 0.2.90, 0.2.89, 0.2.88, 0.2.87, 0.2.86, 0.2.85, 0.2.84, ctest-v0.4.0, 0.2.83, 0.2.82, 0.2.81, 0.2.80, 0.2.79, 0.2.78, 0.2.77, 0.2.76, 0.2.75, 0.2.74, 0.2.73, 0.2.72, ctest-v0.3.0, 0.2.71, 0.2.70, 0.2.69, 0.2.68, 0.2.67, 0.2.66, 0.2.65, 0.2.64, 0.2.63, 0.2.62, 0.2.61, 0.2.60, 0.2.59, 0.2.58, 0.2.57, 0.2.56 |
|
| #
a74b588a |
| 28-May-2019 |
gnzlbg <[email protected]> |
Deprecate AF_MAX and PF_MAX
|
| #
8e26ab49 |
| 28-May-2019 |
gnzlbg <[email protected]> |
Minor nitpicks
|
| #
1a3d1525 |
| 27-May-2019 |
gnzlbg <[email protected]> |
[breaking change] sendmmsg/recvmmsg flag argument is an unsigned integer on MUSL
|
|
Revision tags: 0.2.55, 0.2.54, 0.2.53, 0.2.51, 0.2.50, 0.2.49 |
|
| #
f5cbdbc2 |
| 22-Feb-2019 |
gnzlbg <[email protected]> |
Clean libc-test for apple targets
This cleans up the build.rs of `libc-test` for apple targets.
I wanted to update the docker containers of some targets so that we can start
testing newer currently
Clean libc-test for apple targets
This cleans up the build.rs of `libc-test` for apple targets.
I wanted to update the docker containers of some targets so that we can start
testing newer currently-skipped APIs properly, but it is impossible to figure
out which headers and APIs are skipped for each target.
This PR separates the testing of apple targets into its own self-contained
function. This allows seeing exactly which headers are included, and which items
are skipped. A lot of work will be required to separate the testing of all major
platforms and make the script reasonable.
During the clean up, I discovered that, at least for apple targets, deprecated
but not removed APIs are not tested. I re-enabled testing for those, and fixed
`daemon`, which was not properly linking its symbol. I also added the
`#[deprecated]` attribute to the `#[deprecated]` APIs of the apple targets. The
attribute is available since Rust 1.9.0 and the min. Rust version we support is
Rust 1.13.0.
Many other APIs are also currently not tested "because they are weird" which I
interpret as "the test failed for an unknown reason", as a consequence:
* the signatures of execv, execve, and execvp are incorrect (see
https://github.com/rust-lang/libc/issues/1272)
* the `sig_t` type is called `sighandler_t` in libc for some reason:
https://github.com/rust-lang/libc/issues/1273
This probably explains why some other things, like the
`sa_handler`/`sa_sigaction` fields of `sigaction` were skipped. The field is
actually a union, which can be either a `sig_t` for the `sa_handler` field, or
some other type for the `sa_sigaction` field, but because the distinction was
not made, the field was not checked.
The latest ctest version can check volatile pointers, so a couple of skipped
tests are now tested using this feature.
show more ...
|
|
Revision tags: 0.2.48, 0.2.47, 0.2.46, 0.2.45, ctest-v0.2.7, 0.2.44, ctest-v0.2.4, ctest-v0.2.3, ctest-v0.2.2, ctest-v0.2.1, ctest-v0.2.0, 0.2.43, 0.2.42, 0.2.41, 0.2.40, 0.2.39, 0.2.38, 0.2.37, ctest-v0.1.7, 0.2.36, 0.2.35, 0.2.34, 0.2.33, 0.2.32, ctest-v0.1.6, 0.2.31, ctest-v0.1.5, 0.2.30 |
|
| #
ce276177 |
| 22-Aug-2017 |
Alex Crichton <[email protected]> |
Remove warnings in libc-test
|
| #
2e11d9e1 |
| 10-Aug-2017 |
Bryant Mairs <[email protected]> |
Add more fcntl and seal constants for Android/Linux
We now create an additional binary `linux_fcntl` for testing this
since there are header conflicts when including all necessary headers.
This bina
Add more fcntl and seal constants for Android/Linux
We now create an additional binary `linux_fcntl` for testing this
since there are header conflicts when including all necessary headers.
This binary is run on all platforms even though it's empty on all non-
Android/non-Linux platforms.
Testing has been switched from a custom binary to using a runner-less
test (or pair of tests). This means that for local development a simple
`cd libc-test && cargo test` will run all the tests. CI has also been
updated here to reflect that.
show more ...
|