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 com.jcabi:jcabi-xml to v0.29.0 #63

Merged
merged 1 commit into from
Aug 7, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 3, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.jcabi:jcabi-xml (source) 0.25.1 -> 0.29.0 age adoption passing confidence

Release Notes

jcabi/jcabi-xml (com.jcabi:jcabi-xml)

v0.29.0: feat(#​215): Add several useful constructors for SaxonDocument

Compare Source

See #​216, release log:

Released by Rultor 1.75.1, see build log

v0.28.0: XMLDocumentTest.java:59-64: Implement XPath 2.0...

Compare Source

See #​213, release log:

Released by Rultor 1.75.1, see build log

v0.27.2: XMLDocument.with(Sources) forgets the SID

Compare Source

See #​196, release log:

Released by Rultor 2.0-SNAPSHOT, see build log

v0.27.1: XMLDocument.with(Sources) forgets the SID

Compare Source

See #​196, release log:

Released by Rultor 2.0-SNAPSHOT, see build log

v0.27.0: trace() instead of debug()

Compare Source

See #​193, release log:

Released by Rultor 2.0-SNAPSHOT, see build log

v0.26.0: XSLDocument ctor must accept SystemId in most cases

Compare Source

See #​191, release log:

Released by Rultor 2.0-SNAPSHOT, see build log

v0.25.5: Threading bug fixed

Compare Source

See https://github.com/jcabi/jcabi-xml/issues/185

v0.25.4: improve logging messages

Compare Source

See #​182, release log:

Released by Rultor 2.0-SNAPSHOT, see build log

v0.25.3: load XSL only once per XSLDocument

Compare Source

See #​172, release log:

Released by Rultor 2.0-SNAPSHOT, see build log

v0.25.2: more logs about factories

Compare Source

See #​171, release log:

Released by Rultor 2.0-SNAPSHOT, see build log


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 has been generated by Mend Renovate. View repository job log here.

@yegor256
Copy link
Member

yegor256 commented Nov 4, 2022

@rultor please, try to merge

@rultor
Copy link
Contributor

rultor commented Nov 4, 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
Contributor

rultor commented Nov 5, 2022

@rultor please, try to merge

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

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures.

Please refer to /home/r/repo/target/surefire-reports for the individual test results.
Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
    at org.apache.maven.plugin.surefire.SurefireHelper.throwException (SurefireHelper.java:283)
    at org.apache.maven.plugin.surefire.SurefireHelper.reportExecution (SurefireHelper.java:171)
    at org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary (SurefirePlugin.java:546)
    at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked (AbstractSurefireMojo.java:1183)
    at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute (AbstractSurefireMojo.java:931)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:370)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:351)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
[ERROR] 
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
\u001b[0m\u001b[0m'pid' file is absent on the server after the end of operation; it seems that we didn't manage to start Docker container correctly

@renovate renovate bot force-pushed the renovate/com.jcabi-jcabi-xml-0.x branch from 0fd4136 to 05490de Compare March 18, 2023 23:53
@renovate renovate bot changed the title Update dependency com.jcabi:jcabi-xml to v0.25.5 Update dependency com.jcabi:jcabi-xml to v0.27.2 Mar 18, 2023
@renovate renovate bot changed the title Update dependency com.jcabi:jcabi-xml to v0.27.2 Update dependency com.jcabi:jcabi-xml to v0.27.2 - autoclosed Apr 20, 2023
@renovate renovate bot closed this Apr 20, 2023
@renovate renovate bot deleted the renovate/com.jcabi-jcabi-xml-0.x branch April 20, 2023 02:33
@renovate renovate bot changed the title Update dependency com.jcabi:jcabi-xml to v0.27.2 - autoclosed Update dependency com.jcabi:jcabi-xml to v0.27.2 Apr 20, 2023
@renovate renovate bot reopened this Apr 20, 2023
@renovate renovate bot restored the renovate/com.jcabi-jcabi-xml-0.x branch April 20, 2023 07:35
@renovate renovate bot changed the title Update dependency com.jcabi:jcabi-xml to v0.27.2 Update dependency com.jcabi:jcabi-xml to v0.28.0 Jul 19, 2023
@renovate renovate bot force-pushed the renovate/com.jcabi-jcabi-xml-0.x branch from 05490de to f2443e3 Compare July 19, 2023 15:49
@renovate renovate bot changed the title Update dependency com.jcabi:jcabi-xml to v0.28.0 Update dependency com.jcabi:jcabi-xml to v0.29.0 Jul 21, 2023
@renovate renovate bot force-pushed the renovate/com.jcabi-jcabi-xml-0.x branch from f2443e3 to 7730129 Compare July 21, 2023 09:49
@yegor256
Copy link
Member

yegor256 commented Aug 7, 2023

@rultor merge

@rultor
Copy link
Contributor

rultor commented Aug 7, 2023

@rultor merge

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

@rultor rultor merged commit 7730129 into master Aug 7, 2023
8 checks passed
@renovate renovate bot deleted the renovate/com.jcabi-jcabi-xml-0.x branch August 7, 2023 16:00
@rultor
Copy link
Contributor

rultor commented Aug 7, 2023

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 3min)

@0crat
Copy link

0crat commented Aug 7, 2023

Job gh:jcabi/jcabi-matchers#63 is not assigned, can't get performer

@0crat
Copy link

0crat commented Aug 7, 2023

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

PID: 2@abc18478-9d50-4572-83ec-8a9b701d7eb8, thread: PQ-C3RUBL5H9
com.zerocracy.farm.strict.StrictProject[122] java.lang.IllegalArgumentException: File "blanks/renovate[bot].xml" is not accessible in "PMO"

1.0-SNAPSHOT: CID: 01e35acc-68d2-43b8-b65f-aad5bb129ddb, Type: "Close job"

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.

None yet

3 participants