-
Notifications
You must be signed in to change notification settings - Fork 19
lcov report #270
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
lcov report #270
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're disabling GitHub Actions completely?
.drone/lcov-report.sh
Outdated
mkdir -p /tmp/lcov-repo-results || true | ||
skiplist="' | ||
|
||
textpart2="${SKIPLIST}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To make this easier you could use either text+=
or just change quotes like
text='use=41"'\
"$variable"'
$non-evaled'
Or use a here-doc and sed with placeholders
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, instead of textpart1 textpart2 textpart3 , and then joining them together, perhaps it all be one monolithic here-doc. Originally, I tried to design it all as one large variable. Then having difficulty embedded variables inside variables, and dealing with multiple quotes inside quotes. So, broke it apart into pieces. That simplified it.
If you strongly prefer to push them all back into one variable again, and be certain it works, with all the quotes and interpolations, then you can modify this PR, or submit another PR, and I will agree. Or, it can stay as-is, I believe it's ok.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking about how to improve this string creation to be "clean".
In the end I think it would be cleanest to NOT have this string at all:
- add
ci/runcodecov.sh
as a regular script file - before
git submodule foreach
export the 2 required variables from this script (SKIPLIST
&LCOV_SKIP_PATTERN
) - alternatively pass those as arguments for better visibility and fetch them at the start of the script
Having the script separate allows for easier development, linting (I see you also use shellcheck) and manual execution for focused testing
BTW: I'd suggest to always use set -eu
at the top of the scripts to detect misspelled variables, missing parameters and unexpectedly failing commands
The cause was actualy the git safe-directory not the working directory, so this is not required.
@jeking3 , these reports are on a separate branch "feature/reports", to not confuse drone files of the |
1209c4c
to
94f4911
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## feature/reports #270 +/- ##
====================================================
- Coverage 100.00% 88.23% -11.77%
====================================================
Files 2 2
Lines 22 17 -5
Branches 11 0 -11
====================================================
- Hits 22 15 -7
- Misses 0 2 +2 see 2 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
.drone/lcov-report.sh
Outdated
mkdir -p /tmp/lcov-repo-results || true | ||
skiplist="' | ||
|
||
textpart2="${SKIPLIST}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking about how to improve this string creation to be "clean".
In the end I think it would be cleanest to NOT have this string at all:
- add
ci/runcodecov.sh
as a regular script file - before
git submodule foreach
export the 2 required variables from this script (SKIPLIST
&LCOV_SKIP_PATTERN
) - alternatively pass those as arguments for better visibility and fetch them at the start of the script
Having the script separate allows for easier development, linting (I see you also use shellcheck) and manual execution for focused testing
BTW: I'd suggest to always use set -eu
at the top of the scripts to detect misspelled variables, missing parameters and unexpectedly failing commands
Required because the owner inside containers is different, likely root, and git doesn't allow that by default.
Test this by using `set -u` in build scripts
No description provided.