Add arm/musl, mips64, and s390x linux targets to Tier3

[Susurrus]

I don't know why these weren't added originally. They should work with cross.

[asomers]

LGTM

bors r+

[Susurrus]

bors r-

[bors]

Canceled

[Susurrus]

I don't know if the just released version of libc will work, since I saw a commit that inspired me to do this. Let's merge that first and then we can see if this works.

[Susurrus]

Nvm, this doesn't actually make them blocking, so we can merge this.

Bors r+

[Susurrus]

bors r+

[bors]

Build failed

• continuous-integration/travis-ci/push

[asomers]

On the rust=beta channel, test_wait hung. I've seen this on the bench for multithreaded tests, but not for single threaded tests. I'm going to try again.

bors r+

[notriddle]

BuildBot is being unresponsive again...

[bors]

Build failed

• continuous-integration/travis-ci/push

[asomers]

I think that Bors sometimes renames staging.tmp to staging instead of doing a merge commit, and BuildBot doesn't know to build the branch rename. I've just configured buildbot to build the staging.tmp branch as well, even though the Bors docs advise against it. We'll see if it starts picking up this change.

bors r+

[notriddle]

Nope.

[asomers]

Ok, I figured it out. It's a matter of whether the repository ends in .git. When GitHub sends change requests, it leaves off that part. I introduced this error as part of my fix for issue #652 .

bors r-

[bors]

Canceled

[asomers]

Try again.

bors r+

[bors]

Build succeeded

• buildbot/nix-rust/nix fbsd11
• continuous-integration/travis-ci/push

[notriddle]

By the way, there's really no reason to build staging.tmp. Bors never just moves the commit from staging.tmp to staging; it always uses the Git Data API to take the staging.tmp commit and make one in staging with the same contents but a different commit message.