Closed Bug 828858 Opened 12 years ago Closed 9 years ago

Investigate why httpd.js behaves differently when using sdcard on B2G

Categories

(Testing :: XPCShell Harness, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: dhylands, Unassigned)

Details

I noticed this when I added support for saving the update.mar file to sdcard (so running xpcshell tests in the B2G emulator under linux). In order to reproduce this, you'll need to make sure that when you run the emulator locally, that it has a valid SDCard image. By default, it doesn't seem to. STR: - Run the xpcshell tests for the updater (under the emulator on linux) - When pt12 of test_0030_general.js runs, nsIncrementalDownload::OnStartRequest gets a return status of 416 from GetResponseStatus. - Edit b2g/components/DirectoryProvider.js - Change gUseSDCard to false - rebuild - rerun xpcshell tests. - When pt12 of test_0030_general.js runs, nsIncrementalDownload::OnStartRequest gets a return status of 200 from GetResponseStatus. When the response code of 416 is returned, no onProgress occurs (so no data is received) and we wind up getting a status code of Cr.NS_ERROR_CORRUPTED_CONTENT. When the response code of 200 is returned, onProgress occurs and the 351 bytes of the file is received. This winds up getting a status code of NS_ERROR_UNEXPECTED What's bizarre, is that in both cases, the source file being served is the same, it's just the destination that changes. For bug 785124, I modified test_0030_general.js to accept both of the above status codes, but something seems fishy (hence this bug)
Looks like you are going to have at the very least workarounds for this difference in bug 785124 and this doesn't appear to be an app update bug so moving to a component where the problem might actually lie.
Component: Application Update → XPCShell Harness
Product: Toolkit → Testing
This bug should backout the workarounds introduced in bug 813770.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.