From: "Zhang, Shenglei" <shenglei.zhang@intel.com>
To: Sean <sean.brogan@microsoft.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Zhang, Shenglei" <shenglei.zhang@intel.com>
Subject: Re: [edk2-devel] [PATCH v1 0/6] Edk2 Platform and Core CI for ArmVirtPkg, EmulatorPkg, and OvmfPkg
Date: Wed, 15 Apr 2020 07:13:44 +0000 [thread overview]
Message-ID: <C0706E73DB8C124D9B9C38AA364E5D5E0605EDC9@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <31845.1586933495148991333@groups.io>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
Sorry for that. I didn’t make the query clear.
· what do you mean "test for the adding pipelines"? I mean when you add a new pipline how do you know it can work well on github and all steps work correctly. Do you have test on a local server or something?
Thanks,
Shenglei
From: sean.brogan via [] [mailto:sean.brogan=microsoft.com@[]]
Sent: Wednesday, April 15, 2020 2:52 PM
To: Zhang; Zhang, Shenglei <shenglei.zhang@intel.com>; devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH v1 0/6] Edk2 Platform and Core CI for ArmVirtPkg, EmulatorPkg, and OvmfPkg
what do you mean "test for the adding pipelines"?
The pipeline currently builds the platforms and then runs them to the shell where it has a startup.nsh which does reset -h.
If the boot fails or hangs the task will timeout in 1 minute and then fail.
Thanks
Sean
[-- Attachment #2: Type: text/html, Size: 6538 bytes --]
next prev parent reply other threads:[~2020-04-15 7:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 18:13 [PATCH v1 0/6] Edk2 Platform and Core CI for ArmVirtPkg, EmulatorPkg, and OvmfPkg Michael Kubacki
2020-04-14 8:31 ` [edk2-devel] " Zhang, Shenglei
2020-04-15 6:51 ` Sean
2020-04-15 7:13 ` Zhang, Shenglei [this message]
2020-04-15 16:15 ` Sean
2020-04-15 20:22 ` Rebecca Cran
2020-04-15 20:44 ` Sean
2020-04-15 21:08 ` Rebecca Cran
2020-04-15 21:14 ` Sean
2020-04-17 7:39 ` Zhang, Shenglei
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-list 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=C0706E73DB8C124D9B9C38AA364E5D5E0605EDC9@SHSMSX104.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/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