Closed
Bug 1060310
Opened 11 years ago
Closed 11 years ago
mozharness configuration is writable in query_abs_dir()
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: massimo, Unassigned)
References
Details
Attachments
(1 file)
|
776 bytes,
patch
|
jlund
:
review+
massimo
:
checked-in+
|
Details | Diff | Splinter Review |
In BaseScript.__init__, we call query_abs_dis() before locking the configuration (_pre_config_lock), so in query_abs_dir(), the configuration is still writable.
http://hg.mozilla.org/build/mozharness/file/461eb9ef2e34/mozharness/base/script.py#l1328
| Reporter | ||
Comment 1•11 years ago
|
||
removed call to query_abs_dirs() in new_log_obj
Attachment #8481235 -
Flags: review?(jlund)
Comment 2•11 years ago
|
||
Comment on attachment 8481235 [details] [diff] [review]
[mozharness] Bug 1060310 - lock configuration before calling abs_query_dirs().patch
Review of attachment 8481235 [details] [diff] [review]:
-----------------------------------------------------------------
we discussed this earlier. I think this is the right thing to do. The downside is we define this in two places now. Although I think we have only ever used it in base_work_dir and it's still configurable within base_work_dir via c['log_dir'].
This would be a big mess if we landed this and missed something. Think we should trigger a job or two within cypress and then confirm that the logs are uploaded and the log_dir is where its supposed to be on the respective slave?
Attachment #8481235 -
Flags: review?(jlund) → review+
| Reporter | ||
Updated•11 years ago
|
Attachment #8481235 -
Flags: checked-in+
| Reporter | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•