Hi Alex,
These patches are OK to push.
One minor point, the script sha512-base64 in the RSB creates a base64 encoded
hash and that makes them smaller. I prefer we move to this more and more.
Chris
On 19/8/21 1:34 pm, Alex White wrote:
> Hi,
>
> This patch set now depends on Joel's newlib
On 20/8/21 3:16 am, Joel Sherrill wrote:
> On Thu, Aug 19, 2021 at 11:51 AM Gedare Bloom wrote:
>>
>> I have no problem with this. I think it is sensible to look for
>> python3 before python2. At some point we'll have to stop looking for
>> python2 :)
>
> That is further in the future than I
On 20/8/21 1:45 am, junkes wrote:
> Hallo Peter,
> I do not know if this is best practice but I run the following code:
>
> static void
> default_network_dhcpcd(void)
> {
> static const char default_cfg[] = "clientid test client\n";
> rtems_status_code sc;
> int fd;
> int rv;
>
On 20/8/21 4:55 am, Kinsey Moore wrote:
> On 8/19/2021 13:32, Gedare Bloom wrote:
>> On Thu, Aug 19, 2021 at 11:43 AM Kinsey Moore
>> wrote:
>>> I've seen these failures on my local system, in our CI, and on a build
>>> server that I sometimes
>>> use for development/testing so if it's a
On 20/8/21 2:58 am, Gedare Bloom wrote:
> I know I OK'd looking at the versal, but on second thought, I'd rather
> leave the xilinx-versal/tstqemu.yml alone until the BSP is finished,
> so revert that part of your patch. Sorry about that.
Agreed, please leave the Versal as is.
Chris
On 19/8/21 10:45 pm, Kinsey Moore wrote:
> On 8/18/2021 18:02, Chris Johns wrote:
>> On 19/8/21 5:49 am, Kinsey Moore wrote:
>>> On 8/18/2021 13:20, Chris Johns wrote:
On 19/8/21 3:41 am, Kinsey Moore wrote:
> This is functional on the ZynqMP board I currently have setup for testing
>
On 8/19/2021 13:32, Gedare Bloom wrote:
On Thu, Aug 19, 2021 at 11:43 AM Kinsey Moore wrote:
I've seen these failures on my local system, in our CI, and on a build
server that I sometimes
use for development/testing so if it's a configuration issue we're being
pretty consistent about
On Thu, Aug 19, 2021 at 11:43 AM Kinsey Moore wrote:
>
> I've seen these failures on my local system, in our CI, and on a build
> server that I sometimes
> use for development/testing so if it's a configuration issue we're being
> pretty consistent about
> misconfiguration across some pretty
I've seen these failures on my local system, in our CI, and on a build
server that I sometimes
use for development/testing so if it's a configuration issue we're being
pretty consistent about
misconfiguration across some pretty different environments (docker,
bare-metal, VM, different
OSs,
On Thu, Aug 19, 2021 at 11:51 AM Gedare Bloom wrote:
>
> I have no problem with this. I think it is sensible to look for
> python3 before python2. At some point we'll have to stop looking for
> python2 :)
That is further in the future than I would have thought based on the
CentOS project
Can you explain the process for generating the lists of indeterminate
test results?
I hate to circle this subject so many times, but is labeling sporadic
simulator failures as indeterminate results really the right thing to
do? Are these indeterminate tests reproducible on different
I have no problem with this. I think it is sensible to look for
python3 before python2. At some point we'll have to stop looking for
python2 :)
On Thu, Aug 19, 2021 at 3:24 AM Christian MAUDERER
wrote:
>
> PS: I had the problem on the 5 branch of RTEMS source builder. I think
> we should apply a
Added implementation of the pthread_cond_clockwait()
method to cpukit/posix/src/condclockwait.c. Additional
logic added to condwaitsupp.c to implement new method.
pthread_cond_clockwait() has been added to the Issue 8
POSIX Standard.
psxcond03 test added to testsuites/psxtests to test the
newly
Dr Joel,
Thank you for your feedback! This patch aims to implement
your suggested edits.
Sincerely,
Matt
Matt Joyce (1):
Added implementation / tests for pthread_cond_clockwait()
cpukit/include/rtems/posix/condimpl.h | 7 +-
cpukit/posix/src/condclockwait.c | 78 +++
- Change status of all spintrcritical tests to indeterminate, expanded upon
comments.
- Add indeterminate tests to xilinx-versal
---
spec/build/bsps/aarch64/a53/tsta53.yml| 40 ++---
spec/build/bsps/aarch64/xilinx-versal/tstqemu.yml | 54 ++-
Hallo Peter,
I do not know if this is best practice but I run the following code:
static void
default_network_dhcpcd(void)
{
static const char default_cfg[] = "clientid test client\n";
rtems_status_code sc;
int fd;
int rv;
ssize_t n;
struct stat statbuf;
if (ENOENT
CID 1506207: Buffer not null terminated
Closes #4491
---
tester/covoar/TraceWriterQEMU.cc | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/tester/covoar/TraceWriterQEMU.cc b/tester/covoar/TraceWriterQEMU.cc
index c417745..be9b6e1 100644
---
On Wed, Aug 18, 2021 at 8:44 PM Joel Sherrill wrote:
>
> On Wed, Aug 18, 2021 at 6:17 AM Matt Joyce wrote:
> >
> > Added implementation of the pthread_cond_clockwait()
> > method to cpukit/posix/src/condclockwait.c. Additional
> > logic added to condwaitsupp.c to implement new method.
> >
On 8/18/2021 18:02, Chris Johns wrote:
On 19/8/21 5:49 am, Kinsey Moore wrote:
On 8/18/2021 13:20, Chris Johns wrote:
On 19/8/21 3:41 am, Kinsey Moore wrote:
This is functional on the ZynqMP board I currently have setup for testing and on
ZynqMP QEMU except for the data corruption/loss
I'd like to use the DHCP option 17 (Root Path) to get a mount point for NFS
from the DHCP server.
I'm starting dhcp with "rtems_dhcpcd_start(NULL)" so it's starting with only
the argv array of {"dhcpcd", NULL }.
I *think* I need to start it with a customized rtems_dhcpcd_config that would
PS: I had the problem on the 5 branch of RTEMS source builder. I think
we should apply a patch to both: master and the 5 branch.
Am 19.08.21 um 10:34 schrieb Christian Mauderer:
More and more systems stop shipping python2. So we should start to
prefer python3 over python2. For building gdb it
More and more systems stop shipping python2. So we should start to
prefer python3 over python2. For building gdb it is not only necessary
to have a python binary installed, but also the matching python-devel
packet. On a lot of hosts that will now be more often python3-devel
and not python2-devel.
22 matches
Mail list logo
