Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update links #1445

Merged
merged 2 commits into from Aug 13, 2019
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
Expand Up @@ -38,9 +38,9 @@ With that in mind, the steps for adding a new API are:

### Test before you commit

We have two automated tests running on [Travis](https://travis-ci.org/rust-lang/libc):
We have two automated tests running on [Travis](https://travis-ci.com/rust-lang/libc):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the Travis link be replaced with the Azure one? Also is libc-test using Azure as well? The linked repo still lists Travis in its readme.

Copy link
Contributor

@gnzlbg gnzlbg Aug 13, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes and yes, libc uses azure and libc-test is using azure as well.


1. [`libc-test`](https://github.com/alexcrichton/ctest)
1. [`libc-test`](https://github.com/gnzlbg/ctest)
- `cd libc-test && cargo test`
- Use the `skip_*()` functions in `build.rs` if you really need a workaround.
2. Style checker
Expand Down