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

Update dependency codecov to v0.6.0 #174

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 5, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
codecov (changelog) '0.2.8' -> '0.6.0' age adoption passing confidence

Release Notes

codecov/codecov-ruby (codecov)

v0.6.0

Compare Source

  • #​145 Fixes issue with nil URI and provides more token information

v0.5.2

Compare Source

v0.5.1

Compare Source

  • #​138 Update pass_ci_if_error flag

v0.5.0

Compare Source

  • #​137 Place uploader in try/rescue block and add pass_ci_if_error flag

v0.4.3

Compare Source

  • #​135 Shorten coverage message on formatter

v0.4.2

Compare Source

  • #​134 Wrap file creation in try/catch

v0.4.1

Compare Source

  • #​133 Write down to file when using the formatter

v0.4.0

Compare Source

  • #​130 Split uploader from formatter

v0.3.0

Compare Source

  • #​124 Ruby 3.0 support
  • #​125 open simplecov requirement to 0.21.x

v0.2.15

Compare Source

  • #​118 Include codecov/version in the gem

v0.2.14

Compare Source

  • #​107 Add EditorConfig file
  • #​113 Return version constant, don't duplicate version value
  • #​117 Update simplecov dependency versions

v0.2.13

Compare Source

  • #​105 Remove unnecessary dependency for ruby standard gem
  • #​110 Fix GitHub Actions
  • #​111 Fix branch name detection for GitHub Actions CI

v0.2.12

Compare Source

  • #​102 Fix value of params[:pr] when useing CodeBuild

v0.2.11

Compare Source

  • Add vendor/ to invalid directories

v0.2.10

Compare Source

  • Adds better logging on error cases
  • Add more invalid directories in the network

v0.2.9

Compare Source

  • Remove String specific colors
  • Add support for Codebuild CI

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@0crat
Copy link
Collaborator

0crat commented Nov 5, 2022

There is an unrecoverable failure on my side. Please, submit it here:

PID: 4@e7f9fc12-6494-413b-94c5-f81742e2228c, thread: PQ-CT4L4490E
com.jcabi.xml.StrictXML[124] java.lang.IllegalArgumentException: 2 error(s) in XML document: -1:-1: cvc-pattern-valid: Value 'renovate[bot]' is not facet-valid with respect to pattern '[a-z0-9\-]{3,}' for type 'login'.;-1:-1: cvc-type.3.1.3: The value 'renovate[bot]' of element 'login' is not valid.

1.0-SNAPSHOT: CID: 1ed696c5-d38d-469f-a5ba-1311696b607e, Type: "Job was added to WBS"

@yegor256
Copy link
Owner

yegor256 commented Nov 5, 2022

@rultor please, try to merge

@0crat
Copy link
Collaborator

0crat commented Nov 5, 2022

@yegor256/z everybody who has role REV is banned at #174; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@renovate
Copy link
Contributor Author

renovate bot commented Nov 5, 2022

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Gemfile.lock
Fetching gem metadata from https://rubygems.org/.........
Resolving dependencies...

Could not find compatible versions

Because codecov >= 0.3.0 depends on simplecov >= 0.15, < 0.22
and simplecov >= 0.15, < 0.22 could not be found in rubygems repository
https://rubygems.org/ or installed locally for any resolution platforms (ruby,
x86_64-darwin-18, x86_64-darwin-19),
  codecov >= 0.3.0 is forbidden.
So, because Gemfile depends on codecov = 0.6.0,
  version solving has failed.

The source contains the following gems matching 'simplecov (>= 0.15, < 0.22)':
  * simplecov-0.15.0
  * simplecov-0.15.1
  * simplecov-0.16.0
  * simplecov-0.16.1
  * simplecov-0.17.0
  * simplecov-0.17.1
  * simplecov-0.18.0.beta1
  * simplecov-0.18.0.beta2
  * simplecov-0.18.0.beta3
  * simplecov-0.18.0
  * simplecov-0.18.1
  * simplecov-0.18.2
  * simplecov-0.18.3
  * simplecov-0.18.4
  * simplecov-0.18.5
  * simplecov-0.19.0
  * simplecov-0.19.1
  * simplecov-0.20.0
  * simplecov-0.21.0
  * simplecov-0.21.1
  * simplecov-0.21.2

@rultor
Copy link
Collaborator

rultor commented Nov 5, 2022

@rultor please, try to merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor
Copy link
Collaborator

rultor commented Nov 5, 2022

@rultor please, try to merge

@renovate[bot] @yegor256 Oops, I failed. You can see the full log here (spent 9min)

D: SELECT login FROM author WHERE id=$1: 0ms / 5600
D: SELECT author FROM project WHERE id=$1: 0ms / 5620
D: SELECT login FROM author WHERE id=$1: 0ms / 5640
D: SELECT login FROM author WHERE id=$1: 0ms / 5660
D: SELECT login FROM author WHERE id=$1: 0ms / 5600
D: UPDATE project SET deleter=$1 WHERE id=$2: 1ms / 5620
D: SELECT coordinates FROM project WHERE id=$1: 0ms / 5640
D: SELECT login FROM author WHERE id=$1: 0ms / 5660
D: SELECT login FROM author WHERE id=$1: 0ms / 5600
D: SELECT author FROM project WHERE id=$1: 0ms / 5620
D: SELECT login FROM author WHERE id=$1: 0ms / 5640
D: SELECT author FROM project WHERE id=$1: 0ms / 5660
D: SELECT login FROM author WHERE id=$1: 0ms / 5600
D: SELECT login FROM author WHERE id=$1: 0ms / 5620
D: SELECT login FROM author WHERE id=$1: 0ms / 5640
D: SELECT deleter FROM project WHERE id=$1: 0ms / 5660
D: SELECT deleter FROM project WHERE id=$1: 0ms / 5600
D: SELECT login FROM author WHERE id=$1: 0ms / 5620
  test_rejects_review_for_deleted_project                        \u001b[32m PASS\u001b[0m (0.01s)

Xia::MetaTest
D: INSERT INTO author (login) VALUES ($1) ON CONFLICT DO NOTHING: 0ms / 5640
D: SELECT id FROM author WHERE login=$1: 0ms / 5660
D: SELECT login FROM author WHERE id=$1: 0ms / 5600
D: SELECT login FROM author WHERE id=$1: 0ms / 5620
D: SELECT id FROM project WHERE platform=$1 AND coordinates=$2: 0ms / 5640
D: SELECT login FROM author WHERE id=$1: 0ms / 5660
D: SELECT COUNT(*) FROM meta JOIN author ON author.id=meta.author WHERE project=$1 AND login=$2 AND key=$3: 1ms / 5600
D: INSERT INTO meta (project, author, key, value) VALUES ($1, $2, $3, $4) ON CONFLICT (project, author, key) DO UPDATE SET value = $4 RETURNING id: 1ms / 5620
D: SELECT login FROM author WHERE id=$1: 0ms / 5640
D: SELECT COUNT(*) FROM meta JOIN author ON author.id=meta.author WHERE project=$1 AND login=$2 AND key=$3: 1ms / 5660
D: INSERT INTO meta (project, author, key, value) VALUES ($1, $2, $3, $4) ON CONFLICT (project, author, key) DO UPDATE SET value = $4 RETURNING id: 1ms / 5600
D: SELECT login FROM author WHERE id=$1: 0ms / 5620
D: SELECT value FROM meta JOIN author ON author.id=meta.author WHERE project=$1 AND login=$2 AND key=$3: 1ms / 5640
  test_set_and_read                                              \u001b[32m PASS\u001b[0m (0.01s)

Finished in 2.75379s
44 tests, 185 assertions, \u001b[32m0 failures, 0 errors, \u001b[0m\u001b[33m0 skips\u001b[0m
Coverage report generated for Unit Tests to /home/r/repo/coverage. 709 / 773 LOC (91.72%) covered.
Running RuboCop...
Inspecting 47 files
\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m

47 files inspected, \u001b[32mno offenses\u001b[0m detected
Running xcop...
Inspecting 13 files...
\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m\u001b[32m.\u001b[0m
13 files checked, everything looks \u001b[32mpretty\u001b[0m
grep -q -r '2022'     --include '*.rb'     --include '*.txt'     --include 'Rakefile'     .
2022-11-05 11:09:49.982 UTC [10737] LOG:  received smart shutdown request
PostgreSQL killed in PID 10737
2022-11-05 11:09:49.993 UTC [10737] LOG:  background worker "logical replication launcher" (PID 10744) exited with exit code 1
+ mv /home/r/repo .
2022-11-05 11:09:49.993 UTC [10739] LOG:  shutting down
2022-11-05 11:09:50.080 UTC [10737] LOG:  database system is shut down
mv: cannot stat '/home/r/repo/target/pgsql/postmaster.pid': No such file or directory
mv: cannot stat '/home/r/repo/target/pgsql/.s.PGSQL.38705.lock': No such file or directory
mv: cannot stat '/home/r/repo/target/pgsql/.s.PGSQL.38705': No such file or directory
container 37006080c880797ba1ae649c726ffdc48590e37cf9450c351e37806a18a6fe57 is dead
Sat 05 Nov 2022 12:15:47 PM CET

@0crat
Copy link
Collaborator

0crat commented Nov 10, 2022

@yegor256/z everybody who has role REV is banned at #174; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Nov 15, 2022

@yegor256/z everybody who has role REV is banned at #174; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Nov 20, 2022

@yegor256/z everybody who has role REV is banned at #174; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Nov 25, 2022

@yegor256/z everybody who has role REV is banned at #174; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Nov 30, 2022

@yegor256/z everybody who has role REV is banned at #174; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Dec 5, 2022

@yegor256/z everybody who has role REV is banned at #174; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Dec 10, 2022

@yegor256/z everybody who has role REV is banned at #174; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Dec 15, 2022

@yegor256/z everybody who has role REV is banned at #174; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Dec 20, 2022

@yegor256/z everybody who has role REV is banned at #174; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Jan 18, 2023

@yegor256/z everybody who has role REV is banned at #174; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Jan 23, 2023

@yegor256/z everybody who has role REV is banned at #174; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants