Re: eCos GNU tools 4.6.2-20120125 ready for testing

[Sergei Gavrikov <sergei dot gavrikov at gmail dot com>]

On Wed, 7 Mar 2012, Ilija Kocho wrote:

> Thank you Alex

Also from me (you have great test farm :-)

> We will need some time to analyze the results and try to reproduce.
> At present I could ony partially comment on ustl tests.
> 
> bvt13 and bvt17 require certain input from the user, something which the test machine might not be able to provide.
> Similar report from Sergei (pse see NOTE near end of his mail). http://ecos.sourceware.org/ml/ecos-devel/2012-03/msg00001.html
> I have tried both tests manually (on TWR-K60N512 target) and they passed.
> 
> bvt05 seem's to need a lot of RAM. It was beyond capacity of my target
> (128KiB RAM), and maybe even too much for STM3210-EVAL. I'll see if the
> test could be changed to run with less memory.

The `bvt05' is suitable for targets with of amount of RAM even more than
1M. So, I rejected this test from my runs (but when I decreased a number
of items for the 64-bit tests the test passed on ARM7 target).
 
> For sprintf2 I don't have explanation - I'll try to rerun on STM3210-EVAL.

I found this bug during tests on ARM7 and submit a patch

 http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001490
 http://bugs.ecos.sourceware.org/attachment.cgi?id=1587

As the patch tweaks libc (vsnprintf()) I did not risk commit it without
further discussion.

> I notice that other tests have failed with /uitron/ template with which
> I have no experience so I can't comment at present.

I did not tried '-Os' builds, so, I will try to reproduce those faults
(for comparison) on ARM7 target.

And there is more news for me, that is `testintr' ...

Sergei

> Regards
> Ilija
> 
> 
> On 07.03.2012 12:58, Alex Schuilenburg wrote:
> > Hi Ilija,
> >
> > The RedBoot issue on the STM3210E-EVAL turned out to be a non-issue. 
> > eCos and eCosPro RedBoot are compatible. There was an eCosPro specific
> > issue which I had forgotten about - sorry.  The board ran overnight just
> > over 1000 tests in different eCos configurations.  There are currently 9
> > failures, listed according to their configuration name in our test farm.
> > As jld knows, when a test fails in the farm it is automatically rerun an
> > additional 2 times to confirm the failure is reproducible.  All other
> > tests in these configurations passed.
> >
> > ustl1: bvt05, bvt13, bvt17, sprintf2
> >
> > infra1: except1, kexcept1, testintr
> >
> > absent1, compile1: testintr
> >
> > The eCos used was the version was dated 1 March and the configurations
> > script segment to create each configuration is listed below.  If you
> > need any more info, just let me know. I unfortunately don't have the
> > time at the moment to export the full set of results, but hopefully this
> > will be enough for you to reproduce the failures.  As a comparison, all
> > tests passed in eCosPro for the STM3210E-EVAL with the obvious exception
> > of the ustl1 configuration.
> >
> >
> > ustl1:
> >
> > ecosconfig -i new stm3210e_eval
> > cat > ustl1.ecm <<EOF;
> > cdl_configuration eCos {
> >     template default ;
> >     package CYGPKG_USTL current ;
> >     package CYGPKG_IO_FILEIO current ;
> > };
> > EOF
> > ecosconfig import ustl1.ecm
> > ecosconfig resolve
> > ecosconfig tree
> > ...
> >
> >
> > infra1:
> > ecosconfig -i new stm3210e_eval
> > cat > infra1.ecm <<EOF;
> > cdl_configuration infra1 {
> >     template    uitron ;
> >     package -template CYGPKG_UITRON current ;
> > };
> >
> > cdl_component CYG_HAL_STARTUP {
> >     user_value RAM
> > };
> >
> > cdl_component CYGPKG_INFRA_DEBUG {
> >     user_value 1
> > };
> > EOF
> > ecosconfig import infra1.ecm
> > ecosconfig resolve
> > ecosconfig tree
> > ...
> >
> >
> > compile1:
> > Default build with "-Os"
> >
> > absent1:
> > ecosconfig -i new stm3210e_eval
> >
> > cat > absent1.ecm <<EOF;
> > cdl_configuration absent1 {
> >     hardware    stm3210e_eval ;
> >     template    uitron ;
> >     package -template CYGPKG_UITRON current ;
> > };
> >
> > cdl_component CYG_HAL_STARTUP {
> >     user_value RAM
> > };
> >
> > cdl_option CYGSEM_LIBC_EXIT_CALLS_FFLUSH {
> >     user_value 0
> > };
> >
> > cdl_option CYGFUN_LIBC_TIME_POSIX {
> >     user_value 0
> > };
> >
> > cdl_option CYGIMP_LIBC_TIME_ASCTIME_R_INLINE {
> >     user_value 0
> > };
> >
> > cdl_option CYGIMP_LIBC_TIME_CTIME_R_INLINE {
> >     user_value 0
> > };
> >
> > cdl_option CYGIMP_LIBC_TIME_GMTIME_R_INLINE {
> >     user_value 0
> > };
> >
> > cdl_option CYGIMP_LIBC_TIME_LOCALTIME_R_INLINE {
> >     user_value 0
> > };
> >
> > cdl_option CYGSEM_LIBM_USE_STDERR {
> >     user_value 0
> > };
> > EOF
> >
> > ecosconfig import absent1.ecm
> >
> > ecosconfig resolve
> > ecosconfig tree
> > ...
> >
> >
> >
> > Cheers
> > - Alex Schuilenburg
> >
> > Managing Director/CEO                                eCosCentric Limited
> >
> >   **  Visit us at the ESC Expo at Design West in San Jose  **
> >   **  27-29 March, McEnery Convention Center - Stand #846  **
> >
> >
>