|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: Strange symbols_lookup() behaviour in test-symbols on arm64 CI
Hi Jan, Apologies for the delay in responding. On Mon, Dec 15, 2025 at 1:27 PM Jan Beulich <jbeulich@xxxxxxxx> wrote: > > On 15.12.2025 12:00, Mykola Kvach wrote: > > On Thu, Dec 11, 2025 at 6:40 PM Jan Beulich <jbeulich@xxxxxxxx> wrote: > >> > >> On 11.12.2025 17:30, Mykola Kvach wrote: > >>> I have now attached the corresponding build log. > >> > >> Okay, so indeed not a table size change issue here. Then I fear some > >> instrumenting > >> will be needed to at least know what exactly is going wrong. Alternatively > >> you could > >> arrange for the intermediate binaries to not be deleted, and make them > >> available > >> somehow / somewhere for me to see whether by inspection I can gain some > >> clue. > > > > I prepared a small patch to keep the intermediate artifacts instead of > > deleting them. > > > > It removes two cleanup commands: > > xen/arch/arm/Makefile: drops rm -f $(@D)/.$(@F).[0-9]* (keeps > > .xen-syms.* intermediates) > > This alone should be sufficient. Understood. I have rerun the build with the cleanup line removed so the intermediate .xen-syms.* files are kept. The build artifacts are available here: https://gitlab.com/xen-project/people/mykola_kvach/xen/-/jobs/12707528457/artifacts/browse/xen/ Best regards, Mykola > > > xen/scripts/Kbuild.include: drops rm -f $(@D)/.cst.$$$$ (keeps > > .cst.<pid> used by compare-symbol-tables) > > These can be easily re-created from the ones retained above. (They might be > of immediate interest - and hence worth keeping - if the comparisons failed, > but you said the build works fine for you even with these comparisons added.) > > Jan > > > Should I gather any other files/logs that would be useful? > > > > > > > > Mykola > > > >> > >> Jan >
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |