* test suites for eCos? @ 1998-11-10 8:15 Mohan Pakkurti 1998-11-10 8:15 ` Stuart Adams 0 siblings, 1 reply; 6+ messages in thread From: Mohan Pakkurti @ 1998-11-10 8:15 UTC (permalink / raw) To: ecos-discuss Hi, Is there a test suite for testing new ports to boards and processors? Mohan ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: test suites for eCos? 1998-11-10 8:15 test suites for eCos? Mohan Pakkurti @ 1998-11-10 8:15 ` Stuart Adams [not found] ` < 36485FC7.82D5DFCD@brightstareng.com > 0 siblings, 1 reply; 6+ messages in thread From: Stuart Adams @ 1998-11-10 8:15 UTC (permalink / raw) To: ecos-discuss > Is there a test suite for testing new ports to boards and processors? There is an impressive amount of test support in eCos. After doing a build of the test code I count 146 different test executables for various features of eCos. Now, rather than run each of these by hand I am wondering if there is a dejagnu test harness which will load and run all the tests for me ??? -- Stuart Adams Bright Star Engineering Inc. 19 Enfield Drive Andover MA 01810 USA Tel: +1-978-470-8738 Fax: +1-978-470-8878 Email: sja@brightstareng.com Web: http://www.brightstareng.com/ ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: < 36485FC7.82D5DFCD@brightstareng.com >]
* Re: test suites for eCos? [not found] ` < 36485FC7.82D5DFCD@brightstareng.com > @ 1998-11-10 8:15 ` Mohan Pakkurti [not found] ` < 199811101615.IAA26826@cadence.Cadence.COM > 0 siblings, 1 reply; 6+ messages in thread From: Mohan Pakkurti @ 1998-11-10 8:15 UTC (permalink / raw) To: ecos-discuss; +Cc: sja At 10:46 AM 11/10/98 -0500, Stuart Adams wrote: >> Is there a test suite for testing new ports to boards and processors? > > There is an impressive amount of test support in eCos. After > doing a build of the test code I count 146 different test > executables for various features of eCos. > > Now, rather than run each of these by hand I am wondering > if there is a dejagnu test harness which will load > and run all the tests for me ??? OOps, that is what I meant, some mechanism to run different test configurations! I guess it is time to whip out some Perl... :) hey, you are in Andover, I am in Chelmsford, small world. > >-- > >Stuart Adams >Bright Star Engineering Inc. >19 Enfield Drive >Andover MA 01810 USA >Tel: +1-978-470-8738 >Fax: +1-978-470-8878 >Email: sja@brightstareng.com >Web: http://www.brightstareng.com/ > ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: < 199811101615.IAA26826@cadence.Cadence.COM >]
* ECOS Re: test suites for eCos? [not found] ` < 199811101615.IAA26826@cadence.Cadence.COM > @ 1998-11-18 13:30 ` Bart Veer [not found] ` < 199811182130.VAA18786@sheesh.cygnus.co.uk > 0 siblings, 1 reply; 6+ messages in thread From: Bart Veer @ 1998-11-18 13:30 UTC (permalink / raw) To: pmohan; +Cc: ecos-discuss >>>>> "Mohan" == Mohan Pakkurti <pmohan@cadence.com> writes: Mohan> At 10:46 AM 11/10/98 -0500, Stuart Adams wrote: >>> Is there a test suite for testing new ports to boards and >>> processors? >> There is an impressive amount of test support in eCos. After >> doing a build of the test code I count 146 different test >> executables for various features of eCos. >> >> Now, rather than run each of these by hand I am wondering if >> there is a dejagnu test harness which will load and run all the >> tests for me ??? Mohan> OOps, that is what I meant, some mechanism to run different Mohan> test configurations! I guess it is time to whip out some Mohan> Perl... :) We actually have a number of different test harnesses we use internally for different purposes, e.g. overnight testing on lots of different eval boards vs. manual testing by a single programmer. Currently none of these are ready for general use. Development is ongoing, including the ability to run the test cases directly from the configuration tool. I'll see what I can do about having at least one of the harnesses released to the net. Bart Veer // eCos net maintainer ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: < 199811182130.VAA18786@sheesh.cygnus.co.uk >]
* RE: ECOS Re: test suites for eCos? [not found] ` < 199811182130.VAA18786@sheesh.cygnus.co.uk > @ 1998-11-18 18:35 ` Jimen Ching [not found] ` < 000201be1364$f1c7c0d0$65b7a8c0@JimenC.alii.com > 0 siblings, 1 reply; 6+ messages in thread From: Jimen Ching @ 1998-11-18 18:35 UTC (permalink / raw) To: ecos-discuss >Currently none of these are ready for general use. Development is ^^^^^^^^^^^^^^ >ongoing, including the ability to run the test cases directly from the ^^^^^^^ >configuration tool. I keep reading this. But for some reason, on going development for ecos is not the same as on going development for cygwin or egcs. With these other projects, you see lots of activity on the mailing lists and you have access to snapshots and the cvs tree. But with ecos, there doesn't look like there's anything happening outside of cygnus. Is it really open development, or is it just open source? I guess it is not a one-to-one comparison between ecos, cygwin and egcs. Since ecos is a real-time OS, which may require fault tolerancem while the other software does not have to be as fault tolerant. But somehow, I get the impression that the development model is not the same. ecos seems to be a lot more closed. --jc -- jimen@adtech-inc.com Adtech, Inc. ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: < 000201be1364$f1c7c0d0$65b7a8c0@JimenC.alii.com >]
* Re: ECOS Re: test suites for eCos? [not found] ` < 000201be1364$f1c7c0d0$65b7a8c0@JimenC.alii.com > @ 1998-11-19 14:12 ` Bart Veer 0 siblings, 0 replies; 6+ messages in thread From: Bart Veer @ 1998-11-19 14:12 UTC (permalink / raw) To: jimen; +Cc: ecos-discuss >>>>> "Jimen" == Jimen Ching <jimen@adtech-inc.com> writes: >> Currently none of these are ready for general use. Development >> is ongoing, including the ability to run the test cases >> directly from the configuration tool. Jimen> I keep reading this. But for some reason, on going Jimen> development for ecos is not the same as on going Jimen> development for cygwin or egcs. With these other projects, Jimen> you see lots of activity on the mailing lists and you have Jimen> access to snapshots and the cvs tree. But with ecos, there Jimen> doesn't look like there's anything happening outside of Jimen> cygnus. Is it really open development, or is it just open Jimen> source? Jimen> I guess it is not a one-to-one comparison between ecos, Jimen> cygwin and egcs. Since ecos is a real-time OS, which may Jimen> require fault tolerancem while the other software does not Jimen> have to be as fault tolerant. But somehow, I get the Jimen> impression that the development model is not the same. ecos Jimen> seems to be a lot more closed. This is in large part due to timing. cygwin is on its twentieth release. I am not sure exactly when it started, according to its FAQ the tenth release happened in December 1995 and the third release happened so long ago that nobody remembers the details anymore. This means that they have had quite a few years to build up an active development community. The egcs project was announced in August 1997, so they have had over a year. Of course they had a very significant headstart because there were already very many people involved in the development of the various GNU compilers. eCos was released to the world on November 3 1998, so we have had just over two weeks to build up an active development community. To complicate matters further, during the first week most of the eCos development team at Cygnus was busy demonstrating the system at ESC West, and last week most of the team took a break to recover from the strains during the last few months to get the release out on time. We are very pleased with the web site and download statistics to date. We certainly want to see an open development process, because we believe that is the best way to move the system forward. Both anonymous CVS access and regular snapshots are planned, we have just not had the time yet to get these things in place. In the case of egcs I believe it took about five months before anonymous CVS access became available - if it takes us five weeks to do the same then I'll be happy. If in a year from now you still believe that eCos is just open source rather than open development than as far as I am concerned I'll have failed in my job. As explained in a number of earlier messages and in the FAQ, there is a caveat: Cygnus is not a charitable organization, it is a company. At times there are legal and commercial reasons for not disclosing certain information immediately. This caveat also applies to other projects at Cygnus, for example when the compiler group does a port to a new architecture this is not always announced immediately, but the work still becomes part of the public releases in due course. It is unfortunate that the eCos issues people are most interested in right now, e.g. which additional ports we will be working on, generally fall into this category right now, but the situation should be improving in the coming weeks. Bart Veer // eCos net maintainer ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~1998-11-19 14:12 UTC | newest] Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 1998-11-10 8:15 test suites for eCos? Mohan Pakkurti 1998-11-10 8:15 ` Stuart Adams [not found] ` < 36485FC7.82D5DFCD@brightstareng.com > 1998-11-10 8:15 ` Mohan Pakkurti [not found] ` < 199811101615.IAA26826@cadence.Cadence.COM > 1998-11-18 13:30 ` ECOS " Bart Veer [not found] ` < 199811182130.VAA18786@sheesh.cygnus.co.uk > 1998-11-18 18:35 ` Jimen Ching [not found] ` < 000201be1364$f1c7c0d0$65b7a8c0@JimenC.alii.com > 1998-11-19 14:12 ` Bart Veer
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).