@orsenthil: Status check is done, and it's a success ✅ .

@orsenthil: Status check is done, and it's a success ✅ .

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

Hi! The buildbotx86 Gentoo Installed with X 3.7 has failed when building commitf4dac7e.

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/430/builds/4) and take a look at the build logs.
4. Check if the failure is related to this commit (f4dac7e) 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/430/builds/4

Failed tests:

• test_socket

Failed subtests:

• testSendFrame - test.test_socket.CANTest

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

== Tests result: FAILURE then FAILURE ==

403 tests OK.

1 test failed:
test_socket

12 tests skipped:
test_asdl_parser test_clinic test_devpoll test_gdb test_ioctl
test_kqueue test_msilib test_startfile test_winconsoleio
test_winreg test_winsound test_zipfile64

1 re-run test:
test_socket

Total duration: 26 min 12 sec

Traceback (most recent call last):  File"/buildbot/buildarea/cpython/3.7.ware-gentoo-x86.installed/build/target/lib/python3.7/test/test_socket.py", line1866, intestSendFrameself.assertEqual(addr[0],self.interface)AssertionError:'v' != 'vcan0'- v+ vcan0

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

Hi! The buildbotx86 Gentoo Non-Debug with X 3.7 has failed when building commitf4dac7e.

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/351/builds/4) and take a look at the build logs.
4. Check if the failure is related to this commit (f4dac7e) 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/351/builds/4

Failed tests:

• test_socket

Failed subtests:

• testSendFrame - test.test_socket.CANTest

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

== Tests result: FAILURE then FAILURE ==

406 tests OK.

10 slowest tests:

• test_tokenize: 3 min 57 sec
• test_concurrent_futures: 3 min 41 sec
• test_multiprocessing_spawn: 3 min 19 sec
• test_lib2to3: 3 min 18 sec
• test_tools: 2 min 31 sec
• test_multiprocessing_forkserver: 1 min 57 sec
• test_asyncio: 1 min 31 sec
• test_multiprocessing_fork: 1 min 26 sec
• test_io: 1 min 18 sec
• test_gdb: 1 min 12 sec

1 test failed:
test_socket

9 tests skipped:
test_devpoll test_ioctl test_kqueue test_msilib test_startfile
test_winconsoleio test_winreg test_winsound test_zipfile64

1 re-run test:
test_socket

Total duration: 28 min 33 sec

Traceback (most recent call last):  File"/buildbot/buildarea/cpython/3.7.ware-gentoo-x86.nondebug/build/Lib/test/test_socket.py", line1866, intestSendFrameself.assertEqual(addr[0],self.interface)AssertionError:'v' != 'vcan0'- v+ vcan0