daily.sh is opaque to developers
Bug #712282 reported by
Stuart Bishop
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Critical
|
William Grant | ||
Bug Description
Developers have no way of seeing what daily.sh is doing until after the fact. This has contributed to the current problem where daily.sh is taking more than a day to complete.
Simple improvements:
- it needs to echo "Running foo `date`" >> /srv/whatever/
- all the scripts need --log-file=
- New logs need to be synced regularly to devpad.
- Existing jobs taking 'too long' need to be moved out of nightly.sh and bugs opened. We could create a weekly.sh and run them once a week until performance improves, or install them as separate cron jobs to be run in parallel.
Related branches
lp:~wgrant/launchpad/nightly.sh-fixes
- Tom Haddon: Approve
- Stuart Bishop (community): Approve
-
Diff: 115 lines (+42/-36)1 file modifiedcronscripts/nightly.sh (+42/-36)
Revision history for this message
| Stuart Bishop (stub) wrote | #1 |
| Changed in launchpad: | |
| importance: | Undecided → Critical |
| status: | New → Triaged |
| Changed in launchpad: | |
| assignee: | nobody → William Grant (wgrant) |
| status: | Triaged → In Progress |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #2 |
| Changed in launchpad: | |
| milestone: | none → 11.02 |
| tags: | added: qa-untestable |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Logs should go in /srv/launchpad.