Closed
Bug 1225084
Opened 9 years ago
Closed 9 years ago
Fix abs_log_dir to be located under abs_work_dir but not base_work_dir
Categories
(Release Engineering :: Applications: MozharnessCore, defect)
Release Engineering
Applications: MozharnessCore
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: whimboo, Unassigned)
Details
IMO it doesn't make sense to let the logs to be created under the base_work_dir which usually is the base directory of base_work_dir. Instead all the logs should be created inside the abs_work_dir folder which usually is base_work_dir/build or something completely different. So logs should lay beside all other files for a specific build. Jordan, if you agree with that I can get this fixed.
Flags: needinfo?(jlund)
Reporter | ||
Comment 1•9 years ago
|
||
I want to add that I assume the current behavior has been added by accident: https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/mozharness/base/script.py#1772
Comment 2•9 years ago
|
||
Note: The clobber action nukes the abs_work_dir, so if logs/ is under abs_work_dir, you'll nuke your current job's logs.
Reporter | ||
Comment 3•9 years ago
|
||
Oh I see. In that case it makes sense. Thanks Aki.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(jlund)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•