This job does not have a trace

GitLab CI/CD
1

Replace this template with your information

Jobs stopped showing trace:

  • I didn’t do anything with .gitlab-ci.yaml, but at one point the traces stopped showing.
    screen *

    • GitLab: GitLab Enterprise Edition [13.4.2-ee]
    • Runner: executor = “shell”

  • *.gitlab-ci.yaml:

test:
script: cat index.php
tags: [testing]

  • Could you tell me where to look for the problem?
2 Likes
2

Having the same problem lately

Bildschirmfoto vom 2020-10-06 10-02-26
Bildschirmfoto vom 2020-10-06 10-02-26698×506 14.6 KB

3

Same problems on many Pipelines, on many projects, under Gitlab CE 13.4.2 (b08b36dccc3)

4

Hi everyone, thanks for bringing this up. I’d like to get to the bottom of this.

  • Is it correct that you are all using GitLab 13.4.2?
  • When did you first notice this issue? Did you see this problem before upgrading to 13.4.2?
  • What version of GitLab Runner (13.4, 13.3 etc), and what GitLab runner executor are you using (shell, docker, etc.)?

This should help troubleshoot the issue and investigate any potential bugs. Thanks in advance.

5

Hi, and thanks for your quick reply.

My gitlab-runner was 11.1.0 (I don’t know why /usr/local/bin/gitlab-runner was used instead of /usr/bin/gitlab-runner).

I have fixed this mistake and upgraded to gitlab-runner 13.4.1 (amd64).

Now it seems to be working better (I will monitor jobs today because failures was partially random).

1 Like
6

Thanks, my runner was not updated either.

7

Version 13.4.7

Yesterday & today as I’ve only just started trying to use CI/CD.

I’m using the Docker runner. I was using :latest but I’ve now switched it to ubuntu-v13.4.1 (there doesn’t seem to be a 13.4.7).

The job runs and I can see the output but, sometimes, the display of that output just vanishes and gets replaced with the “This job does not have a trace” message. If I leave the browser page open, sometimes it goes back to displaying the output again. All a bit weird …

8

any update about this?

I’m getting this problem too…using gitlab.com and installing the latest gitlab-runner in a ec2 instance, running a shell runner… my jobs passed but it doesn’t show any output…

are there any way to show logs or some runner information in order to find the possible error?

thank you…

9

We get this issue in our self managed GitLab too. We updated from version 12 to 14 around 3 weeks ago.

10

This problem is caused by the inconsistency between the database’s ci_job_artifacts’s created_at and your local time zone

see timestamps are inconsistent when the timezone set is not UTC (#26320) · Issues · GitLab.org / GitLab · GitLab

1 Like