Closed Bug 1317084 Opened 8 years ago Closed 8 years ago

Intermittent SandboxBrokerTest.MultiThreadOpen | Expected: (nullfd) >= (0), actual: -5 vs 0 | test completed (time: 1504ms)

Categories

(Core :: Security: Process Sandboxing, defect, P3)

Product:
Core
Component:
Security: Process Sandboxing
Version:
43 Branch
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1243108

People

(Reporter: aryx, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure, Whiteboard: sb+) 

+++ This bug was initially created as a clone of Bug #1243108 +++

https://treeherder.mozilla.org/logviewer.html#?job_id=39114671&repo=mozilla-inbound

[task 2016-11-12T17:21:47.261470Z] 17:21:47     INFO -  TEST-START | SandboxBrokerTest.MultiThreadOpen
[task 2016-11-12T17:21:48.225321Z] 17:21:48     INFO -  Sandbox: Unexpected EOF, op 0 flags 00 path /dev/null
[task 2016-11-12T17:21:48.266273Z] 17:21:48  WARNING -  TEST-UNEXPECTED-FAIL | SandboxBrokerTest.MultiThreadOpen | Expected: (nullfd) >= (0), actual: -5 vs 0
[task 2016-11-12T17:21:48.266976Z] 17:21:48     INFO -  Loop 5869/10000 @ /home/worker/workspace/build/src/security/sandbox/linux/gtest/TestBroker.cpp:408
[task 2016-11-12T17:21:48.765891Z] 17:21:48  WARNING -  TEST-UNEXPECTED-FAIL | SandboxBrokerTest.MultiThreadOpen | test completed (time: 1504ms)
Why is this a separate bug from bug 1243108?
Flags: needinfo?(aryx.bugmail)
Sorry, hadn't updated the bug summary. Difference is zerofd vs nullfd.
Flags: needinfo?(aryx.bugmail)
Summary: Intermittent SandboxBrokerTest.MultiThreadOpen or SandboxBrokerTest.MultiThreadStat | Expected: (zerofd) >= (0), actual: -5 vs 0 | test completed (time: 1198ms) → Intermittent SandboxBrokerTest.MultiThreadOpen | Expected: (nullfd) >= (0), actual: -5 vs 0 | test completed (time: 1504ms)
Blocks: sb-test
Depends on: 1243108
Whiteboard: sb+
This is almost certainly the same underlying bug as bug 1243108.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
No longer depends on: 1243108
You need to log in before you can comment on or make changes to this bug.