[igt-dev] [PATCH i-g-t] gitlab-CI: Keep build artifacts when arm64-test fails

[igt-dev] [PATCH i-g-t] gitlab-CI: Keep build artifacts when arm64-test fails

[Daniel Vetter]

There's something very funky going on with the occasional commit
consistently failing, e.g.

https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/jobs/51208

We need to catch it to understand what happens.

v2: Also dump the environment (Petri)

Cc: Petri Latvala <petri.latvala@intel.com>
Acked-by: Petri Latvala <petri.latvala@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
---
 .gitlab-ci.yml | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 0e55e3157a69..bcc32cd9c71f 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -97,7 +97,13 @@ test:ninja-test-arm64:
   dependencies:
     - build:tests-debian-meson-arm64
   stage: test
-  script: ninja -C build test
+  script:
+    - env > build/envdump.txt
+    - ninja -C build test
+  artifacts:
+    paths:
+      - build
+    when: on_failure
 
 test:test-list-diff:
   dependencies:
-- 
2.19.1

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

[igt-dev] ✗ Fi.CI.BAT: failure for gitlab-CI: Keep build artifacts when arm64-test fails

[Patchwork]

== Series Details ==

Series: gitlab-CI: Keep build artifacts when arm64-test fails
URL   : https://patchwork.freedesktop.org/series/53255/
State : failure

== Summary ==

Applying: gitlab-CI: Keep build artifacts when arm64-test fails
Patch failed at 0001 gitlab-CI: Keep build artifacts when arm64-test fails
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

Re: [igt-dev] [PATCH i-g-t] gitlab-CI: Keep build artifacts when arm64-test fails

[Daniel Vetter]

On Thu, Nov 29, 2018 at 04:24:04PM +0100, Daniel Vetter wrote:
> There's something very funky going on with the occasional commit
> consistently failing, e.g.
> 
> https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/jobs/51208
> 
> We need to catch it to understand what happens.
> 
> v2: Also dump the environment (Petri)
> 
> Cc: Petri Latvala <petri.latvala@intel.com>
> Acked-by: Petri Latvala <petri.latvala@intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>

Just crossed my mind: Should we do this for all jobs at the test stage, in
case of failures? For testcases usually the log output from ninja isn't
good enough (as opposed to compile fail, that's generally totally clear
with just the gcc output).
-Daniel

> ---
>  .gitlab-ci.yml | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 0e55e3157a69..bcc32cd9c71f 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -97,7 +97,13 @@ test:ninja-test-arm64:
>    dependencies:
>      - build:tests-debian-meson-arm64
>    stage: test
> -  script: ninja -C build test
> +  script:
> +    - env > build/envdump.txt
> +    - ninja -C build test
> +  artifacts:
> +    paths:
> +      - build
> +    when: on_failure
>  
>  test:test-list-diff:
>    dependencies:
> -- 
> 2.19.1
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev