Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B bull
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 175
    • Issues 175
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OptimalBits
  • bull
  • Issues
  • #230
Closed
Open
Issue created Jan 12, 2016 by Administrator@rootContributor

Stacktrace is undefined in failed jobs

Created by: avermeil

Hi!

When jobs fail, the stacktrace field in the job hash in redis stays "undefined". It looks to me like this is the fault of a line in the lua script on line 404 of job.js, which overwrites the stacktrace field with a value coming from the argument context, which isn't defined when _moveToSet() is called by moveToFailed().

Since the stacktrace field is already set by _saveAttempt(), just commenting out the that line of the lua script seems to fix it:

//redis.call("HSET", KEYS[3], "stacktrace", ARGV[1])

But I might be missing something.

Any ideas on what is going on here?

Assignee
Assign to
Time tracking