1847164 - Permanent failure line for successful py3(mb) tasks: OSError: [WinError 6] The handle is invalid - DO NOT USE FOR CLASSIFICATIOn

Status: RESOLVED FIXED

(Testing :: Mozbase, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: nerli [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=424908829&repo=mozilla-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/aP5mwXj6QFmFiWUa4Mamkg/runs/0/artifacts/public/logs/live_backing.log

---

[task 2023-08-04T05:22:04.610Z] Exception ignored in: <function Popen.__del__ at 0x0000017AB9B51E50>
[task 2023-08-04T05:22:04.610Z] Traceback (most recent call last):
[task 2023-08-04T05:22:04.610Z]   File "C:\mozilla-build\python3\lib\subprocess.py", line 1055, in __del__
[task 2023-08-04T05:22:04.610Z]     self._internal_poll(_deadstate=_maxsize)
[task 2023-08-04T05:22:04.610Z]   File "C:\mozilla-build\python3\lib\subprocess.py", line 1457, in _internal_poll
[task 2023-08-04T05:22:04.610Z]     if _WaitForSingleObject(self._handle, 0) == _WAIT_OBJECT_0:
[task 2023-08-04T05:22:04.610Z] OSError: [WinError 6] The handle is invalid
[task 2023-08-04T05:22:04.610Z] 
[task 2023-08-04T05:22:04.610Z] 
[task 2023-08-04T05:22:49.845Z] Tests Completed:  99%|#########8| 80/81 [01:08<00:05,  5.29s/Test]
[task 2023-08-04T05:22:49.856Z]                                                                   
[task 2023-08-04T05:22:49.856Z] 
[task 2023-08-04T05:22:49.856Z] Tests Completed: 100%|##########| 81/81 [01:53<00:00, 17.25s/Test]
[task 2023-08-04T05:22:49.856Z]                                                                   
[task 2023-08-04T05:22:49.856Z] Z:\task_169111255322733\build\src\testing\mozbase\mozproxy\tests\test_recording.py
[task 2023-08-04T05:22:49.856Z] ============================= test session starts =============================
[task 2023-08-04T05:22:49.856Z] platform win32 -- Python 3.9.10, pytest-7.0.1, pluggy-1.2.0 -- C:\Users\task_169111255322733\.mozbuild\srcdirs\src-7d977e83b7fa\_virtualenvs\python-test\Scripts\python.exe
[task 2023-08-04T05:22:49.856Z] rootdir: z:\task_169111255322733\build\src, configfile: config\mozunit\mozunit\pytest.ini
[task 2023-08-04T05:22:49.857Z] collecting ... collected 1 item
[task 2023-08-04T05:22:49.857Z] 
[task 2023-08-04T05:22:49.857Z] testing/mozbase/mozproxy/tests/test_recording.py::test_record_and_replay TEST-UNEXPECTED-FAIL
[task 2023-08-04T05:22:49.857Z] 
[task 2023-08-04T05:22:49.857Z] ================================== FAILURES ===================================
[task 2023-08-04T05:22:49.857Z] ___________________________ test_record_and_replay ____________________________
[task 2023-08-04T05:22:49.857Z] testing\mozbase\mozproxy\tests\test_recording.py:64: in test_record_and_replay
[task 2023-08-04T05:22:49.857Z]     playback.start()
[task 2023-08-04T05:22:49.857Z] testing\mozbase\mozproxy\mozproxy\backends\mitm\mitm.py:239: in start
[task 2023-08-04T05:22:49.857Z]     self.start_mitmproxy(self.mitmdump_path, self.browser_path)
[task 2023-08-04T05:22:49.857Z] testing\mozbase\mozproxy\mozproxy\backends\mitm\mitm.py:398: in start_mitmproxy
[task 2023-08-04T05:22:49.857Z]     sys.exit(1)  # XXX why do we need to do that? a raise is not enough?
[task 2023-08-04T05:22:49.857Z] E   SystemExit: 1

Comment 1

[Intermittent Failures Robot]

1 failures in 3276 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-central: 1

Platform and build breakdown:

• windows11-64: 1
  • opt: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=1847164&startday=2023-07-31&endday=2023-08-06&tree=all

Comment 2

[Geoff Brown [:gbrown]]

Thanks!

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1843380

Comment 4

[Geoff Brown [:gbrown]]

This is Windows only: Linux and Mac logs are okay.

Windows tests consistently pass but report this exception.

Comment 5

[Geoff Brown [:gbrown]]

Attachment: Bug 1847164 - In mozprocess tests, wait after kill to avoid warning on Windows

https://bugs.python.org/issue37380 and https://bugs.python.org/issue36067
suggest this problem may arise when a process ends but is not waited on,
on Windows only. Sure enough, adding a wait to the test kill() utility
avoids the message -- verified on try.

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/b55efc3e6465
In mozprocess tests, wait after kill to avoid warning on Windows r=hneiva

Comment 7

[Iulian Moraru]

https://hg.mozilla.org/mozilla-central/rev/b55efc3e6465