Skip to content

feat: use cargo-nextest in ci#433

Merged
baszalmstra merged 4 commits intomun-lang:mainfrom
baszalmstra:feat/cargo-nextest
Aug 27, 2022
Merged

feat: use cargo-nextest in ci#433
baszalmstra merged 4 commits intomun-lang:mainfrom
baszalmstra:feat/cargo-nextest

Conversation

@baszalmstra
Copy link
Copy Markdown
Collaborator

Use cargo nextest in CI

@baszalmstra baszalmstra force-pushed the feat/cargo-nextest branch 2 times, most recently from dcff3d4 to 2a86e2a Compare August 6, 2022 18:42
@codecov
Copy link
Copy Markdown

codecov bot commented Aug 6, 2022

Codecov Report

Merging #433 (890968d) into main (9ecf73a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #433   +/-   ##
=======================================
  Coverage   83.13%   83.13%           
=======================================
  Files         281      281           
  Lines       16648    16648           
=======================================
  Hits        13840    13840           
  Misses       2808     2808           

Help us with your feedback. Take ten seconds to tell us how you rate us.

@baszalmstra baszalmstra self-assigned this Aug 6, 2022
@baszalmstra baszalmstra requested a review from Wodann August 6, 2022 22:20
@baszalmstra baszalmstra marked this pull request as ready for review August 6, 2022 22:20
@baszalmstra
Copy link
Copy Markdown
Collaborator Author

@Wodann I think the output of nextest is much nicer than regular cargo test for sure but I don't know if the costs outway of "something extra" and non-standardness outway the benefits. If you don't mind I would like to try for a while and revert if we don't feel this adds more than it costs. WDYT?

@baszalmstra baszalmstra merged commit 468113a into mun-lang:main Aug 27, 2022
@Wodann Wodann added this to the Mun v0.4.0 milestone Dec 5, 2022
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.

2 participants