Ah, you have been bit by a common problem in our test harness. If you
run `RUST_BACKTRACE=1 ./mach test-wpt ...` (ie. the same command as
before, but with RUST_BACKTRACE=1 preceding it) then you should get a
stack trace for the first panic that occurs - right now the output only
shows one for the second panic, which is only incidental.
On 2015-10-25 1:32 PM, Jitendra Jain wrote:
Hi Josh,
Yes, I am getting a stack trace as you mentioned. However analyzing the
stacktrace doesn't show any call to overrideMimeType() which resulted in
the crash. I have attached the stack trace with this email for your
reference. I am getting a similar stack trace for the other crashing test
too (overridemimetype-unsent-state-force-shiftjis.htm).
You can view the code changes at
https://github.com/jitendra29/servo/commit/44ad6b8a666d15e8458b14f78936789de823ed10
We are now working on incorporating the suggested code changes from the
review on the recent pull request.
On Sun, Oct 25, 2015 at 9:03 AM, Josh Matthews <[email protected]>
wrote:
It is generally expected that new changes should not introduce new crashes
in the testsuite. If you run `./mach test-wpt
/XMLHttpRequest/overridemimetype-open-state-force-utf-8.htm`, does the
output contain messages like
'[something] panicked at' followed by a stack trace (like
http://stackoverflow.com/questions/3988788/what-is-a-stack-trace-and-how-can-i-use-it-to-debug-my-application-errors,
but for Rust code)?
Cheers,
Josh
On 2015-10-24 5:03 PM, Jitendra Jain wrote:
Hello,
We are working on M1504: Implement support for missing XMLHttpRequest API
<
https://github.com/servo/servo/wiki/Implement-support-for-missing-XMLHttpRequest-APIs
We have finished implementing the overrideMimeType() method as mentioned
in
the initial steps of the project specification given above. We have also
adjusted the expectations for the existing tests that now pass. However,
while running the test suite for XMLHttpRequest we are getting some of the
tests to timeout and crash.
To verify if this was as a result of our implementation of the
overrideMimeType() method, we also built the initial code which we forked
from servo and ran the same tests on it. We see that most of the test
results match our test results except these additional tests which
crash/timeout after our implementation :
/XMLHttpRequest/overridemimetype-open-state-force-utf-8.htm
----------------------------------------------------------- CRASH [Parent]
/XMLHttpRequest/overridemimetype-unsent-state-force-shiftjis.htm
---------------------------------------------------------------- CRASH
[Parent] /XMLHttpRequest/overridemimetype-open-state-force-xml.htm
--------------------------------------------------------- TIMEOUT expected
FAIL XMLHttpRequest: overrideMimeType() in open state, XML MIME type with
UTF-8 charset TIMEOUT [Parent]
Is this the expected behavior since we have implemented just the initial
steps mentioned in the project specification or we are missing something ?
_______________________________________________
dev-servo mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-servo
_______________________________________________
dev-servo mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-servo
