From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: Andrew Fish <afish@apple.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "edk2-devel@lists.01.org (edk2-devel@ml01.01.org)"
<edk2-devel@ml01.01.org>
Subject: Re: [edk2-staging] Create new edk2-test branch
Date: Thu, 26 Jan 2017 19:36:03 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5648AC4D1@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <48BC9DA9-3CAC-45AD-9EE5-B499F5C61B9B@apple.com>
Andrew,
Was there supposed to be an attachment for the TestCasePkg fixes?
Thanks,
Mike
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Andrew
> Fish
> Sent: Thursday, January 26, 2017 10:26 AM
> To: Kinney, Michael D <michael.d.kinney@intel.com>
> Cc: edk2-devel@lists.01.org (edk2-devel@ml01.01.org) <edk2-devel@ml01.01.org>
> Subject: Re: [edk2] [edk2-staging] Create new edk2-test branch
>
>
> > On Jan 26, 2017, at 9:43 AM, Kinney, Michael D <michael.d.kinney@intel.com>
> wrote:
> >
> > Andrew,
> >
> > Thanks for the patch for the additional compiler compatibility. I will review
> and check in.
> >
>
> Mike,
>
> Here is the TestCasePkg fixes.
>
>
> > I will also correct the Readme.md and add the Unix setup info.
> >
>
> Thanks.
>
> > I am aware that the current post build step is a batch file. We need to update
> that to be compatible with all supported development operating systems.
> >
>
> Is there a way to make the POSTBUILD step OS or Toolchain specific?
>
> Thanks,
>
> Andrew Fish
>
> PS For both contributions....
>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Andrew Fish <afish@apple.com>
>
> > Mike
> >
> > <>From: afish@apple.com [mailto:afish@apple.com]
> > Sent: Thursday, January 26, 2017 1:58 AM
> > To: Kinney, Michael D <michael.d.kinney@intel.com>
> > Cc: edk2-devel@lists.01.org (edk2-devel@ml01.01.org) <edk2-devel@ml01.01.org>
> > Subject: Re: [edk2] [edk2-staging] Create new edk2-test branch
> >
> >
> > On Jan 25, 2017, at 2:05 PM, Kinney, Michael D <michael.d.kinney@intel.com
> <mailto:michael.d.kinney@intel.com>> wrote:
> >
> > The initial version of the edk2-test branch is checked in at:
> >
> > https://github.com/tianocore/edk2-staging/tree/edk2-test
> <https://github.com/tianocore/edk2-staging/tree/edk2-test>
> >
> > Mike,
> >
> > I'm messing around with trying this on macOS.
> >
> > git clone https://github.com/tianocore/edk2.git
> <https://github.com/tianocore/edk2.git>
> > git clone https://github.com/tianocore/edk2-staging.git
> <https://github.com/tianocore/edk2-staging.git> --brach edk2-test
> >
> > set WORKSPACE=%CD%
> > set EDK_TOOLS_PATH=%WORKSPACE%\edk2\BaseTools
> > set PACKAGES_PATH=%WORKSPACE%\edk2;%WORKSPACE%\edk2-staging
> > set EDK_TOOLS_BIN=%WORKSPACE%\BaseTools\BinWrappers\WindowsLike
> > path=%path%;%WORKSPACE%\edk2\BaseTools\Bin\Win32
> >
> > cd edk2
> > edkSetup.bat
> >
> > build -a IA32 -a X64 -t VS2015x86 -p TestFrameworkPkg/TestFrameworkPkg.dsc
> > build -a IA32 -a X64 -t VS2015x86 -p TestCasePkg/TestCasePkg.dsc
> > At least with edksetup.sh this pattern fails as CONF_PATH is not set and it
> gets set in WORKSPACE. Maybe your terminal window was not clean when you tested?
> >
> > Also is it correct that EDK_TOOLS_BIN is not in EDK_TOOLS_PATH?
> >
> > On the Unix side this works for me:
> >
> > export WORKSPACE=`pwd`
> > export EDK_TOOLS_PATH="$WORKSPACE/edk2/BaseTools"
> > export PACKAGES_PATH="$WORKSPACE/edk2:$WORKSPACE/edk2-staging"
> > export EDK_TOOLS_BIN="$$WORKSPACE/edk2/BaseTools/BinWrappers/PosixLike"
> > export CONF_PATH="$WORKSPACE/edk2/Conf"
> > export PATH="$PATH:$EDK_TOOLS_BIN"
> >
> > Lots of minor change. Here is a patch for: >build -a IA32 -a X64 -t XCODE5 -p
> TestFrameworkPkg/TestFrameworkPkg.dsc
> >
> > I get this far. This looks like a DOS batch file.
> >
> > /bin/bash: /Users/andrewfish/work/src/TestFramework/edk2-
> staging/TestFrameworkPkg/GenFramework.cmd: Permission denied
> >
> >
> > Thanks,
> >
> > Andrew Fish
> >
> >
> >
> > Mike
> >
> >
> > -----Original Message-----
> > From: Kinney, Michael D
> > Sent: Tuesday, January 24, 2017 11:07 PM
> > To: edk2-devel@lists.01.org <mailto:edk2-devel@lists.01.org> (edk2-
> devel@ml01.01.org <mailto:edk2-devel@ml01.01.org>) <edk2-devel@ml01.01.org
> <mailto:edk2-devel@ml01.01.org>>;
> > Kinney, Michael D <michael.d.kinney@intel.com
> <mailto:michael.d.kinney@intel.com>>
> > Subject: [edk2-staging] Create new edk2-test branch
> >
> > I am creating a new branch in edk2-staging called edk2-test.
> >
> > The purpose of this branch is to develop a test harness,
> > test case SDK, and library of test cases that can be used
> > as part of edk2 validation.
> >
> > The initial version of this test harness is compatible with
> > binary releases of the PI SCTs and UEFI SCTs, are native
> > edk2 packages with no dependencies on the EdkCompatibilityPkg,
> > and the test harness runs using the latest version of the
> > UEFI Shell.
> >
> > Additional work items:
> > * Update to take advantage of latest edk2 features/libraries.
> > * Update for all supported CPU types
> > * Update for all supported compilers
> > * Review initial test harness features and determine
> > what features should be dropped and what new features
> > should be added.
> > * Determine where the test harness, test case SDK, and
> > test cases should live once the initial functional and
> > quality criteria are met. Could be packages in the
> > edk2 repo or packages in a new edk2-test repo. Other
> > options???
> > * Resolve compatibility issues with binary releases of the
> > PI SCTs and UEFI SCTs.
> > * Update test harness to support PEI tests
> > * Update test harness to support Runtime tests
> > * Update test harness to support SMM tests
> > * Optimize performance of the test harness and tests.
> >
> > Please contact me if you are interested in helping with the
> > test harness, the test case SDK, or the development of
> > test cases.
> >
> > Thanks,
> >
> > Mike
> >
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.01.org <mailto:edk2-devel@lists.01.org>
> > https://lists.01.org/mailman/listinfo/edk2-devel
> <https://lists.01.org/mailman/listinfo/edk2-devel>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-01-26 19:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 7:07 [edk2-staging] Create new edk2-test branch Kinney, Michael D
2017-01-25 22:05 ` Kinney, Michael D
2017-01-26 9:57 ` Andrew Fish
2017-01-26 14:15 ` Rudra ठाकुर
2017-01-26 17:56 ` Kinney, Michael D
2017-01-26 17:43 ` Kinney, Michael D
2017-01-26 18:25 ` Andrew Fish
2017-01-26 19:36 ` Kinney, Michael D [this message]
2017-01-26 19:37 ` Andrew Fish
2017-01-26 19:39 ` Andrew Fish
2017-01-26 17:11 ` Supreeth Venkatesh
2017-01-26 17:54 ` Kinney, Michael D
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=E92EE9817A31E24EB0585FDF735412F5648AC4D1@ORSMSX113.amr.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