Closed Bug 680561 Opened 10 years ago Closed 10 years ago

proxy.flg is being set in the wrong directory

Categories

(Release Engineering :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bear, Assigned: bear)

Details

(Whiteboard: [android][tegra][sut_tools][android_tier_1])

Attachments

(1 file)

aki discovered that something in sut_tools or clientproxy is setting proxy.flg in the wrong location:

bash-3.2$ find . -name proxy.flg
./tegra-079/test/proxy.flg
./tegra-080/test/proxy.flg
./tegra-081/test/proxy.flg
./tegra-082/test/proxy.flg
./tegra-083/test/proxy.flg
./tegra-084/proxy.flg
./tegra-084/test/proxy.flg
./tegra-085/test/proxy.flg
./tegra-086/proxy.flg
./tegra-086/test/proxy.flg
./tegra-087/test/proxy.flg
./tegra-088/test/proxy.flg
./tegra-089/test/proxy.flg
./tegra-090/test/proxy.flg
./tegra-091/test/proxy.flg
bash-3.2$ ls -la tegra-091/test/*.flg
-rw-------  1 cltbld  admin  0 Aug 18 16:25 tegra-091/test/proxy.flg

all of the ./*/test/proxy.flg files should be ./*/proxy.flg - it smells like a broken relative path
Assignee: nobody → bear
Whiteboard: [android][tegra][sut_tools]
Whiteboard: [android][tegra][sut_tools] → [android][tegra][sut_tools][android_tier_1]
proxy.flg is being created in the wrong directory - workdir parameter in the step that calls reboot.py was incorrect
Attachment #555010 - Flags: review?(aki)
Comment on attachment 555010 [details] [diff] [review]
change workdir for reboot.py call step

I think that'll fix it :)
Land this puppy unless you plan on testing somewhere first.
Attachment #555010 - Flags: review?(aki) → review+
I'll land it in staging so it can run overnight as I'm not going to be doing a reconfig tonight
Comment on attachment 555010 [details] [diff] [review]
change workdir for reboot.py call step

committed changeset 1737:bb72e026fdd9

added to tegra staging to allow it to run before tomorrow's reconfig
Attachment #555010 - Flags: checked-in+
Flags: needs-reconfig?
This got deployed to our masters.
Flags: needs-reconfig? → needs-reconfig+
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.