action #65019
closedppc64 debuginfo repo is not stripped for Tumbleweed
0%
Description
ppc64 debuginfo repo is not stripped for Tumbleweed contrary to ppc64 debuginfo repo for Leap 15, or any other arch for Tumbleweed and Leap 15.
This would allow to save some space on o3 storage which is short already.
Updated by riafarov over 4 years ago
From what I see here https://github.com/andrii-suse/openqa-trigger-from-obs/blob/master/xml/obs/openSUSE:Factory:PowerPC.xml we have same configuration as for 64 bit and https://github.com/andrii-suse/openqa-trigger-from-obs/blob/master/xml/obs/openSUSE:Leap:15:PowerPC.xml
Is it still an issue? As there might be a bug then in the sync part, as from the first sight it looked like we have missed the configuration.
Updated by ggardet_arm over 4 years ago
It is still an issue, check repo/openSUSE-Tumbleweed-oss-ppc64_ppc64le-Snapshot20200526-debuginfo on https://openqa.opensuse.org/admin/assets it is 63.13 GiB
In Tumbleweed you also have ppc64 which is not stripped apparently. Only ppc64le is stripped.
Updated by mkittler about 4 years ago
Which exact repository are you talking about?
Updated by ggardet_arm about 4 years ago
mkittler wrote:
Which exact repository are you talking about?
The one used by openQA tests for ppc64 Tumbleweed tests from REPO_OSS_DEBUGINFO.
So, currently repo/openSUSE-Tumbleweed-oss-ppc64_ppc64le-Snapshot20201021-debuginfo 69.51GB
It seems that armv7 is also affected, 33.47 GB.
Updated by okurz about 4 years ago
- Target version changed from Ready to future
Although I don't know the answer by now all the necessary code and data should be accessible for you, either in OBS project config, in github.com/os-autoinst/openqa-trigger-from-obs or on o3 which is also accessible to you and others. Given our current team's capacity we can't commit to do this ourselves.
Updated by ggardet_arm about 4 years ago
- Assignee set to ggardet_arm
Updated by okurz about 4 years ago
- Related to action #76768: HDD images are cleaned-up too early for aarch64 Tumbleweed added
Updated by ggardet_arm about 4 years ago
- Status changed from In Progress to Workable
It seems that the PR was not enough, see: https://github.com/os-autoinst/openqa-trigger-from-obs/pull/102#issuecomment-720391218
Updated by ggardet_arm about 4 years ago
- Assignee set to ggardet_arm
- Priority changed from Low to Normal
2nd attempt to fix it: https://github.com/os-autoinst/openqa-trigger-from-obs/pull/103
Updated by ggardet_arm about 4 years ago
- Status changed from Workable to Resolved
It needed a manual intervention as rsync did not delete the old folder. But now this is fixed on o3.