poweroff and reboot logs are never attached

Bug #1085833 reported by Ara Pulido
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Checkbox
Fix Released
Undecided
Unassigned

Bug Description

Running checkbox 0.15+bzr1834+201211241747~precise1

They are wrongly created at my home directory, rather than $CHECKBOX_DATA

The attachment job tries to look in the correct one ($CHECKBOX_DATA), but there's nothing there.

Looking at the log created under my home directory, it looks like $CHECKBOX_DATA is not correctly replaced:

Exec=sudo /usr/bin/python /usr/lib/checkbox/bin/pm_test -r 0 -w 60 --hardware-delay 30 --pm-delay 5 --min-pm-time 58 --max-pm-time 300 --append --total 1 --start 1354526914 --pm-timestamp 1354526914 --log-level=debug --log-dir= poweroff

tar: Removing leading `/' from member names
tar: /home/ara/.checkbox/*poweroff.1.log: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

tar: Removing leading `/' from member names
tar: /home/ara/.checkbox/*reboot.1.log: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

Related branches

Ara Pulido (ara)
Changed in checkbox:
status: New → Invalid
Revision history for this message
Ara Pulido (ara) wrote :

They are wrongly created at my home directory, rather than $CHECKBOX_DATA

The attachment job tries to look in the correct one ($CHECKBOX_DATA), but there's nothing there.

Looking at the log created under my home directory, it looks like $CHECKBOX_DATA is not correctly replaced:

Exec=sudo /usr/bin/python /usr/lib/checkbox/bin/pm_test -r 0 -w 60 --hardware-delay 30 --pm-delay 5 --min-pm-time 58 --max-pm-time 300 --append --total 1 --start 1354526914 --pm-timestamp 1354526914 --log-level=debug --log-dir= poweroff

Changed in checkbox:
status: Invalid → Triaged
description: updated
Revision history for this message
Daniel Manrique (roadmr) wrote :

The job definitions for power-management/poweroff and power-management/reboot lack the environ clause which ensures that jobs with user: root have access to checkbox environment variables. Something like this in the job definitions would help:

environ: CHECKBOX_DATA

Zygmunt Krynicki (zyga)
Changed in checkbox:
status: Triaged → Fix Committed
Changed in checkbox:
status: Fix Committed → Fix Released
Changed in checkbox:
status: Fix Released → Fix Committed
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.