Re: [PATCH 1/2] Start converting tests to pytest.

On 2020-03-14 11:12 +1100, Chris Johns wrote: > > I would like to hear what Sebastian is considering for the ESA work. I think > we > should follow what will be done there and ends up in the engineering manual. I'm talking about pytest specifically. The documentation is for the unit tests not

Re: [PATCH 1/2] Start converting tests to pytest.

On 14/3/20 10:48 am, Amar Takhar wrote: > On 2020-03-13 17:28 -0600, Gedare Bloom wrote: > >> pydoc? > > I've never added pydoc to this as it's a generic test class the documentation > is > in the test names eg, test_.*(). You can add a string above to add more > verbosity if required but any

Re: [PATCH 1/2] Start converting tests to pytest.

On 2020-03-13 17:28 -0600, Gedare Bloom wrote: > License/file header? Oh, right I forgot about that, thank you. > pydoc? I've never added pydoc to this as it's a generic test class the documentation is in the test names eg, test_.*(). You can add a string above to add more verbosity if req

Re: Issues when adding a multi-port PCI serial card

On 14/3/20 9:17 am, dufa...@hda.com wrote: >> On Mar 13, 2020, at 16:49 , Chris Johns wrote: >> >> On 14/3/20 6:16 am, dufa...@hda.com wrote: On Mar 13, 2020, at 08:42 , Sebastian Huber wrote: > Finally, after initial successful loop-back testing, I tried to start an > RTEMS s

Re: [PATCH 1/2] Start converting tests to pytest.

On Fri, Mar 13, 2020 at 3:35 PM Amar Takhar wrote: > > This converts three files: > > error.py: > - Check for exceptions and error messages > > path.py: > - Test params and setting module variables > > macros.py: > - Test class with setup and shared module access > > This should cover the bu

[PATCH 1/2] Convert host checking to pytest.

--- rtemstoolkit/darwin.py | 5 - rtemstoolkit/freebsd.py | 5 - rtemstoolkit/host.py| 14 -- rtemstoolkit/linux.py | 5 - rtemstoolkit/netbsd.py | 5 - rtemstoolkit/solaris.py | 5 - rtemstoolkit/tests/te

[PATCH 2/2] Fix typo in internal test.

--- rtemstoolkit/tests/test_error.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rtemstoolkit/tests/test_error.py b/rtemstoolkit/tests/test_error.py index 85ceeae..fe768df 100644 --- a/rtemstoolkit/tests/test_error.py +++ b/rtemstoolkit/tests/test_error.py @@ -6,6 +6,6 @@ d

Re: [PATCH 1/2] Start converting tests to pytest.

I'm aware of the typo in the internal test I've fixed this already. Amar. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: Hello world and query about a project availability

On Fri, Mar 13, 2020 at 2:04 PM Richi Dubey wrote: > > Dear Dr. Bloom, > > Please find my patch given below :- > > From 296fa828fec7c3f99231b377c57ca20411564703 Mon Sep 17 00:00:00 2001 > From: Richi Dubey > Date: Sat, 14 Mar 2020 01:33:02 +0530 > Subject: [PATCH 2/2] Changed the hello world file

Re: Issues when adding a multi-port PCI serial card

> On Mar 13, 2020, at 16:49 , Chris Johns wrote: > > On 14/3/20 6:16 am, dufa...@hda.com wrote: >>> On Mar 13, 2020, at 08:42 , Sebastian Huber >>> wrote: Finally, after initial successful loop-back testing, I tried to start an RTEMS shell on one of the new ports. *Here

[PATCH 2/2] Add a message to run 'pytest' to run rest of test suite.

Also check for 'pytest' during configure if not installed print a warning about installing it to run new test suite. --- wscript | 9 + 1 file changed, 9 insertions(+) diff --git a/wscript b/wscript index bd7c54d..79ab78e 100644 --- a/wscript +++ b/wscript @@ -104,6 +104,8 @@ def configur

[PATCH 1/2] Start converting tests to pytest.

This converts three files: error.py: - Check for exceptions and error messages path.py: - Test params and setting module variables macros.py: - Test class with setup and shared module access This should cover the bulk of what is required to convert the rest to pytest. Also removes the ol

Re: Issues when adding a multi-port PCI serial card

On 14/3/20 6:16 am, dufa...@hda.com wrote: >> On Mar 13, 2020, at 08:42 , Sebastian Huber >> wrote: >>> Finally, after initial successful loop-back testing, I tried to start an >>> RTEMS shell on one of the new ports. >>> >>> *Here I'm trying hard to avoid all-caps because this took the most tim

Re: Hello world and query about a project availability

Dear Dr. Bloom, Please find my patch given below :- >From 296fa828fec7c3f99231b377c57ca20411564703 Mon Sep 17 00:00:00 2001 From: Richi Dubey Date: Sat, 14 Mar 2020 01:33:02 +0530 Subject: [PATCH 2/2] Changed the hello world file --- testsuites/samples/hello/init.c | 43 +++

BSP Buildset for EPICS GSOC 2020 Proposal

Hello everyone, This is to inform that I have updated my first draft link to the proposal on https://devel.rtems.org/wiki/GSoC/2020. It is the first draft of the proposal and needs a lot of refinement and suggestions from the mentors to improve it and make it presentable for the GSoC 2020 proposal

Re: Issues when adding a multi-port PCI serial card

> On Mar 13, 2020, at 08:42 , Sebastian Huber > wrote: Thanks for replying. > > On 12/03/2020 21:44, Peter Dufault wrote: > >> I've added an 8-port RS232 PCI Mezzanine Card to the "beatnik" BSP. The >> console (aka serial port) code is confusing. >> >> I decided I should use what is in

Re: microblaze build failure

On 13/03/2020 19:02, Joel Sherrill wrote: On Fri, Mar 13, 2020 at 12:22 PM Sebastian Huber > wrote: On 13/03/2020 14:53, Joel Sherrill wrote: > Based on conversations with Chris, I don't think this is the same as > his failure mode

LLVM for Release?

Hi Just curious what we want to do about LLVM for this release. --joel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: microblaze build failure

On Fri, Mar 13, 2020 at 12:22 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 13/03/2020 14:53, Joel Sherrill wrote: > > > Based on conversations with Chris, I don't think this is the same as > > his failure mode (on FreeBSD?) and this isn't a critical target but I > > am perp

Added link to my proposal and Call for mentors.

Hi, I have uploaded my draft proposal. I would kindly request you all to review the proposal and provide suggestions. There are many areas that require attention. There are three tickets that has been Included in the proposal: - I have also added one more ticket which I haven't yet discu

Re: microblaze build failure

On 13/03/2020 14:53, Joel Sherrill wrote: Based on conversations with Chris, I don't think this is the same as his failure mode (on FreeBSD?) and this isn't a critical target but I am perplexed at this failure in common code. crt0.c should just compile. This is with everything off the master b

Re: virtex4 fails to link norun tests

Thanks. I just started a build sweep for that. I also just started a tool build, etc on Ubuntu. FWIW This was found using my older rtems-testing scripts. On Fri, Mar 13, 2020 at 9:21 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 13/03/2020 14:40, Joel Sherrill wrote: > >

Re: virtex4 fails to link norun tests

On 13/03/2020 14:40, Joel Sherrill wrote: Not sure how to fix this or how long it has been broken: powerpc-rtems5-gcc  -mcpu=405 -O2 -g -fno-keep-inline-functions -ffunction-sections -fdata-sections -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-exter

microblaze build failure

Hi Based on conversations with Chris, I don't think this is the same as his failure mode (on FreeBSD?) and this isn't a critical target but I am perplexed at this failure in common code. crt0.c should just compile. This is with everything off the master but I get the same failure on CentOS 7 with

virtex4 fails to link norun tests

Hi Not sure how to fix this or how long it has been broken: powerpc-rtems5-gcc -mcpu=405 -O2 -g -fno-keep-inline-functions -ffunction-sections -fdata-sections -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs -B./../../lib/libbsp/powerpc/virtex4 -B/h

Documentation of the Configuration Options

Hello, I finished the work to reorganize the configuration options: https://docs.rtems.org/branches/master/c-user/config/index.html My next is now to parse the documentation source files and generate specification items for the configuration options and groups. This is similar to the glossary

Re: Issues when adding a multi-port PCI serial card

On 12/03/2020 21:44, Peter Dufault wrote: I've added an 8-port RS232 PCI Mezzanine Card to the "beatnik" BSP. The console (aka serial port) code is confusing. I decided I should use what is in "bsp/console-termios.h" as opposed to the "legacy console" approach, *even though* "legacy console

[PATCH 0/3] Add support for event record dumps

This helps to get the event records easily via a serial line in case of a crash. Sebastian Huber (3): score: Add _IO_Base64() rtems: Add rtems_put_char() record: Add rtems_record_dump() cpukit/Makefile.am | 7 ++ cpukit/headers.am|

[PATCH 2/3] rtems: Add rtems_put_char()

Update #3904. --- cpukit/Makefile.am | 1 + cpukit/include/rtems/bspIo.h| 10 + cpukit/libcsupport/src/rtems_put_char.c | 38 + cpukit/libcsupport/src/vprintk.c| 7 +- 4 files changed, 50 insertions(+), 6 deleti

[PATCH 3/3] record: Add rtems_record_dump()

Add rtems_record_dump_base64() and rtems_record_dump_zlib_base64(). Add CONFIGURE_RECORD_FATAL_DUMP_BASE64 and CONFIGURE_RECORD_FATAL_DUMP_ZLIB_BASE64 configuration options. Update #3904. --- cpukit/Makefile.am | 5 + cpukit/headers.am| 1

[PATCH 1/3] score: Add _IO_Base64()

Update #3904. --- cpukit/Makefile.am | 1 + cpukit/include/rtems/score/io.h| 27 - cpukit/score/src/iobase64.c| 81 ++ testsuites/sptests/spprintk/init.c | 56 ++ 4 files changed, 164 insertions(+)