public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ser, Simon" <simon.ser@intel.com>
To: "guillaume.tucker@collabora.com" <guillaume.tucker@collabora.com>,
	"Hiler, Arkadiusz" <arkadiusz.hiler@intel.com>,
	"Latvala, Petri" <petri.latvala@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] gitlab-ci: add tests for MIPS
Date: Fri, 28 Jun 2019 06:46:41 +0000	[thread overview]
Message-ID: <3b172cc9bdb3c8b201516aa09c09efd8c84fe4e9.camel@intel.com> (raw)
In-Reply-To: <40326e43def140d19e0d57604e41aa10d1466f7a.1561642240.git.guillaume.tucker@collabora.com>

On Thu, 2019-06-27 at 14:30 +0100, Guillaume Tucker wrote:
> Use the libatomic1:mips package only in the Debian Stretch Docker
> image for MIPS and add Gitlab CI step to run tests on MIPS.
> 
> Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>

And pushed:

To gitlab.freedesktop.org:drm/igt-gpu-tools.git
   3c4edeba35ac..5f6cf7070b24  master -> master

Thanks!

> ---
>  .gitlab-ci.yml         | 14 ++++++++++++++
>  Dockerfile.debian-mips |  2 +-
>  2 files changed, 15 insertions(+), 1 deletion(-)
> 
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 37184b98f5da..665fbb79c523 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -173,6 +173,20 @@ test:ninja-test-armhf:
>        - build
>      when: on_failure
>  
> +test:ninja-test-mips:
> +  image: $CI_REGISTRY/$CI_PROJECT_PATH/igt-debian-mips:latest
> +  dependencies:
> +    - build:tests-debian-meson-mips
> +  stage: test
> +  script:
> +    - export PKG_CONFIG_PATH=/usr/lib/mips-linux-gnu/pkgconfig/
> +    - env > build/envdump.txt
> +    - ninja -C build test
> +  artifacts:
> +    paths:
> +      - build
> +    when: on_failure
> +
>  test:test-list-diff:
>    dependencies:
>      - build:tests-debian-autotools
> diff --git a/Dockerfile.debian-mips b/Dockerfile.debian-mips
> index ebe08db644ea..ee29f5f4ccda 100644
> --- a/Dockerfile.debian-mips
> +++ b/Dockerfile.debian-mips
> @@ -5,7 +5,6 @@ RUN apt-get install -y \
>  			flex \
>  			bison \
>  			pkg-config \
> -			libatomic1 \
>  			x11proto-dri2-dev \
>  			python-docutils \
>  			valgrind \
> @@ -15,6 +14,7 @@ RUN dpkg --add-architecture mips
>  RUN apt-get update
>  RUN apt-get install -y \
>  			gcc-mips-linux-gnu \
> +			libatomic1:mips \
>  			libpciaccess-dev:mips \
>  			libkmod-dev:mips \
>  			libprocps-dev:mips \
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2019-06-28  6:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27 13:30 [igt-dev] [PATCH i-g-t] gitlab-ci: add tests for MIPS Guillaume Tucker
2019-06-27 14:45 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-06-27 14:51 ` [igt-dev] [PATCH i-g-t] " Ser, Simon
2019-06-28  6:47   ` Arkadiusz Hiler
2019-06-28  6:46 ` Ser, Simon [this message]
2019-06-28 13:21 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork

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=3b172cc9bdb3c8b201516aa09c09efd8c84fe4e9.camel@intel.com \
    --to=simon.ser@intel.com \
    --cc=arkadiusz.hiler@intel.com \
    --cc=guillaume.tucker@collabora.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=petri.latvala@intel.com \
    /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