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

ref: Update CI Workflows #528

Merged
merged 3 commits into from
Nov 30, 2022
Merged

ref: Update CI Workflows #528

merged 3 commits into from
Nov 30, 2022

Conversation

Swatinem
Copy link
Member

  • Update actions versions.
  • Switch to cargo-llvm-cov.

- Update actions versions.
- Switch to cargo-llvm-cov.
@codecov-commenter
Copy link

Codecov Report

Merging #528 (7584fd0) into master (3419eee) will decrease coverage by 9.17%.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #528      +/-   ##
==========================================
- Coverage   78.84%   69.66%   -9.18%     
==========================================
  Files          77       66      -11     
  Lines        9355     6554    -2801     
==========================================
- Hits         7376     4566    -2810     
- Misses       1979     1988       +9     

@Swatinem
Copy link
Member Author

The "regression" in code coverage is primarily because we are not considering doctests for coverage anymore. Sentry-rust relies on doctests a lot compared to straight unit/integration tests.

@Swatinem Swatinem enabled auto-merge (squash) November 30, 2022 12:27
@Swatinem Swatinem merged commit b12f72d into master Nov 30, 2022
@Swatinem Swatinem deleted the ref/ci branch November 30, 2022 12:32
MarijnS95 added a commit to MarijnS95/sentry-rust that referenced this pull request Jan 16, 2023
I disabled scheduled jobs on forks in getsentry#435 to prevent [unnecessary spam
from steps that are not supposed to succeed anyway], but @Swatinem
removed the check in getsentry#528 for an undocumented reason.  Add it back to
not bother forkers with day-to-day issues, while still allowing them to
test/see CI results locally on push (to one of a limited set of
preconfigured branches).

[unnecessary spam from steps that are not supposed to succeed anyway]: https://github.com/MarijnS95/sentry-rust/actions/runs/3926205216
Swatinem pushed a commit that referenced this pull request Jan 16, 2023
I disabled scheduled jobs on forks in #435 to prevent [unnecessary spam
from steps that are not supposed to succeed anyway], but @Swatinem
removed the check in #528 for an undocumented reason.  Add it back to
not bother forkers with day-to-day issues, while still allowing them to
test/see CI results locally on push (to one of a limited set of
preconfigured branches).

[unnecessary spam from steps that are not supposed to succeed anyway]: https://github.com/MarijnS95/sentry-rust/actions/runs/3926205216
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants