Closed Bug 1146632 Opened 10 years ago Closed 7 years ago

[e10s] sdk/test/assert.js causes unsafe CPOW usage warnings

Categories

(Add-on SDK Graveyard :: General, defect, P4)

defect

Tracking

(e10s+)

RESOLVED INCOMPLETE
Tracking Status
e10s + ---

People

(Reporter: Kwan, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [unsafe-cpow-usage] triaged)

Mined from test logs In addon-sdk/source/lib/sdk/test/assert.js: fail: function fail(e) { if (!e || typeof(e) !== 'object') { this._log.fail(e); return; } let message = e.message; <- Causes CPOW warning try { if ('operator' in e) { <- Causes CPOW warning message += [ " -", source(e.actual), e.operator, source(e.expected) ].join(" "); } } catch(e) {} this._log.fail(message); }, [...] /** * The equality assertion tests shallow, coercive equality with `==`. * @example * assert.equal(1, 1, "one is one"); */ equal: function equal(actual, expected, message) { if (actual == expected) { <- Causes CPOW warning this.pass(message); return true; } this.fail({ actual: actual, expected: expected, message: message, operator: "==" }); return false; },
tracking-e10s: m8+ → ---
Whiteboard: [unsafe-cpow-usage]
This module is for use in tests, so I think we can consider this test only.
tracking-e10s: --- → +
we are going to check which tests pass - and then disable all that do not to detect breakages from this point on. correcting the test suite issue across the board is a months long effort - that doesn't align with 2017 plans.
Priority: P1 → P4
Whiteboard: [unsafe-cpow-usage] → [unsafe-cpow-usage] triaged
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.