Skip to content

chore: allow nightly build to fail #178

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

Merged
merged 1 commit into from
Jul 11, 2019
Merged

chore: allow nightly build to fail #178

merged 1 commit into from
Jul 11, 2019

Conversation

hawkw
Copy link
Member

@hawkw hawkw commented Jul 11, 2019

Motivation

Recent CI builds have failed on nightly due to a compiler bug:
#174 (comment)

In general, nightly Rust is unstable, and it may often fail for reasons
that are not our fault. We shouldn't block merging branches on nightly
failures, when they are often spurious or unrelated to tracing. It is,
however, still good to look at these builds when possible.

Solution

This branch allows failures on nightly CI builds.

This means that the readme-doctest build is also allowed to fail, which
is a shame. It would be good to find a solution for testing readme
examples that doesn't require nightly Rust. I have some ideas for this
that I'll try to address in a subsequent branch.

Signed-off-by: Eliza Weisman [email protected]

@hawkw hawkw requested review from jonhoo, yaahc and LucioFranco July 11, 2019 17:48
@hawkw hawkw self-assigned this Jul 11, 2019
@hawkw
Copy link
Member Author

hawkw commented Jul 11, 2019

CI is failing for this branch because of deprecations, which tracing denies (we deny all warnings). PR #174 will fix the deprecations.

We should probably not deny all warnings, IMO --- we should probably only deny some warnings. In particular, I think denying deprecations is a mistake, because it means cargo can pick up point releases of upstream deps that will then break our builds.

@hawkw hawkw merged commit 38c8aec into master Jul 11, 2019
hawkw added a commit that referenced this pull request Jul 11, 2019
Recent CI builds have failed on nightly due to a compiler bug:
#174 (comment)

In general, nightly Rust is unstable, and it may often fail for reasons
that are not our fault. We shouldn't block merging branches on nightly
failures, when they are often spurious or unrelated to `tracing`. It is,
however, still good to look at these builds when possible.

This branch allows failures on `nightly` CI builds.

This means that the readme-doctest build is also allowed to fail, which
is a shame. It would be good to find a solution for testing readme
examples that doesn't require `nightly` Rust. I have some ideas for this
that I'll try to address in a subsequent branch.

Signed-off-by: Eliza Weisman <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants