Open Bug 1763002 Opened 4 years ago Updated 4 years ago

test_versioncomparator.js fails on Windows ASan Fission

Categories

(Core :: XPCOM, task)

task

Tracking

()

People

(Reporter: mccr8, Unassigned)

References

(Blocks 1 open bug)

Details

This came up in bug 1751492.

Apparently test_comparator.js (an xpcshell test) fails with Fission. We don't run this configuration by default, so maybe it fails without Fission, too. Very bizarre. It passes on Windows opt.

Here's the failure:

(xpcshell/head.js) | test MAIN run_test pending (1)
8321499136 should be less than 0.9
Z:/task_164823805670957/build/tests/xpcshell/tests/xpcom/tests/unit/test_versioncomparator.js:run_test:42
Z:\task_164823805670957\build\tests\xpcshell\head.js:_execute_test:597
e:null:1

The only thing I can think of is that I think ASan intercepts string operations and maybe something is going wrong with that on Windows.

(The version comparator is implemented in xpcom/base/nsVersionComparator.cpp.)

Nika suggested strtol might be the issue, which led me to some googling which led to this issue about strtol not setting errno correctly in ASan on Windows. The specific case that is failing is testing the error handling of strtol. Maybe it hasn't been fixed in the last 5 years.

You need to log in before you can comment on or make changes to this bug.