On 22/8/19 11:41 am, Kinsey Moore wrote:
> The option --report-mode has been changed to --log-mode to reduce ambiguity
> and --report-format has been added along with --report-path for machine
> readable test reporting.
Pushed. Thank you.
Chris
___
deve
The option --report-mode has been changed to --log-mode to reduce ambiguity
and --report-format has been added along with --report-path for machine
readable test reporting.
---
user/tools/tester.rst | 29 +
1 file changed, 21 insertions(+), 8 deletions(-)
diff --git a/
On 21/8/19 5:33 pm, Jiri Gaisler wrote:
> I suggest that we switch to gdb-8.3 for targets that currently use 8.2.1. The
> update is relatively minor but allows building without any patches. Tested
> for SPARC and RISC-V targets.
I am OK with this happening. Please push.
Thanks
Chris
___
On 22/8/19 2:34 am, Kinsey Moore wrote:
> Add log formatter hooks and JSON log formatter to the test infrastructure
> for consumption by automated processes or report generators.
Pushed. Thank you.
A documentation patch would be most welcome
https://docs.rtems.org/branches/master/user/tools/
---
user/tracing/eventrecording.rst | 86 -
1 file changed, 43 insertions(+), 43 deletions(-)
diff --git a/user/tracing/eventrecording.rst b/user/tracing/eventrecording.rst
index d1e44df..39c0117 100644
--- a/user/tracing/eventrecording.rst
+++ b/user/tracing/event
Add log formatter hooks and JSON log formatter to the test infrastructure
for consumption by automated processes or report generators.
---
tester/rt/test.py | 124 --
1 file changed, 111 insertions(+), 13 deletions(-)
diff --git a/tester/rt/test
Here is the final report, published in my Blog. Please review it.
https://medium.com/my-gsoc-2019-journey/gsoc-2019-posix-compliance-74571990c32a
Vaibhav Gupta
On Wed, Aug 21, 2019 at 12:21 AM Vaibhav Gupta
wrote:
>
>
> On Wed, Aug 21, 2019 at 12:15 AM Vaibhav Gupta
> wrote:
>
>>
>>
>> On Tue
Neither Chris nor I could apply the patch.
Make sure it is against the master and resend it. I will try again.
--joel
On Wed, Aug 21, 2019 at 8:47 AM Himanshu Sekhar Nayak
wrote:
>
> I pulled out the latest commit to my repo and didn't see my commit yet. btw
> what should I do next ?
>
> -Hima
I pulled out the latest commit to my repo and didn't see my commit yet. btw
what should I do next ?
-Himanshu
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
https://docs.google.com/document/d/1AhBCmFxOikBG7EBcAaTF7ol_D7SZGn0TJrPcifuVHnE/edit?usp=sharing
is this link and I should have added both of you.
If any mentor or student needs write access, just ask. It is hard to
remember everyone.
--joel
On Wed, Aug 21, 2019 at 3:15 AM Vaibhav Gupta wrote:
On Tue, Aug 20, 2019, 7:45 PM Joel Sherrill wrote:
> Hi
>
> This has been a fantastic and productive GSoC. As part of wrapping
> things up, we would like to make sure the following get taken care of:
>
> + Make sure all code and documentation is submitted, cleaned up and merged.
>Ping mentors
>
> + GSoC Lightning Slides: I have shared a Google presentation with as some
> of the
>students and mentors. Please add 1-2 slides on your project. The
> presentation
>we are starting from is last year's. The slide deck will be used
> for two purposes:
> - 3 minute presentation at GSo
I suggest that we switch to gdb-8.3 for targets that currently use 8.2.1. The
update is relatively minor but allows building without any patches. Tested for
SPARC and RISC-V targets.
Jiri.
>From 5b12c03d184d6cea7019636fc134e06d25a94d9f Mon Sep 17 00:00:00 2001
From: Jiri Gaisler
Date: Wed, 21
13 matches
Mail list logo
