Re: arm (bsp=xilinx_zynq_a9_qemu ) task in 'testsuites/fstests/fsdosfsname01.exe' failed

2022-03-23 Thread Heinz Junkes
Thank you, now I get this : RTEMS Source Builder - Set Builder, 6 (53cb27c0f520) Build Set: 6/rtems-arm … cleaning: gmp-6.1.0-x86_64-linux-gnu-1 reporting: devel/gmp-6.1.0.cfg -> gmp-6.1.0-x86_64-linux-gnu-1.txt reporting: devel/gmp-6.1.0.cfg -> gmp-6.1.0-x86_64-linux-gnu-1.xml config: tools/rtems

[PATCH 1/1] newlib01: Check exit processing for file objects

2022-03-23 Thread Matthew Joyce
From: Matt Joyce --- testsuites/libtests/newlib01/init.c | 131 ++-- 1 file changed, 124 insertions(+), 7 deletions(-) diff --git a/testsuites/libtests/newlib01/init.c b/testsuites/libtests/newlib01/init.c index 5864047a80..58757a7676 100644 --- a/testsuites/libtests/ne

[PATCH 0/1] newlib01: Check exit processing for file objects

2022-03-23 Thread Matthew Joyce
From: Matt Joyce This patch adds additional tests for Newlib's exit processing for file objects. Matt Joyce (1): newlib01: Check exit processing for file objects testsuites/libtests/newlib01/init.c | 131 ++-- 1 file changed, 124 insertions(+), 7 deletions(-) -- 2.3

[PATCH] devel/glib-2.48: Update hash

2022-03-23 Thread Ryan Long
Fixed checksum failure when building qemu. --- bare/config/devel/glib-2.48.2-1.cfg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bare/config/devel/glib-2.48.2-1.cfg b/bare/config/devel/glib-2.48.2-1.cfg index 76927e9..397a2c9 100644 --- a/bare/config/devel/glib-2.48.2-1.cfg

Re: [PATCH] devel/glib-2.48: Update hash

2022-03-23 Thread Sebastian Huber
On 23/03/2022 17:30, Ryan Long wrote: Fixed checksum failure when building qemu. I think we had similar issues before. The workaround was to attach the patch to an RTEMS ticket. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded-

Store test reports?

2022-03-23 Thread Sebastian Huber
Hello, I plan to commit the new validation tests tomorrow. Then I will make some test runs. The test reports sent to bu...@rtems.org have only limited value to track performance regressions for example. Would it make sense to store the full test reports in YAML format in an RTEMS repository (

Re: Store test reports?

2022-03-23 Thread Chris Johns
On 24/3/2022 3:38 am, Sebastian Huber wrote: > I plan to commit the new validation tests tomorrow. Then I will make some test > runs. The test reports sent to bu...@rtems.org have only limited value to > track > performance regressions for example. The test reports sent to that list are archived