o %ifQ@sbddlmZddlmZddlZddlmZddlmZddl m Z ddl m Z Gdd d Z dS) ) annotations)SequenceN)Producer)report_collection_diff)parse_spec_config)WorkerControllerc@seZdZdZd/d0d d Zed1d d Zed2ddZed2ddZd3ddZ d4ddZ d5d6d d!Z d7d$d%Z d8d(d)Z d9d+d,Zd:d-d.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. Nconfig pytest.ConfiglogProducer | NonereturnNonecCsR||_tt||_i|_i|_g|_i|_|dur td|_ n|j |_ d|_ dS)N eachschedF) r lenrnumnodesnode2collection node2pending_started_removed2pendingrr rcollection_is_completed)selfr r rM/var/www/html/corbot_env/lib/python3.10/site-packages/xdist/scheduler/each.py__init__s  zEachScheduling.__init__list[WorkerController]cCst|jS)z%A list of all nodes in the scheduler.)listrkeys)rrrrnodes(szEachScheduling.nodesboolcCs:|jsdS|jr dS|jD] }t|dkrdSqdS)NFT)rrrvaluesrrpendingrrrtests_finished-s zEachScheduling.tests_finishedcCs|jD]}|r dSqdS)zReturn 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)rr!r"rrr has_pending8s zEachScheduling.has_pendingnodercCs||jvsJg|j|<dSN)r)rr&rrradd_nodeEszEachScheduling.add_node collection Sequence[str]cCs||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)aAdd 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) rrrrrrrgatewayspecridr pop)rr&r)deadnodedead_collectionmsgr#rrradd_node_collectionIs4        z"EachScheduling.add_node_collectionr item_indexintdurationfloatcCs|j||dSr')rremove)rr&r3r5rrrmark_test_completemsz!EachScheduling.mark_test_completeitemstrcCtr'NotImplementedError)rr9rrrmark_test_pendingrsz EachScheduling.mark_test_pendingindices Sequence[int]cCr;r'r<)rr&r?rrrremove_pending_tests_from_nodeusz-EachScheduling.remove_pending_tests_from_node str | NonecCs:|j|}|s dS|j||d}|r||j|<|S)Nr)rr.rr)rr&r# crashitemrrr remove_node|s  zEachScheduling.remove_nodecCst|jsJ|jD]-\}}||jvrq |s,tt|j||dd<||n| ||j |q dS)a2Schedule 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) rritemsrrangerrsend_runtest_allshutdownsend_runtest_someappend)rr&r#rrrschedules    zEachScheduling.scheduler')r r r r r r)r r)r r)r&rr r)r&rr)r*r r)r)r&rr3r4r5r6r r)r9r:r r)r&rr?r@r r)r&rr rB)r r)__name__ __module__ __qualname____doc__rpropertyrr$r%r(r2r8r>rArDrKrrrrr s"     %    r) __future__rtypingrpytest xdist.remoter xdist.reportrxdist.workermanagerrrrrrrs