Hi!
The timout is a bit of issue. It is chromium, javas, and now I'm aware aout hdf5.
I had not not manually touched the timeout, because it was "jsut" first round.
I will keep it in mind, and prolong it in next rerun.
Tomorrow, I will send personal eamil to each maintainer. with his statistics. Is it ok?
Still I think I can generate the list you need.
Following copipasted status from your personal email. Do you still wishthe "public" summary?
Happy to help!
J.
Your summary is:
10 passed
0 even srpm failed - are missing, delete, retired or somehow else utterly missing in action (see lower)
3 found, but missingin in copr?
2 failed, from those 0 failed very quickly (see lower)
Details:
* Passed: BareBonesBrowserLaunch, codehaus-parent, gdal, gdl, hdf, jchardet, octave, openmpi, pcfi, plplot
* Missing: N/A
is/are probably orphan dead or really borked. If it is intentional, you may ignore it. If it is error, you should resurrect the package and if in that, ensure it runs against java-17-openjdk (see failed)
* no-copr: ant-antunit, java-sleep, moconti
is/are probably orphan dead or really borked. If it is intentional, you may ignore it. If it is error, you should resurrect the package and if in that, ensure it runs against java-17-openjdk (see failed)
* Failed, suspiciously quickly: N/A
those packages failed so quickly, that the build was in initial phases. That usually mean that you build with source/target lower then 1.7 java-17-openjdk supports 1.7 and up. We recommend to bump the source/target to 1.8, to allow
existence of compact 1.8 packages alongside main javastack. See https://fedoraproject.org/wiki/Changes/Java17#Wrong_source.2Ftarget_version. Don't forget to upstream the patch, or maybe it is enough to update to more fresh upstream release
which supports java-17-openjdk? it may happen, that after the fix, your build will fail in more terrible way (see bellow)
* Failed: hdf5, vtk
those packages failed. Very often the scary error may be fixed by bump to latest upstream version. java-17-openjdk is out shortly, but changes against java-11-openjdk are minimal, and upstreams keep an track. Please, try to fix the package.
Don't hesitate to ask on devel@xxxxxxxxxxxxxxxxx or java-devel@xxxxxxxxxxxxxxxxx or directly to me jvanek@xxxxxxxxxx. If you fix the fail, feel free to share your fix, it may help others.
We are trying to gather the most common issues at https://fedoraproject.org/wiki/Changes/Java17#common_issues_packagers_can_face_and_gathered_solutions . Feel free to enhance the page, or write us your case (possibly both with solution and
without) so we can add it here.
----------
Debugging Your failures.
The copr repo we maintain, contains builds of java-17-openjdk as system JDK, javapackages-tools, maven & comp. honoring that, and java-11-openjdk as non system JDK. Also it contains successfully rebuilt packages. You can directly use this
copr repo in several ways.
* first glance on error. On https://copr.fedorainfracloud.org/coprs/jvanek/java17/builds/ find your build (select "all" instead of "25" at the bottom),
** Click its number, select chroot (currently fedora-rawhide-x86_64 ) and check the logs. Main log is build.log.gz.
* anything you push to rawhide, will automatically rebuild here in fedora-rawhide-x86_64 chroot.
** It is the best approach. If you can fix your package in rawhide directly, without breaking the rawhide too much, go for it
** If you need to experiment, I have a mock config for you (generated from copr-cli mock-config jvanek/java17 fedora-rawhide-x86_64) which you can copy to your /etc/mock and use -
https://github.com/judovana/FedoraSystemJdkBump/blob/main/scritps/spammer/exemplarResults/jvanek-java17-fedora-rawhide-x86_64.cfg . Eg:
# as root, globally
sudo wget https://raw.githubusercontent.com/judovana/FedoraSystemJdkBump/main/scritps/spammer/exemplarResults/jvanek-java17-fedora-rawhide-x86_64.cfg -O /etc/mock/jvanek-java17-fedora-rawhide-x86_64.cfg
# or as user, locally (after creating ~/.config/mock/)
wget https://raw.githubusercontent.com/judovana/FedoraSystemJdkBump/main/scritps/spammer/exemplarResults/jvanek-java17-fedora-rawhide-x86_64.cfg -O ~/.config/mock/jvanek-java17-fedora-rawhide-x86_64.cfg
# change spec, bump sources, apply patches
fedpkg srpm
mock -r jvanek-java17-fedora-rawhide-x86_64 *.src.rpm
Or any other packaging workflow you use, and you can use against the copr repo.
Thank you very much for your help, there are 107 failures, and 270 java packagers, but only 2 active members of java sig. Without your help, the JDK bump will be very hard.
Thank You!
J.
Those should be links to build logs:
failed https://download.copr.fedorainfracloud.org/results/jvanek/java17/fedora-rawhide-x86_64/02988120-vtk/builder-live.log.gz
failed https://download.copr.fedorainfracloud.org/results/jvanek/java17/fedora-rawhide-x86_64/02987887-hdf5/builder-live.log.gz
MISSING: N/A
Links to all your known java packages:
https://src.fedoraproject.org/rpms/BareBonesBrowserLaunch
https://src.fedoraproject.org/rpms/ant-antunit
https://src.fedoraproject.org/rpms/codehaus-parent
https://src.fedoraproject.org/rpms/gdal
https://src.fedoraproject.org/rpms/gdl
https://src.fedoraproject.org/rpms/hdf
https://src.fedoraproject.org/rpms/hdf5
https://src.fedoraproject.org/rpms/java-sleep
https://src.fedoraproject.org/rpms/jchardet
https://src.fedoraproject.org/rpms/moconti
https://src.fedoraproject.org/rpms/octave
https://src.fedoraproject.org/rpms/openmpi
https://src.fedoraproject.org/rpms/pcfi
https://src.fedoraproject.org/rpms/plplot
https://src.fedoraproject.org/rpms/vtk
On 12/1/21 01:39, Orion Poplawski wrote:
On 11/30/21 01:53, Jiri Vanek wrote:
On 11/29/21 15:01, Mat Booth wrote:
On Mon, 29 Nov 2021 at 13:16, Jiri Vanek <jvanek@xxxxxxxxxx> wrote:
I would kindly ask you to search yourself in this list: https://github.com/judovana/FedoraSystemJdkBump/blob/main/scritps/fillCopr/exemplarResults/maintainers.jbump
This list contains dead/retired packages. Any chance to regenerate it
excluding such?
Indeed, that one contains. But the list in https://copr.fedorainfracloud.org/coprs/jvanek/java17/packages/ is orphan/retired free.
Is it enough for you?
It would be really helpful to have a list of failed pacakages with their maintainers.
I'll also note that for example the hdf5 build failed because it hit the 5 hour build timeout. It would be good to check if others had the same issue. The last copr build of hdf5 took about 11 hours.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
