On 8/27/2021 19:01, Chris Johns wrote:
On 27/8/21 9:36 am, Kinsey Moore wrote:
Since I'm working on SMP and I've had some of those tests failing
sporadically
as well, I took a dive into smpschededf01.exe on AArch64 and the issue that
particular test seems to be encountering is a mismatch
On 27/8/21 9:36 am, Kinsey Moore wrote:
> On 8/20/2021 22:06, Chris Johns wrote:
>> On 21/8/21 2:38 am, Kinsey Moore wrote:
>>> On 8/19/2021 18:03, Chris Johns wrote:
>>> My comment in that regard was that other system
>>> loading (or multiple simultaneous test runs) can also cause the same
On 8/20/2021 22:06, Chris Johns wrote:
On 21/8/21 2:38 am, Kinsey Moore wrote:
On 8/19/2021 18:03, Chris Johns wrote:
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
On 21/8/21 2:38 am, Kinsey Moore wrote:
> On 8/19/2021 18:03, Chris Johns wrote:
>> 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 8/19/2021 18:03, Chris Johns wrote:
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
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 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,
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
- 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 ++-
12 matches
Mail list logo
