sandbox trace errors in CI loop

[Michal Simek]

Hi Simon and Tom,

I am preparing pull request and I see that CI loop is reporting issue with 
sandbox trace and I have no idea what's going wrong here.

This is the first problematic commit but have no clue what it has to do with trace.

https://source.denx.de/u-boot/custodians/u-boot-microblaze/-/commit/8c5f80d11b29536979ac41a6087fb8938f45bbf2

If you have an access you can take a look at my queue to see that only this job 
is failing.
https://source.denx.de/u-boot/custodians/u-boot-microblaze/-/pipelines

Thanks,
Michal

collected 1152 items / 1151 deselected / 1 selected
test/py/tests/test_trace.py F                                            [100%]
=================================== FAILURES ===================================
__________________________________ test_trace __________________________________
test/py/tests/test_trace.py:292: in test_trace
     check_function(cons, fname, proftool, map_fname, trace_dat)
test/py/tests/test_trace.py:117: in check_function
     out = util.run_and_log(cons, ['sh', '-c', cmd])
test/py/u_boot_utils.py:181: in run_and_log
     output = runner.run(cmd, ignore_errors=ignore_errors, stdin=stdin, env=env)
test/py/multiplexed_log.py:183: in run
     raise exception
E   ValueError: Exit code: 1
---------------------------- Captured stdout setup -----------------------------
/u-boot
trace: early enable at 00100000
sandbox_serial serial: pinctrl_select_state_full: 
uclass_get_device_by_phandle_id: err=-19
=>
----------------------------- Captured stdout call -----------------------------
=> Call list dumped to 02000000, size 0xde3b30
=> +/tmp/sandbox/tools/proftool -t /tmp/test_trace/trace -o 
/tmp/test_trace/trace.dat -m /tmp/sandbox/System.map dump-ftrace
9842 functions found in map file, start addr 3e000
call count: 1213676
+trace-cmd dump /tmp/test_trace/trace.dat
  Tracing meta data in file /tmp/test_trace/trace.dat:
	[Initial format]
		6	[Version]
		0	[Little endian]
		4	[Bytes in a long]
		4096	[Page size, bytes]
	[Header page, 205 bytes]
	[Header event, 205 bytes]
	[Ftrace format, 3 events]
	[Events format, 0 systems]
	[Kallsyms, 370293 bytes]
	[Trace printk, 0 bytes]
	[Saved command lines, 9 bytes]
	1 [CPUs with tracing data]
	[6 options]
	[Flyrecord tracing data]
	[Tracing clock]
		[local] global counter uptime perf mono mono_raw boot x86-tsc
+sh -c trace-cmd report /tmp/test_trace/trace.dat |grep -E '(initf_|initr_)'
   failed to init data
Exit code: 1
=========================== short test summary info ============================
FAILED test/py/tests/test_trace.py::test_trace - ValueError: Exit code: 1
====================== 1 failed, 1151 deselected in 3.32s ======================
-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP/Versal ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal/Versal NET SoCs
TF-A maintainer - Xilinx ZynqMP/Versal/Versal NET SoCs