Closed
Bug 1267913
Opened 10 years ago
Closed 9 years ago
Windows AWS instances come up with nothing in hg-shared
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Unassigned)
Details
Attachments
(1 file)
I've checked this by looking at the first job a machine does on try, and also by inspecting y-2008-spot and b-2008-spot instances just after they come up - c:\builds\hg-shared is empty, despite all the effort to populate it.
| Reporter | ||
Comment 1•10 years ago
|
||
grenade, am I following the code correctly here .....
It looks like we populate hg-shared with Get-SourceCaches at
https://github.com/mozilla/build-cloud-tools/blob/master/configs/b-2008.user-data#L114
and then blow them away again inside Prep-Golden with Flush-BuildFiles at
https://github.com/mozilla/build-cloud-tools/blob/master/configs/Ec2UserdataUtils.psm1#L845
Do you recall if there is some reason for this ordering, or perhaps things got re-arranged at some point and we missed the regression ?
Flags: needinfo?(rthijssen)
Comment 2•10 years ago
|
||
nthomas++
thanks for the debugging!
pr submitted
Flags: needinfo?(rthijssen)
Attachment #8748625 -
Flags: review?(catlee)
Comment 3•10 years ago
|
||
Comment on attachment 8748625 [details] [review]
https://github.com/mozilla/build-cloud-tools/pull/212
pr merged
Attachment #8748625 -
Flags: review?(catlee)
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 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
•