o ªZhã@s6ddlmZddlmZddlmZGdd„dƒZdS)é)ÚProducer)Úparse_spec_config)Úreport_collection_diffc@speZdZdZddd„Zedd„ƒZedd„ƒZed d „ƒZd d „Z d d„Z ddd„Z dd„Z dd„Z dd„ZdS)ÚEachSchedulinga"Implement scheduling of test items on all nodes If a node gets added after the test run is started then it is assumed to replace a node which got removed before it finished its collection. In this case it will only be used if a node with the same spec got removed earlier. Any nodes added after the run is started will only get items assigned if a node with a matching spec was removed before it finished all its pending items. The new node will then be assigned the remaining items from the removed node. NcCsR||_tt|ƒƒ|_i|_i|_g|_i|_|dur tdƒ|_ n|j |_ d|_ dS)NÚ eachschedF) ÚconfigÚlenrÚnumnodesÚnode2collectionÚ node2pendingÚ_startedÚ_removed2pendingrÚlogrÚcollection_is_completed)Úselfrr©rúK/var/www/html/lang_env/lib/python3.10/site-packages/xdist/scheduler/each.pyÚ__init__s  zEachScheduling.__init__cCst|j ¡ƒS)z%A list of all nodes in the scheduler.)Úlistr Úkeys)rrrrÚnodes!szEachScheduling.nodescCs:|jsdS|jr dS|j ¡D] }t|ƒdkrdSqdS)NFéT)rr r Úvaluesr©rÚpendingrrrÚtests_finished&s ÿzEachScheduling.tests_finishedcCs|j ¡D]}|r dSqdS)zÜReturn True if there are pending test items This indicates that collection has finished and nodes are still processing test items, so this can be thought of as "the scheduler is active". TF)r rrrrrÚ has_pending1s ÿzEachScheduling.has_pendingcCs||jvsJ‚g|j|<dS©N)r )rÚnoderrrÚadd_node>szEachScheduling.add_nodecCsÈ||jvsJ‚|js%t|ƒ|j|<g|j|<t|jƒ|jkr#d|_dSdS|jr`|jD]6}|jj|jjkr_|j|}||krQt |||jj |jj ƒ}|  |¡dS|j  |¡}||j|<dSq+dSdS)aòAdd the collected test items from a node Collection is complete once all nodes have submitted their collection. In this case its pending list is set to an empty list. When the collection is already completed this submission is from a node which was restarted to replace a dead node. In this case we already assign the pending items here. In either case ``.schedule()`` will instruct the node to start running the required tests. TN) r rrr rr r ZgatewayÚspecrÚidrÚpop)rrÚ collectionZdeadnodeZdead_collectionÚmsgrrrrÚadd_node_collectionBs4   ÿ  ü   óþz"EachScheduling.add_node_collectionrcCs|j| |¡dSr)r Úremove)rrZ item_indexÚdurationrrrÚmark_test_completedsz!EachScheduling.mark_test_completecCs0|j d|j |¡¡|jD]}| |¡qdS©Nr)rÚinsertr#Úindexr Zcheck_schedule)rÚitemrrrrÚmark_test_pendinggs þ  ÿz EachScheduling.mark_test_pendingcCs:|j |¡}|s dS|j|| d¡}|r||j|<|Sr))r r"r r )rrrZ crashitemrrrÚ remove_nodeos  zEachScheduling.remove_nodecCst|jsJ‚|j ¡D]-\}}||jvrq |s,tt|j|ƒƒ|dd…<| ¡| ¡n|  |¡|j  |¡q dS)a1Schedule the test items on the nodes If the node's pending list is empty it is a new node which needs to run all the tests. If the pending list is already populated (by ``.add_node_collection()``) then it replaces a dead node and we only need to run those tests. N) rr Úitemsr Úrangerr Zsend_runtest_allÚshutdownZsend_runtest_someÚappend)rrrrrrÚscheduleys    ÷zEachScheduling.scheduler)r)Ú__name__Ú __module__Ú __qualname__Ú__doc__rÚpropertyrrrrr%r(r-r.r3rrrrrs      " rN)Z xdist.remoterZxdist.workermanagerZ xdist.reportrrrrrrÚs