Thanks :)... almost a month of soak time should produce a sane release.
FWIW, I'm solving other issues that I find along the way too. I've found about
10-20 bugs that existed prior to my tipping the apple cart back when I did the
Makefile stuff too.
There are other things with file descriptor flushing that need to be
worked out though because I'm seeing issues with forked processes and printing
to stdout/stderr (it wasn't printing out debug messages after I called
FORK_OR_VFORK in chmod04), so I might need to come up with a more complete
solution to FORK_OR_VFORK that properly handles file descriptor duping, error
trapping, etc. I was also seeing weird issues last night with some tests
(chmod04 again) where it wasn't properly unregistering the signal handler on my
copy of Fedora 13, and it kept on calling the tst_sig handler in the spawned
child process which wasn't desired. So there's a Linux bug or (more likely) an
LTP bug with tst_sig that needs to be fixed somewhere. I need to instrument
signal / sigaction code up that I know works on BSD and a stable linux release
to tie down the issue to Fedora 13 or LTP.
I also need to run the container tests because I did a relatively blind
commit (it built and didn't blow up when I invoked it was all I really did last
night). If someone else would do that for me that would free up some of my time
-- that stuff will compile without failures so you can do a make all / install
of that section of the tree and things will work. If not, please let me know.
Thanks,
-Garrett
On Jan 3, 2011, at 10:44 AM, Subrata Modak wrote:
> On Mon, Jan 3, 2011 at 5:32 PM, Garrett Cooper <[email protected]> wrote:
> There are 200 or so issues remaining with warnings in the sourcebase
> on i386 at least. I'm working through them as quickly as I can, but I run
> into roadblocks occasionally that slow me down... Any warnings that existed
> before will need to be resolved as well before we can continue.
> I've detailed what can be done to help fix things in a previous email
> -- as long as people follow the lead for the changes I've made, it'll be easy
> to resolve all of the outstanding issues.
>
> Should be fine. Lets concentrate and give you enough time to fix them. I will
> release LTP in January-end then when things will stabilize to more extent.
>
> Regards--
> Subrata
>
> Thanks,
> -Garrett
>
> On Jan 3, 2011, at 3:32 AM, Subrata Modak wrote:
>
> > Garret,
> >
> > I see them today:
> >
> > gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -Werror
> > -I/root/LTP-GIT/ltp/testcases/kernel/include -I../../../../include
> > -I../../../../include -L../../../../lib alarm02.c -lltp -o alarm02
> > cc1: warnings being treated as errors
> > alarm02.c: In function ‘main’:
> > alarm02.c:169: error: control reaches end of non-void function
> > make[4]: *** [alarm02] Error 1
> > make[4]: Leaving directory
> > `/root/LTP-GIT/ltp/testcases/kernel/syscalls/alarm'
> > make[3]: *** [all] Error 2
> > make[3]: Leaving directory `/root/LTP-GIT/ltp/testcases/kernel/syscalls'
> > make[2]: *** [all] Error 2
> > make[2]: Leaving directory `/root/LTP-GIT/ltp/testcases/kernel'
> > make[1]: *** [all] Error 2
> > make[1]: Leaving directory `/root/LTP-GIT/ltp/testcases'
> > make: *** [testcases-all] Error 2
> >
> > Regards--
> > Subrata
> >
> >
>
>
>
>
> --
> Regards & Thanks--
> Subrata
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list
