⚠️⚠️⚠️ Buildbot failure⚠️⚠️⚠️

Hi! The buildbotx86 Gentoo Non-Debug with X 3.x has failed when building commita679c3d.

What do you need to do:

1. Don't panic.
2. Checkthe buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/58/builds/4385) and take a look at the build logs.
4. Check if the failure is related to this commit (a679c3d) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/all/#builders/58/builds/4385

Failed tests:

• test.test_asyncio.test_subprocess

Failed subtests:

• test_subprocess_consistent_callbacks - test.test_asyncio.test_subprocess.SubprocessThreadedWatcherTests.test_subprocess_consistent_callbacks

Summary of the results of the build (if available):

== Tests result: FAILURE then FAILURE ==

444 tests OK.

10 slowest tests:

• test_concurrent_futures: 2 min 7 sec
• test_multiprocessing_spawn: 1 min 22 sec
• test_multiprocessing_forkserver: 1 min 11 sec
• test_signal: 1 min 9 sec
• test_multiprocessing_fork: 1 min 3 sec
• test_io: 33.6 sec
• test_socket: 31.1 sec
• test_imaplib: 30.6 sec
• test_xmlrpc: 27.3 sec
• test_subprocess: 26.3 sec

1 test failed:
test.test_asyncio.test_subprocess

16 tests skipped:
test.test_asyncio.test_windows_events
test.test_asyncio.test_windows_utils test_devpoll test_gdb
test_ioctl test_kqueue test_launcher test_msilib
test_peg_generator test_perf_profiler test_startfile
test_winconsoleio test_winreg test_winsound test_wmi
test_zipfile64

1 re-run test:
test.test_asyncio.test_subprocess

Total duration: 9 min 39 sec

Traceback (most recent call last):  File"/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.nondebug/build/Lib/test/test_asyncio/test_subprocess.py", line788, intest_subprocess_consistent_callbacksself.loop.run_until_complete(main())  File"/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.nondebug/build/Lib/asyncio/base_events.py", line664, inrun_until_completereturn future.result()^^^^^^^^^^^^^^^  File"/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.nondebug/build/Lib/test/test_asyncio/test_subprocess.py", line780, inmainself.assertEqual(events, [AssertionError:Lists differ: ['process_exited', ('pipe_data_received', 1, b'stdout')] != [('pipe_data_received', 1, b'stdout'), ('p[95 chars]ted']Traceback (most recent call last):  File"/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.nondebug/build/Lib/test/test_asyncio/test_subprocess.py", line788, intest_subprocess_consistent_callbacksself.loop.run_until_complete(main())  File"/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.nondebug/build/Lib/asyncio/base_events.py", line664, inrun_until_completereturn future.result()^^^^^^^^^^^^^^^  File"/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.nondebug/build/Lib/test/test_asyncio/test_subprocess.py", line780, inmainself.assertEqual(events, [AssertionError:Lists differ: [('pi[69 chars]), 'process_exited', 'pipe_connection_lost', '[17 chars]ost'] != [('pi[69 chars]), 'pipe_connection_lost', 'pipe_connection_lo[17 chars]ted']

⚠️⚠️⚠️ Buildbot failure⚠️⚠️⚠️

Hi! The buildbotARM Raspbian 3.x has failed when building commita679c3d.

What do you need to do:

1. Don't panic.
2. Checkthe buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/424/builds/3820) and take a look at the build logs.
4. Check if the failure is related to this commit (a679c3d) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/all/#builders/424/builds/3820

Failed tests:

• test_sqlite3

Failed subtests:

• test_interact_on_disk_file - test.test_sqlite3.test_cli.InteractiveSession.test_interact_on_disk_file

Summary of the results of the build (if available):

== Tests result: FAILURE then ENV CHANGED ==

438 tests OK.

10 slowest tests:

• test_venv: 5 min 32 sec
• test_multiprocessing_spawn: 5 min 12 sec
• test_largefile: 4 min 29 sec
• test_math: 4 min 26 sec
• test_source_encoding: 4 min 19 sec
• test_concurrent_futures: 3 min 22 sec
• test_lib2to3: 2 min 37 sec
• test_cppext: 2 min 31 sec
• test_tokenize: 2 min 27 sec
• test_multiprocessing_forkserver: 2 min 10 sec

1 test altered the execution environment:
test_multiprocessing_spawn

22 tests skipped:
test.test_asyncio.test_windows_events
test.test_asyncio.test_windows_utils test_devpoll test_idle
test_ioctl test_kqueue test_launcher test_msilib
test_peg_generator test_perf_profiler test_startfile test_tcl
test_tix test_tkinter test_ttk test_ttk_textonly test_turtle
test_winconsoleio test_winreg test_winsound test_wmi
test_zipfile64

1 re-run test:
test_sqlite3

Total duration: 30 min 54 sec

Traceback (most recent call last):  File"/var/lib/buildbot/workers/3.x.gps-raspbian.nondebug/build/Lib/test/test_sqlite3/test_cli.py", line142, intest_interact_on_disk_file    out, err= proc.communicate(input="create table t(t);",^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^  File"/var/lib/buildbot/workers/3.x.gps-raspbian.nondebug/build/Lib/subprocess.py", line1207, incommunicate    stdout, stderr=self._communicate(input, endtime, timeout)^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^  File"/var/lib/buildbot/workers/3.x.gps-raspbian.nondebug/build/Lib/subprocess.py", line2076, in_communicateself._check_timeout(endtime, orig_timeout, stdout, stderr)  File"/var/lib/buildbot/workers/3.x.gps-raspbian.nondebug/build/Lib/subprocess.py", line1251, in_check_timeoutraise TimeoutExpired(subprocess.TimeoutExpired:Command '['/var/lib/buildbot/workers/3.x.gps-raspbian.nondebug/build/python', '-Xutf8', '-m', 'sqlite3', '@test_14047_tmpæ']' timed out after 5.25 seconds

Hi! The buildbotx86 Gentoo Non-Debug with X 3.x has failed when building commita679c3d.

A re-run passed. The worker host was doing updates at the time of the initial failure.