gnu: Set up the CI for _TIME_BITS=64

Add new jobs for i686 in test_tier1 and arm and powerpc in test_tier2
where RUST_LIBC_UNSTABLE_GNU_TIME_BITS=64.

Use artifact-tag to avoid artifact name collisi

gnu: Set up the CI for _TIME_BITS=64

Add new jobs for i686 in test_tier1 and arm and powerpc in test_tier2
where RUST_LIBC_UNSTABLE_GNU_TIME_BITS=64.

Use artifact-tag to avoid artifact name collisions.

(backport <https://github.com/rust-lang/libc/pull/4433>)
(cherry picked from commit 352274a3dedcbb942da5eca5cf7df75b15444518)

show more ...

gnu: Set up the CI for _FILE_OFFSET_BITS=64

Add new jobs for i686 in test_tier1 and arm and powerpc in test_tier2
where RUST_LIBC_UNSTABLE_GNU_FILE_OFFSET_BITS=64.

Use artifact-tag to avoid artifac

gnu: Set up the CI for _FILE_OFFSET_BITS=64

Add new jobs for i686 in test_tier1 and arm and powerpc in test_tier2
where RUST_LIBC_UNSTABLE_GNU_FILE_OFFSET_BITS=64.

Use artifact-tag to avoid artifact name collisions.

(backport <https://github.com/rust-lang/libc/pull/4345>)
(cherry picked from commit 874e3994740d84a0e5c52ed4a845076d021b4fd4)

show more ...

ci: Use $PWD instead of $(pwd) in run-docker

Less commands makes for a cleaner `set -x` log. And it is more
efficient.

(backport <https://github.com/rust-lang/libc/pull/4345>)
(cherry picked from

ci: Use $PWD instead of $(pwd) in run-docker

Less commands makes for a cleaner `set -x` log. And it is more
efficient.

(backport <https://github.com/rust-lang/libc/pull/4345>)
(cherry picked from commit afa5c65d2dad6a0534c48d330c8bb555075c5cf4)

show more ...

ci: Replace `$1` with a binding in run-docker.sh

(backport <https://github.com/rust-lang/libc/pull/4124>)
(cherry picked from commit 3faaf4d64bf42d57ccb366089b4d5c6f484d4052)

ci: fix indentation in one more place

(backport <https://github.com/rust-lang/libc/pull/4108>)
(cherry picked from commit 331dd50ef6976778ea73535a953d111fa438caee)

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 ...

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 ...

Use a unique name for the Docker image used by CI.

This allows testing multiple targets in parallel on the same host machine.

Suppress shellcheck warnings

Signed-off-by: Yuki Okushi <[email protected]>

add CI for armv7-unknown-linux-uclibceabihf

Fix shellcheck warnings

Use `build-std` feature instead of using `cargo-xbuild`

Revive CI for the switch target

Add a workaround for disk space failures on Docker

ci: allow overriding run-docker.sh CARGO_HOME.

The `ci/run-docker.sh` utility script adds a `--volume` argument to the
`docker` command to mount the Cargo home directory of the host machine
into the

ci: allow overriding run-docker.sh CARGO_HOME.

The `ci/run-docker.sh` utility script adds a `--volume` argument to the
`docker` command to mount the Cargo home directory of the host machine
into the container at `/cargo`.

Prior to this patch the host's Cargo home directory is assumed to be the
`dirname` of the `dirname` of the `cargo` command's path. That works in
most cases where the host machine installed rust with vanilla
`rustup`. It may fail if the host machine used a different method.

For example if the host machine used the Archlinux rustup package[0]
then `cargo` is installed to `/usr/bin/cargo` and the `run-docker.sh`
script incorrectly mounts `/usr/` to the `/cargo` directory of the test
container.

This patch allows specifying an explicit `CARGO_HOME` to the
`ci/run-docker.sh` script so that users with a non-standard cargo dir
can use the utility without modification. By default if no `CARGO_HOME`
is set then the legacy behaviour is used and `CARGO_HOME` defaults to
the `dirname` of the `dirname` of the `cargo` command is used.

[0]: https://wiki.archlinux.org/index.php/rust#Arch_Linux_package

show more ...

Add a build task for FreeBSD11 without LIBC_CI

Setup Azure Pipelines

Remove hacky Travis workaround

Remove non-POSIX loop construct

Download Docker images first as that seems to work better at least locally

Fix shellcheck issues

Update Android images/runners

Remove --privileged from docker

Update to NDK r15b (with unified headers) and add missing symbols needed by nix crate

Remove docker flags that can cause issues (rust-lang/rust#39036)