Please check the troubleshooting guide before creating a ticket.
Your link is broken (404).
Hello.
There was support ticket: https://codecov.freshdesk.com/support/tickets/4511 (but no help for free project).
I have somewhy failed codecov/project check:
Also somewhy there are by 2 checks for /patch and /project. One link directs to Codecov page, another — to GitHub checks.
Anyway, I somewhy see -0.03%, although when I click on the link of failed check — I see the same 98.33%, not 98.30%:
Why there is a fail and how to re-run Codecov check?
r18n:master ← r18n:depfu/check/i18n-1.8.10
opened 11:48PM - 31 Mar 21 UTC
We've tested your project with an updated dependency and the build failed.
This… version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.
| name | version specification | new version |
| --- | --- | --- |
| i18n | ~> 1.0 | 1.8.10 |
Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.
If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)
We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of i18n for this test run.
### What changed?
#### ✳️ i18n (~> 1.0 → 1.8.10) · [Repo](https://github.com/ruby-i18n/i18n) · [Changelog](https://github.com/ruby-i18n/i18n/blob/master/CHANGELOG.md)
<details>
<summary>Release Notes</summary>
<h4><a href="https://github.com/ruby-i18n/i18n/releases/tag/v1.8.10">1.8.10</a></h4>
<blockquote><ul>
<li>Fix string locale will trigger on_fallback hook - <a href="https://bounce.depfu.com/github.com/ruby-i18n/i18n/pull/562">#562</a>
</li>
</ul></blockquote>
<p><em>Does any of this look wrong? <a href="https://depfu.com/packages/rubygem/i18n/feedback">Please let us know.</a></em></p>
</details>
<details>
<summary>Commits</summary>
<p><a href="https://github.com/ruby-i18n/i18n/compare/aec9d66dfdc1d06d43fa98bce3eb494699d3a7bb...0888807ab2fe4f4c8a4b780f5654a8175df61feb">See the full diff on Github</a>. The new version differs by 3 commits:</p>
<ul>
<li><a href="https://github.com/ruby-i18n/i18n/commit/0888807ab2fe4f4c8a4b780f5654a8175df61feb"><code>Bump to 1.8.10</code></a></li>
<li><a href="https://github.com/ruby-i18n/i18n/commit/a4695615dedb3257dbcd20928ecf402019b69252"><code>Merge pull request #562 from piecehealth/fix_on_fallback</code></a></li>
<li><a href="https://github.com/ruby-i18n/i18n/commit/ff6e0b4d5f4d2576b554b8b8e43d82f61e7f04bb"><code>Fix string locale will trigger on_fallback hook.</code></a></li>
</ul>
</details>
---
[Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`.
<details><summary>All Depfu comment commands</summary>
<blockquote><dl>
<dt>@depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd>
<dt>@depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd>
<dt>@depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd>
<dt>@depfu close</dt><dd>Closes this PR and deletes the branch</dd>
<dt>@depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd>
<dt>@depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd>
<dt>@depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd>
<dt>@depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd>
</dl></blockquote>
</details>
Cirrus CI: Cirrus CI
Ruby.
Coverage report generated for RSpec to /tmp/cirrus-ci-build/coverage. 232 / 236 LOC (98.31%) covered.
(without logo somewhy)
Single check per /project and /patch without fails (if no tracking code changed, just dependency version).
Duplicate GitHub checks, one of them failed.
Nothing.
I’ve got a case with fail (-0.03%), but without duplicates:
r18n:master ← r18n:depfu/update/gem_toys-0.8.0
opened 01:09AM - 17 Apr 21 UTC
Here is everything you need to know about this upgrade. Please take a good look … at what changed and the test results before merging this pull request.
### What changed?
#### ✳️ gem_toys (~> 0.7.1 → ~> 0.8.0) · [Repo](https://github.com/AlexWayfer/gem_toys) · [Changelog](https://github.com/AlexWayfer/gem_toys/blob/master/CHANGELOG.md)
<details>
<summary>Release Notes</summary>
<h4>0.8.0 (from changelog)</h4>
<blockquote><ul>
<li>Add <code>refresh</code> answer for release confirmation.</li>
</ul></blockquote>
<p><em>Does any of this look wrong? <a href="https://depfu.com/packages/rubygem/gem_toys/feedback">Please let us know.</a></em></p>
</details>
<details>
<summary>Commits</summary>
<p><a href="https://github.com/AlexWayfer/gem_toys/compare/697cca8ef21a4ffcecd8f30932a6ed2a92b7079c...9a775fa17f0de57646db33cc6c508c25239ef180">See the full diff on Github</a>. The new version differs by 4 commits:</p>
<ul>
<li><a href="https://github.com/AlexWayfer/gem_toys/commit/9a775fa17f0de57646db33cc6c508c25239ef180"><code>Update version to 0.8.0</code></a></li>
<li><a href="https://github.com/AlexWayfer/gem_toys/commit/1835a5ec4ea0c4bbad10884686c7073c2987de67"><code>Add `refresh` answer for release confirmation</code></a></li>
<li><a href="https://github.com/AlexWayfer/gem_toys/commit/b13f8cca3f28124b90e95188ce8299e739d3ed92"><code>Replace custom confirmation with `HighLine::Menu`</code></a></li>
<li><a href="https://github.com/AlexWayfer/gem_toys/commit/b63c9629a776bc6803633ec59ce569dce3279079"><code>Update codecov to version 0.5.0</code></a></li>
</ul>
</details>
---
[Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`.
<details><summary>All Depfu comment commands</summary>
<blockquote><dl>
<dt>@depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd>
<dt>@depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd>
<dt>@depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd>
<dt>@depfu close</dt><dd>Closes this PR and deletes the branch</dd>
<dt>@depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd>
<dt>@depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd>
<dt>@depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd>
<dt>@depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd>
</dl></blockquote>
</details>
tom
April 23, 2021, 9:53pm
3
@AlexWayfer so looking at the compare page between the commits on this PR I see these changes . I’ll be honest, I don’t really understand why those lines are showing up, but maybe you have some insight.
The other thing I notice is that the most recent commit is showing 2 uploads , while the base is showing 4 uploads . The last upload is showing coverage on line 64 for this file lib/r18n-rails-api/loader.rb.
I don’t know, the last changes around loader.rb:64 were made 15 months ago and 3 years ago: https://github.com/r18n/r18n-rails-api/blame/cff867612d740f65ee322bf2eb67c142772c1f5a/lib/r18n-rails-api/loader.rb#L64
So even none of rebase could make changes there.
Maybe something is going differently with parsing multiline assignment, maybe some of dependencies was updated (simplecov ?) or I don’t know.
while the base is showing 4 uploads .
Can you check please times of these 4 uploads? Are there differences in milliseconds, maybe it’s a bug of something?
The other thing I notice is that the most recent commit is showing 2 uploads
Oh, I remember something.
There are should be 4 uploads, as I understand, because I’m testing for 4 versions of Ruby and there is an upload for each of them: https://github.com/r18n/r18n-rails-api/runs/2373937307 (the end of test script).
There can be no uploads in PRs by bot because bots has no permission to read secured environment variables (Codecov token is one of them): [ruby] Upgrade gem_toys to version 0.8.0 by depfu[bot] · Pull Request #4 · r18n/r18n-rails-api · GitHub (there is nothing from Codecov at the end of test scripts).
Maybe this difference affects somehow. But it should not be related to loader.rb:64 strange diff.
tom
May 3, 2021, 6:17pm
5
@AlexWayfer sorry, I’m a little bit confused here. My guess is that it is effecting files like loader.rb, but I really don’t know the technical details there. Is there an issue where you cannot upload the other 2 reports? What can we do to help?
I don’t what to do and what I should to investigate. I suggest to wait another case.
1 Like
tom
August 28, 2021, 8:07pm
10
Got it, thanks @AlexWayfer . This has to do with our use of GitHub checks and statuses. We’re taking a look to see how we can fix this race condition.
1 Like
