oops while using the code review

Asked by Seth Arnold

Hello, I tried to review a co-worker's merge request and got an emailed oops. This is neat, I don't remember getting one emailed to me before! :)

OOPS-b92bbeb77e100b85fcef172f1217c9c7

Thanks

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Jürgen Gmach (jugmac00) said :
#1

Hey Seth,
I recall that I saw this error message earlier, but I cannot recall the exact reason for it.

The error message says:

```
  InvalidTransition: Transition from Completed to Running is invalid.

    Traceback (most recent call last):
  Module lazr.jobrunner.jobrunner, line 194, in runJobHandleError
    self.runJob(job, fallback)
  Module lp.services.job.runner, line 391, in runJob
    super().runJob(IRunnableJob(job), fallback)
  Module lazr.jobrunner.jobrunner, line 159, in runJob
    job.start(manage_transaction=True)
  Module lp.services.job.runner, line 326, in start
    self.job.start(manage_transaction=manage_transaction)
  Module lp.services.job.model.job, line 183, in start
    self._set_status(JobStatus.RUNNING)
  Module lp.services.job.model.job, line 106, in _set_status
    raise InvalidTransition(self._status, status)
lp.services.job.model.job.InvalidTransition: Transition from Completed to Running is invalid.
```

Could you please reload the page and try again? And then get back to us whether this is a persistent error.

Revision history for this message
Seth Arnold (seth-arnold) said :
#2

I submitted another review on the merge request in question https://code.launchpad.net/~eslerm/ubuntu-cve-tracker/+git/ubuntu-cve-tracker/+merge/459486/comments/1235415

I waited an hour and haven't yet received the "Launchpad internal error" email that I got yesterday.

Thanks

Revision history for this message
Jürgen Gmach (jugmac00) said :
#3

Is there anything else we can do right now?

Unfortunately, I do not think we have currently the capacity to investigate these kind of bugs.

But - I think it would make a lot of sense to have a bug report, where we at least document the workaround, ie retrying, and eventually look into it when we have some spare cycles.

Would you mind creating that bug report and please include the oops?

Thank you, and sorry for the inconveniences.

Can you help with this problem?

Provide an answer of your own, or ask Seth Arnold for more information if necessary.

To post a message you must log in.