|
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 |
|
| #
18181ec5 |
| 18-Nov-2024 |
Trevor Gross <[email protected]> |
ci: Set `-u` (error on unset) in all script files
This is a pretty common flag to reduce errors. Make use of it here.
(backport <https://github.com/rust-lang/libc/pull/4108>)
(cherry picked from co
ci: Set `-u` (error on unset) in all script files
This is a pretty common flag to reduce errors. Make use of it here.
(backport <https://github.com/rust-lang/libc/pull/4108>)
(cherry picked from commit 59a18de777622bccd8be5afce1248cfbfd32f607)
show more ...
|
|
Revision tags: 0.2.164, 0.2.163 |
|
| #
1d981230 |
| 15-Nov-2024 |
Trevor Gross <[email protected]> |
ci: make scripts more uniform
Perform the following style changes:
- Only use uppercase variable names if they are exported
- Only use `${...}` syntax when joining with other strings, `$...`
othe
ci: make scripts more uniform
Perform the following style changes:
- Only use uppercase variable names if they are exported
- Only use `${...}` syntax when joining with other strings, `$...`
otherwise
- Use `CARGO_TERM_VERBOSE` rather than always passing `-v`
- Indent is always four spaces
- Fix shellcheck errors in all shell scripts
- Rewrap some long or complex commands
- Replace redundant `| \` with just `|`
(backport <https://github.com/rust-lang/libc/pull/4042>)
(cherry picked from commit eddb526e06708e64557089dff59ad60e759ab443)
show more ...
|
|
Revision tags: 0.2.162, 0.2.161, 0.2.160, 0.2.159, 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 |
|
| #
cb542f93 |
| 21-Sep-2022 |
kxxt <[email protected]> |
refactor: use grep -E instead of egrep
|
|
Revision tags: 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 |
|
| #
70c9a98c |
| 24-May-2019 |
gnzlbg <[email protected]> |
Run CMSG tests on s390x
Closes #1240.
|
|
Revision tags: 0.2.55, 0.2.54, 0.2.53, 0.2.51, 0.2.50, 0.2.49 |
|
| #
38cf5b15 |
| 01-Feb-2019 |
Alan Somers <[email protected]> |
Add an integration test for the cmsg(3) functions.
Since these are defined in C as macros, they must be reimplemented in
libc as Rust functions. They're hard to get exactly right, and they
vary fro
Add an integration test for the cmsg(3) functions.
Since these are defined in C as macros, they must be reimplemented in
libc as Rust functions. They're hard to get exactly right, and they
vary from platform to platform. The test builds custom C code that uses
the real macros, and compares its output to the Rust versions' output
for various inputs.
Skip the CMSG_NXTHDR test on sparc64 linux because it hits a Bus Error.
Issue #1239
Skip the entire cmsg test program on s390x because it dumps core
seemingly before the kernel finishes booting.
Issue #1240
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 |
|
| #
97a81d79 |
| 13-Nov-2017 |
Sébastien Santoro <[email protected]> |
Use more convenient and UNIX-agnostic shebang
Pure sh scripts should use /bin/sh as it's available on every platform.
When using bash-specific features, use env to find it, as bash can
be installed
Use more convenient and UNIX-agnostic shebang
Pure sh scripts should use /bin/sh as it's available on every platform.
When using bash-specific features, use env to find it, as bash can
be installed in different places according the OS.
show more ...
|
|
Revision tags: 0.2.33 |
|
| #
cd2e87d5 |
| 27-Oct-2017 |
Marco A L Barbosa <[email protected]> |
Run s390x test in qemu system instead of qemu user
|