GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — test_multiprocessing_fork: test_nested_startmethod() fails randomly. · Issue #109706 · python/cpython Closed Labels testsTests in the Lib/test dirTests in the Lib/test dir Descriptiontest_nested_startmethod() fails randomly. Since there is no synchronization, putting items in the queue is not really ordered. I suggest to either accept [1, 2] and [2, 1] in the test, or add some kind of synchronization to ensure that events happen in the expected order. Here I don't think that order matters. The test was added by PR #108568 of issue gh-108520. build: https://buildbot.python.org/all/#/builders/503/builds/3941 The failure can be reproduced by stressing the test: Linked PRsActivity
MetadataMetadataAssigneesLabelstestsTests in the Lib/test dirTests in the Lib/test dir ProjectsMilestoneRelationshipsDevelopmentIssue actions |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |