Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
• Learn more: For more information on this, see Tracking coverage changes for pull request builds.
• Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
• Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
• Learn more: For more information on this, see Tracking coverage changes for pull request builds.
• Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
• Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.
New Repo Setting:
INCLUDE COVERAGE % WITH WARNINGS ABOUT DRIFTED BUILDS?
INCLUDE COVERAGE % WITH WARNINGS ABOUT DRIFTED BUILDS?
Enabling this setting will include a (potentially inaccurate) coverage % with warning messages in status updates for drifted builds.
Adjust setting
whylabs
/
whylogs
/
807588517
/
1
0%
mainline: 83%
mainline: 83%
|
Ran
|
Files
0
|
Run time
0s
|
Badge
Embed ▾
README BADGES
|
coverage: 0.0%. Remained the same
github
GitHub
0 of 0 relevant lines covered (NaN%)
0.0 hits per line
