shunping opened a new pull request, #38456:
URL: https://github.com/apache/beam/pull/38456

   Got another flaky test below 
(https://github.com/apache/beam/actions/runs/25705764624/job/75475412939)
   
   ```
   =================================== FAILURES 
===================================
   _ 
MultiProcessSharedSpawnProcessTest.test_unsafe_hard_delete_autoproxywrapper __
   [gw1] linux -- Python 3.12.13 
/runner/_work/beam/beam/sdks/python/test-suites/tox/py312/build/srcs/sdks/python/target/.tox-py312/py312/bin/python
   
   self = 
<apache_beam.utils.multi_process_shared_test.MultiProcessSharedSpawnProcessTest 
testMethod=test_unsafe_hard_delete_autoproxywrapper>
   
       def test_unsafe_hard_delete_autoproxywrapper(self):
         shared1 = multi_process_shared.MultiProcessShared(
             Counter, tag='to_delete', always_proxy=True, spawn_process=True)
         shared2 = multi_process_shared.MultiProcessShared(
             Counter, tag='to_delete', always_proxy=True, spawn_process=True)
         counter3 = multi_process_shared.MultiProcessShared(
             Counter, tag='to_keep', always_proxy=True,
             spawn_process=True).acquire()
       
         counter1 = shared1.acquire()
         counter2 = shared2.acquire()
         self.assertEqual(counter1.increment(), 1)
   >     self.assertEqual(counter2.increment(), 2)
   E     AssertionError: 1 != 2
   
   apache_beam/utils/multi_process_shared_test.py:333: AssertionError
   ----------------------------- Captured stderr call 
-----------------------------
   INFO:root:Process 273400: Proxy serving to_keep at ('127.0.0.1', 44037)
   INFO:root:Process 273459: Proxy serving to_delete at ('127.0.0.1', 33487)
   INFO:root:Process 273507: Proxy serving to_delete at ('127.0.0.1', 44533)
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to