cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Chris Paterson <Chris.Paterson2@renesas.com>
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] realtime on de0-nano bisection
Date: Mon, 23 Mar 2020 23:17:20 +0100	[thread overview]
Message-ID: <20200323221720.GB7808@duo.ucw.cz> (raw)
In-Reply-To: <TYAPR01MB2285AA6A0ED614311F861538B7F50@TYAPR01MB2285.jpnprd01.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 709 bytes --]

Hi!

> > In the meantime:
> >
> > https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/478548891
> > https://lava.ciplatform.org/scheduler/job/13037
> >
> > So yes, it seems this is not reproducible. Is it easy to make the test
> > run .. say 5 times?
> 
> Just repeat the test case name 5 times in the gitlab-ci file.
> E.g. https://gitlab.com/cip-project/cip-kernel/linux-cip/-/commit/791b84001ce05a9a26117a0c2de0e7250b343960
>

Thanks for useful trick. I'll try to remember it in case it is needed
again.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

      reply	other threads:[~2020-03-23 22:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 11:05 [cip-dev] realtime on de0-nano bisection Pavel Machek
2020-03-19 11:23 ` Chris Paterson
2020-03-19 11:34   ` Chris Paterson
2020-03-19 16:13   ` Chris Paterson
2020-03-19 21:07     ` Ben Hutchings
2020-03-19 21:23       ` Pavel Machek
2020-03-20  9:56         ` Chris Paterson
2020-03-23 22:17           ` Pavel Machek [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200323221720.GB7808@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=Chris.Paterson2@renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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 NNTP newsgroup(s).