dev-java/dom4j: upgrade jaxen:1.1 -> jaxen:1.2 #20412

vaukai · 2021-04-16T18:11:35Z

Trouble with

There was 1 failure:
1) warning(junit.framework.TestSuite$1)
junit.framework.AssertionFailedError: No tests found in org.apache.commons.jelly.core.BaseMemoryLeakTest
        at junit.framework.Assert.fail(Assert.java:57)
        at junit.framework.TestCase.fail(TestCase.java:223)
        at junit.framework.TestSuite$1.runTest(TestSuite.java:96)
        at junit.framework.TestCase.runBare(TestCase.java:142)
        at junit.framework.TestResult$1.protect(TestResult.java:122)
        at junit.framework.TestResult.runProtected(TestResult.java:142)
        at junit.framework.TestResult.run(TestResult.java:125)
        at junit.framework.TestCase.run(TestCase.java:130)
        at junit.framework.TestSuite.runTest(TestSuite.java:241)
        at junit.framework.TestSuite.run(TestSuite.java:236)
        at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:90)
        at org.junit.runners.Suite.runChild(Suite.java:128)
        at org.junit.runners.Suite.runChild(Suite.java:27)
        at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
        at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
        at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
        at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
        at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
        at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
        at org.junit.runner.JUnitCore.runMain(JUnitCore.java:77)
        at org.junit.runner.JUnitCore.main(JUnitCore.java:36)

FAILURES!!!
Tests run: 121,  Failures: 1

gentoo-repo-qa-bot · 2021-04-16T18:24:26Z

Pull request CI report

Report generated at: 2021-04-16 18:24 UTC
Newest commit scanned: af36102
Status: ✅ good

There are existing issues already. Please look into the report to make sure none of them affect the packages in question:
https://qa-reports.gentoo.org/output/gentoo-ci/99d66ab86d/output.html

gentoo-bot · 2021-04-17T00:16:08Z

Pull Request assignment

Submitter: @vaukai
Areas affected: ebuilds
Packages affected: dev-java/commons-jelly, dev-java/jaxen

dev-java/commons-jelly: @gentoo/java
dev-java/jaxen: @gentoo/java

Linked bugs

Bugs linked: 783165

In order to force reassignment and/or bug reference scan, please append [please reassign] to the pull request title.

Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide

gentoo-repo-qa-bot · 2021-04-17T00:49:28Z

Pull request CI report

Report generated at: 2021-04-17 00:49 UTC
Newest commit scanned: 0cc3539
Status: ✅ good

There are existing issues already. Please look into the report to make sure none of them affect the packages in question:
https://qa-reports.gentoo.org/output/gentoo-ci/c5cb648351/output.html

vaukai · 2021-04-17T07:44:41Z

>>> Installing (4 of 4) dev-java/commons-jelly-1.0.1::testing
 * checking 2 files for package collisions
>>> Merging dev-java/commons-jelly-1.0.1 to /
 * Possibly unneeded dependencies found
 *      forehead
--- /usr/
--- /usr/share/
>>> /usr/share/commons-jelly-1/
>>> /usr/share/commons-jelly-1/lib/
>>> /usr/share/commons-jelly-1/lib/commons-jelly.jar
>>> /usr/share/commons-jelly-1/package.env
>>> dev-java/commons-jelly-1.0.1 merged.

 * Messages for package dev-java/dom4j-1.6.1-r8:

 * Class files not found via DEPEND in package.env
 *      org/jaxen/dom4j/DocumentNavigator.class
 *      org/jaxen/dom4j/Dom4jXPath.class

 * Messages for package dev-java/commons-jelly-1.0.1:

 * Possibly unneeded dependencies found
 *      forehead
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

gentoo-repo-qa-bot · 2021-04-17T08:09:22Z

Pull request CI report

Report generated at: 2021-04-17 08:09 UTC
Newest commit scanned: c21a514
Status: ✅ good

There are existing issues already. Please look into the report to make sure none of them affect the packages in question:
https://qa-reports.gentoo.org/output/gentoo-ci/e5e1b5c6d9/output.html

gentoo-repo-qa-bot · 2021-04-17T08:39:16Z

Pull request CI report

Report generated at: 2021-04-17 08:39 UTC
Newest commit scanned: bdf2d84
Status: ✅ good

There are existing issues already. Please look into the report to make sure none of them affect the packages in question:
https://qa-reports.gentoo.org/output/gentoo-ci/47672742b9/output.html

vaukai · 2021-04-17T08:48:42Z

How could this be solved?

Could not load class: org.apache.commons.jelly.DOESNOTEXIST so taglib instantiation failed

dev-java/jaxen/jaxen-1.2.0-r1.ebuild

fordfrog · 2021-04-17T11:26:01Z

Trouble with

There was 1 failure:
1) warning(junit.framework.TestSuite$1)
junit.framework.AssertionFailedError: No tests found in org.apache.commons.jelly.core.BaseMemoryLeakTest
        at junit.framework.Assert.fail(Assert.java:57)
        at junit.framework.TestCase.fail(TestCase.java:223)
        at junit.framework.TestSuite$1.runTest(TestSuite.java:96)
        at junit.framework.TestCase.runBare(TestCase.java:142)
        at junit.framework.TestResult$1.protect(TestResult.java:122)
        at junit.framework.TestResult.runProtected(TestResult.java:142)
        at junit.framework.TestResult.run(TestResult.java:125)
        at junit.framework.TestCase.run(TestCase.java:130)
        at junit.framework.TestSuite.runTest(TestSuite.java:241)
        at junit.framework.TestSuite.run(TestSuite.java:236)
        at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:90)
        at org.junit.runners.Suite.runChild(Suite.java:128)
        at org.junit.runners.Suite.runChild(Suite.java:27)
        at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
        at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
        at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
        at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
        at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
        at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
        at org.junit.runner.JUnitCore.runMain(JUnitCore.java:77)
        at org.junit.runner.JUnitCore.main(JUnitCore.java:36)

FAILURES!!!
Tests run: 121,  Failures: 1

the class can be ignored if it contains no tests, using the exclude variable.

vaukai · 2021-04-17T11:37:03Z

the class can be ignored if it contains no tests, using the exclude variable.

Done.

gentoo-repo-qa-bot · 2021-04-17T11:54:27Z

Pull request CI report

Report generated at: 2021-04-17 11:54 UTC
Newest commit scanned: ca7a2fe
Status: ✅ good

There are existing issues already. Please look into the report to make sure none of them affect the packages in question:
https://qa-reports.gentoo.org/output/gentoo-ci/b0d655430a/output.html

gentoo-repo-qa-bot · 2021-04-18T08:04:34Z

Pull request CI report

Report generated at: 2021-04-18 08:04 UTC
Newest commit scanned: 8e6b6ce
Status: ✅ good

There are existing issues already. Please look into the report to make sure none of them affect the packages in question:
https://qa-reports.gentoo.org/output/gentoo-ci/f76ffa708f/output.html

fordfrog · 2021-04-18T14:39:06Z

@vaukai both jaxen commits are merged. you can see my change in a871d2b

dev-java/commons-jelly/commons-jelly-1.0.1.ebuild

vaukai · 2021-04-18T15:16:48Z

@vaukai both jaxen commits are merged. you can see my change in a871d2b

Thanks. Just rebased.

gentoo-repo-qa-bot · 2021-04-18T15:28:24Z

Pull request CI report

Report generated at: 2021-04-18 15:28 UTC
Newest commit scanned: 2d2c5fe
Status: ❌ broken

There are too many broken packages to determine whether the breakages were added by the pull request. If in doubt, please rebase.

fordfrog · 2021-04-18T15:47:36Z

@vaukai just searched for packages depending on <commons-lang-3 and came again across commons-jelly and i did not find any packages depending on it. do we really need it for something or we can last-rite it? there's no point in keeping libraries in the tree that we do not have a use for.

vaukai · 2021-04-18T16:08:26Z

@vaukai just searched for packages depending on <commons-lang-3 and came again across commons-jelly and i did not find any packages depending on it. do we really need it for something or we can last-rite it? there's no point in keeping libraries in the tree that we do not have a use for.

I would be glad to get rid of that one and I will just remove it from this PR. Pls go ahead and last-rite.
Then only the dom4j remains here.

Package-Manager: Portage-3.0.17, Repoman-3.0.2 Signed-off-by: Volkmar W. Pogatzki <gentoo@pogatzki.net>

gentoo-repo-qa-bot · 2021-04-18T16:23:19Z

Pull request CI report

Report generated at: 2021-04-18 16:23 UTC
Newest commit scanned: e464e54
Status: ❌ broken

There are too many broken packages to determine whether the breakages were added by the pull request. If in doubt, please rebase.

fordfrog · 2021-04-18T16:55:40Z

@vaukai thanks! there is still a failing test though... but...

gentoo-bot added assigned PR successfully assigned to the package maintainer(s). no bug found No Bug/Closes found in the commits. labels Apr 16, 2021

vaukai force-pushed the commons-jelly branch 2 times, most recently from 29f3d57 to 36796fe Compare April 17, 2021 00:11

vaukai changed the title ~~dev-java/commons-jelly: bump to 1.0.1~~ dev-java/commons-jelly: bump to 1.0.1 [please reassign] Apr 17, 2021

gentoo-bot changed the title ~~dev-java/commons-jelly: bump to 1.0.1 [please reassign]~~ dev-java/commons-jelly: bump to 1.0.1 Apr 17, 2021

gentoo-bot added assigned PR successfully assigned to the package maintainer(s). bug linked Bug/Closes found in footer, and cross-linked with the PR. and removed assigned PR successfully assigned to the package maintainer(s). no bug found No Bug/Closes found in the commits. labels Apr 17, 2021

vaukai force-pushed the commons-jelly branch from 36796fe to 0cc3539 Compare April 17, 2021 00:36

vaukai force-pushed the commons-jelly branch from 0cc3539 to c21a514 Compare April 17, 2021 07:56

vaukai force-pushed the commons-jelly branch from c21a514 to bdf2d84 Compare April 17, 2021 08:28

fordfrog reviewed Apr 17, 2021

View reviewed changes

dev-java/jaxen/jaxen-1.2.0-r1.ebuild Outdated Show resolved Hide resolved

fordfrog reviewed Apr 17, 2021

View reviewed changes

dev-java/jaxen/jaxen-1.2.0-r1.ebuild Outdated Show resolved Hide resolved

vaukai force-pushed the commons-jelly branch from bdf2d84 to ca7a2fe Compare April 17, 2021 11:36

vaukai changed the title ~~dev-java/commons-jelly: bump to 1.0.1~~ dev-java/commons-jelly: bump to 1.0.1 * dev-java/jaxen: support dom4j * dev-java/dom4j: upgrade jaxen:1.1 -> jaxen:1.2 Apr 18, 2021

fordfrog reviewed Apr 18, 2021

View reviewed changes

dev-java/commons-jelly/commons-jelly-1.0.1.ebuild Outdated Show resolved Hide resolved

vaukai force-pushed the commons-jelly branch from 8e6b6ce to 2d2c5fe Compare April 18, 2021 15:15

vaukai changed the title ~~dev-java/commons-jelly: bump to 1.0.1 * dev-java/jaxen: support dom4j * dev-java/dom4j: upgrade jaxen:1.1 -> jaxen:1.2~~ dev-java/commons-jelly: bump to 1.0.1 * dev-java/dom4j: upgrade jaxen:1.1 -> jaxen:1.2 Apr 18, 2021

vaukai changed the title ~~dev-java/commons-jelly: bump to 1.0.1 * dev-java/dom4j: upgrade jaxen:1.1 -> jaxen:1.2~~ dev-java/dom4j: upgrade jaxen:1.1 -> jaxen:1.2 Apr 18, 2021

dev-java/dom4j: upgrade jaxen:1.1 -> jaxen:1.2

e464e54

Package-Manager: Portage-3.0.17, Repoman-3.0.2 Signed-off-by: Volkmar W. Pogatzki <gentoo@pogatzki.net>

vaukai force-pushed the commons-jelly branch from 2d2c5fe to e464e54 Compare April 18, 2021 16:10

gentoo-bot closed this in 90f6986 Apr 18, 2021

vaukai deleted the commons-jelly branch April 18, 2021 19:26

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

dev-java/dom4j: upgrade jaxen:1.1 -> jaxen:1.2 #20412

dev-java/dom4j: upgrade jaxen:1.1 -> jaxen:1.2 #20412

vaukai commented Apr 16, 2021 •

edited

gentoo-repo-qa-bot commented Apr 16, 2021

gentoo-bot commented Apr 17, 2021

gentoo-repo-qa-bot commented Apr 17, 2021

vaukai commented Apr 17, 2021 •

edited

gentoo-repo-qa-bot commented Apr 17, 2021

gentoo-repo-qa-bot commented Apr 17, 2021

vaukai commented Apr 17, 2021

fordfrog commented Apr 17, 2021

vaukai commented Apr 17, 2021

gentoo-repo-qa-bot commented Apr 17, 2021

gentoo-repo-qa-bot commented Apr 18, 2021

fordfrog commented Apr 18, 2021

vaukai commented Apr 18, 2021

gentoo-repo-qa-bot commented Apr 18, 2021

fordfrog commented Apr 18, 2021

vaukai commented Apr 18, 2021

gentoo-repo-qa-bot commented Apr 18, 2021

fordfrog commented Apr 18, 2021

dev-java/dom4j: upgrade jaxen:1.1 -> jaxen:1.2 #20412

dev-java/dom4j: upgrade jaxen:1.1 -> jaxen:1.2 #20412

Conversation

vaukai commented Apr 16, 2021 • edited

gentoo-repo-qa-bot commented Apr 16, 2021

Pull request CI report

gentoo-bot commented Apr 17, 2021

Pull Request assignment

Linked bugs

gentoo-repo-qa-bot commented Apr 17, 2021

Pull request CI report

vaukai commented Apr 17, 2021 • edited

gentoo-repo-qa-bot commented Apr 17, 2021

Pull request CI report

gentoo-repo-qa-bot commented Apr 17, 2021

Pull request CI report

vaukai commented Apr 17, 2021

fordfrog commented Apr 17, 2021

vaukai commented Apr 17, 2021

gentoo-repo-qa-bot commented Apr 17, 2021

Pull request CI report

gentoo-repo-qa-bot commented Apr 18, 2021

Pull request CI report

fordfrog commented Apr 18, 2021

vaukai commented Apr 18, 2021

gentoo-repo-qa-bot commented Apr 18, 2021

Pull request CI report

fordfrog commented Apr 18, 2021

vaukai commented Apr 18, 2021

gentoo-repo-qa-bot commented Apr 18, 2021

Pull request CI report

fordfrog commented Apr 18, 2021

vaukai commented Apr 16, 2021 •

edited

vaukai commented Apr 17, 2021 •

edited