Value of key 'io_log_filename' is of incorrect type list, session cannot be resumed after the poweroff test

[Po-Hsu Lin]

After the poweroff test, I was unable to resume the session with the following error message

ubuntu@201301-12636:~$ checkbox-cli
=========================[ Resume Incomplete Session ]==========================
There is 1 incomplete session that might be resumed
Do you want to resume session 'pbox-37hjv1ub'?
  r => resume this session
  n => next session
  c => create new session
[rnc]: r
Value of key 'io_log_filename' is of incorrect type list
This session cannot be resumed

Since I was blocked by this issue twice, I would set the priority to "Critical"

[Zygmunt Krynicki (zyga)]

Thanks for reporting this.

I've fixed the cause of this bug a while ago while working on checkbox-cli --new-ui. It should *not* appear anymore in newly created sessions. It is very well possible to discover older sessions that still have this problem (as the solution didn't contain a fix for existing stored sessions). If you think this session was created recently then please reopen this issue, otherwise I'd like to close it.

[Po-Hsu Lin (cypressyew)]

Yes,
this happened today on a fresh-install system, with dev ppa (bzr3070)

checkbox 0.17.10+bzr2820+pkg76+legacy1~ubuntu14.04.1
checkbox-certification 0.20+bzr652+201406121331~ubuntu14.04.1
checkbox-certification-client 0.20+bzr652+201406121331~ubuntu14.04.1
checkbox-certification-tools 0.20+bzr652+201406121331~ubuntu14.04.1
checkbox-gui 0.17.9~dev+bzr3070+pkg2~ubuntu14.04.1
checkbox-ng 0.4~dev+bzr3070+pkg7~ubuntu14.04.1
checkbox-ng-service 0.4~dev+bzr3070+pkg7~ubuntu14.04.1
checkbox-qt 0.17.10+bzr2820+pkg76+legacy1~ubuntu14.04.1
plainbox-provider-checkbox 0.5~dev+bzr3070+pkg5~ubuntu14.04.1
python3-checkbox 0.17.10+bzr2820+pkg76+legacy1~ubuntu14.04.1
python3-checkbox-ng 0.4~dev+bzr3070+pkg7~ubuntu14.04.1
python3-checkbox-support 0.3~dev+bzr3070+pkg3~ubuntu14.04.1
plainbox-provider-certification-client 0.1~dev+bzr3070+pkg16~ubuntu14.04.1
plainbox-provider-resource-generic 0.4~dev+bzr3070+pkg5~ubuntu14.04.1
plainbox-secure-policy 0.6~dev+bzr3070+pkg4~ubuntu14.04.1
python3-plainbox 0.6~dev+bzr3070+pkg4~ubuntu14.04.1

I started with checkbox-cli, as --new-ui is a default flag now.

[Zygmunt Krynicki (zyga)]

Value of key 'io_log_filename' is of incorrect type list
This session cannot be resumed

^^ I misread that to 'null'. List is definitely something new and strange.

[Zygmunt Krynicki (zyga)]

So this seems to be buried inside the session:

         "2013.com.canonical.certification::suspend/1_display_after_suspend_Wrestler_Radeon_HD_7310" : [
            {
               "outcome" : "pass",
               "comments" : null,
               "execution_duration" : 1.81198120117188e-05,
               "io_log_filename" : [],
               "return_code" : null
            }
         ],

I have no idea what might cause io_log_filename to be [] there

[Po-Hsu Lin (cypressyew)]

Workaround to bypass this job:
Since this is a user-verify job, it will ask you to hit enter and start testing.
When asked to do so, you could bypass it by Ctrl+C , and resume the session.
Now it will allow you to select the test result (mark it as passed and continue) but without running that job.

[Zygmunt Krynicki (zyga)]

Thanks for the hint. I will concentrate on user-verify jobs and try to
debug this problem further.

On Tue, Jun 17, 2014 at 8:02 AM, Po-Hsu Lin <email address hidden>
wrote:

> Workaround to bypass this job:
> Since this is a user-verify job, it will ask you to hit enter and start
> testing.
> When asked to do so, you could bypass it by Ctrl+C , and resume the
> session.
> Now it will allow you to select the test result (mark it as passed and
> continue) but without running that job.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1330359
>
> Title:
> Value of key 'io_log_filename' is of incorrect type list, session
> cannot be resumed after the poweroff test
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/plainbox/+bug/1330359/+subscriptions
>

[Zygmunt Krynicki (zyga)]

Woot, solved it. Let me verify my theory and propose a fix

[Zygmunt Krynicki (zyga)]

Every time after I write a comment like that, the bus factor increases so here's the working theory:

job.command = None
return_code, record_path = JobRunner._run_command(job, config)
assert record_path == ()

# Which should never happen, static typing would have caught that.