| Server IP : 192.158.238.246 / Your IP : 3.135.202.40 Web Server : LiteSpeed System : Linux uniform.iwebfusion.net 4.18.0-553.27.1.lve.1.el8.x86_64 #1 SMP Wed Nov 20 15:58:00 UTC 2024 x86_64 User : jenniferflocom ( 1321) PHP Version : 8.1.32 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : OFF | Pkexec : OFF Directory : /opt/alt/python37/lib/python3.7/site-packages/nose/plugins/__pycache__/ |
Upload File : |
B
0�Se։ � @ s� d Z ddlZddlZddlZddlZddlZddlZddlZddlZddl Z
ddl m Z ddl
m
Z
ddl
mZ ddlmZ ddlmZ ddlmZ dd lmZ dd
lmZ ydd lmZ W n ek
r� dd lmZ Y nX dd l m Z dd
l m Z yddl m!Z! W n ek
�r$ ddl Z Y nX dZ"e�#e$�Z%d a& a' a( a) a*a+G dd� de,�Z-dd� Z.G dd� d�Z/G dd� de�Z0dd� Z1G dd� de �Z2dd � Z3d d � Z4G d d � d e�Z5dS )!a�
Overview
========
The multiprocess plugin enables you to distribute your test run among a set of
worker processes that run tests in parallel. This can speed up CPU-bound test
runs (as long as the number of work processeses is around the number of
processors or cores available), but is mainly useful for IO-bound tests that
spend most of their time waiting for data to arrive from someplace else.
.. note ::
See :doc:`../doc_tests/test_multiprocess/multiprocess` for
additional documentation and examples. Use of this plugin on python
2.5 or earlier requires the multiprocessing_ module, also available
from PyPI.
.. _multiprocessing : http://code.google.com/p/python-multiprocessing/
How tests are distributed
=========================
The ideal case would be to dispatch each test to a worker process
separately. This ideal is not attainable in all cases, however, because many
test suites depend on context (class, module or package) fixtures.
The plugin can't know (unless you tell it -- see below!) if a context fixture
can be called many times concurrently (is re-entrant), or if it can be shared
among tests running in different processes. Therefore, if a context has
fixtures, the default behavior is to dispatch the entire suite to a worker as
a unit.
Controlling distribution
^^^^^^^^^^^^^^^^^^^^^^^^
There are two context-level variables that you can use to control this default
behavior.
If a context's fixtures are re-entrant, set ``_multiprocess_can_split_ = True``
in the context, and the plugin will dispatch tests in suites bound to that
context as if the context had no fixtures. This means that the fixtures will
execute concurrently and multiple times, typically once per test.
If a context's fixtures can be shared by tests running in different processes
-- such as a package-level fixture that starts an external http server or
initializes a shared database -- then set ``_multiprocess_shared_ = True`` in
the context. These fixtures will then execute in the primary nose process, and
tests in those contexts will be individually dispatched to run in parallel.
How results are collected and reported
======================================
As each test or suite executes in a worker process, results (failures, errors,
and specially handled exceptions like SkipTest) are collected in that
process. When the worker process finishes, it returns results to the main
nose process. There, any progress output is printed (dots!), and the
results from the test run are combined into a consolidated result
set. When results have been received for all dispatched tests, or all
workers have died, the result summary is output as normal.
Beware!
=======
Not all test suites will benefit from, or even operate correctly using, this
plugin. For example, CPU-bound tests will run more slowly if you don't have
multiple processors. There are also some differences in plugin
interactions and behaviors due to the way in which tests are dispatched and
loaded. In general, test loading under this plugin operates as if it were
always in directed mode instead of discovered mode. For instance, doctests
in test modules will always be found when using this plugin with the doctest
plugin.
But the biggest issue you will face is probably concurrency. Unless you
have kept your tests as religiously pure unit tests, with no side-effects, no
ordering issues, and no external dependencies, chances are you will experience
odd, intermittent and unexplainable failures and errors when using this
plugin. This doesn't necessarily mean the plugin is broken; it may mean that
your test suite is not safe for concurrency.
New Features in 1.1.0
=====================
* functions generated by test generators are now added to the worker queue
making them multi-threaded.
* fixed timeout functionality, now functions will be terminated with a
TimedOutException exception when they exceed their execution time. The
worker processes are not terminated.
* added ``--process-restartworker`` option to restart workers once they are
done, this helps control memory usage. Sometimes memory leaks can accumulate
making long runs very difficult.
* added global _instantiate_plugins to configure which plugins are started
on the worker processes.
� N)�TextTestRunner)�failure)�loader)�Plugin)�bytes_)�TextTestResult)� ContextSuite)� test_address)�_WritelnDecorator)�Empty)�warn)�StringIOc @ s e Zd Zddd�Zdd� ZdS )�TimedOutException� Timed Outc C s
|| _ d S )N)�value)�selfr � r �J/opt/alt/python37/lib/python3.7/site-packages/nose/plugins/multiprocess.py�__init__� s zTimedOutException.__init__c C s
t | j�S )N)�reprr )r r r r �__str__� s zTimedOutException.__str__N)r )�__name__�
__module__� __qualname__r r r r r r r � s
r c C s~ yZddl m} ma t�tjtj�}| � }t�tj|� |j|j|j|j |j
f\aaaa a
W n t k
rx t dt
� Y nX d S )Nr )�Manager�ProcesszKmultiprocessing module is not available, multiprocess plugin cannot be used)�multiprocessingr r �signal�SIGINT�SIG_IGN�Queue�Pool�Event�Value�Array� ImportErrorr �RuntimeWarning)r �old�mr r r �
_import_mp� s &r) c @ s, e Zd Zdd� Zdd� Zdd� Zdd� Zd S )
�TestLetc C s< y|� � | _W n tk
r" Y nX |�� | _t|�| _d S )N)�id�_id�AttributeError�shortDescription�_short_description�str�_str)r �caser r r r � s
zTestLet.__init__c C s | j S )N)r, )r r r r r+ � s z
TestLet.idc C s | j S )N)r/ )r r r r r. � s zTestLet.shortDescriptionc C s | j S )N)r1 )r r r r r � s zTestLet.__str__N)r r r r r+ r. r r r r r r* � s r* c @ s8 e Zd ZdZdZi Zdd� Zdd� Zdd� Zd d
� Z d S ) � MultiProcesszF
Run tests in multiple processes. Requires processing module.
i� c C s\ |j dd|�dd�dddd� |j d d|�d
d �d d
dd� |j dd|�dd�ddd� dS )z0
Register command-line options.
z --processes�storeZNOSE_PROCESSESr �multiprocess_workersZNUMaN Spread test run among this many processes. Set a number equal to the number of processors or cores in your machine for best results. Pass a negative number to have the number of processes automatically set to the number of cores. Passing 0 means to disable parallel testing. Default is 0 unless NOSE_PROCESSES is set. [NOSE_PROCESSES])�action�default�dest�metavar�helpz--process-timeoutZNOSE_PROCESS_TIMEOUT�
�multiprocess_timeoutZSECONDSzfSet timeout for return of results from each test runner process. Default is 10. [NOSE_PROCESS_TIMEOUT]z--process-restartworker�
store_trueZNOSE_PROCESS_RESTARTWORKERF�multiprocess_restartworkerz�If set, will restart each worker process once their tests are done, this helps control memory leaks from killing the system. [NOSE_PROCESS_RESTARTWORKER])r6 r7 r8 r: N)�
add_option�get)r �parser�envr r r �options� s
zMultiProcess.optionsc C s y| j �d� W n tk
r$ Y nX t|d�s:d| _dS |jrDdS || _yt|j�}W n t t
fk
rt d}Y nX |�rt � t dkr�d| _dS |dk r�yddl
}|�� }W n tk
r� d| _dS X d| _|| j_t|j�}|| j_t|j�}|| j_d| j d< dS )z#
Configure plugin.
Zactiver5 FNr T)�status�pop�KeyError�hasattr�enabled�worker�config�intr5 � TypeError�
ValueErrorr) r r � cpu_count�NotImplementedError�floatr< r> )r rC rJ �workersr �t�rr r r � configure� sB
zMultiProcess.configurec C s |j | _dS )zbRemember loader class so MultiProcessTestRunner can instantiate
the right loader.
N)� __class__� loaderClass)r r r r r �prepareTestLoader s z MultiProcess.prepareTestLoaderc C s t |j| jj| j| jd�S )z9Replace test runner with MultiProcessTestRunner.
)�stream� verbosityrJ rV )�MultiProcessTestRunnerrX rJ rY rV )r �runnerr r r �prepareTestRunner
s z MultiProcess.prepareTestRunnerN)
r r r �__doc__�scorerD rC rT rW r\ r r r r r3 � s )r3 c C s
t � �d S )N)r )�sig�framer r r �
signalhandler s ra c s� e Zd ZdZ� fdd�Zdd� Zdd� Zdd � Zd
d � Ze e�Zd d
� Z
e e
�Z
dd� Z dd� Z e e �Z dd� Z
dd� Z� ZS )rZ g @c s& |� dtj�| _tt| �jf |� d S )NrV )rE r �defaultTestLoaderrV �superrZ r )r �kw)rU r r r s z MultiProcessTestRunner.__init__c
C s� �x|| � |�D �]l}t�d|t|�� t|tjj�rVt|jt j
�rVt�d� ||� qt|t �r�|j t j
kr�t�d� ||� qqt|t ��rZ| �
|��rZt�d|� y |�� W nD ttfk
r� � Y n� t�dt�� � |�|t�� � Y nbX |�|� |j�rF|jj �|g �}x*|d d� D ]}t|dd��r(d|_�q(W | �|||||� q| �|||�} t�d t|�| |� qW d S )
NzNext batch %s (%s)zCase is a Failurez%s has shared fixturesz%s setup failed� �_multiprocess_shared_FTzQueued test %s (%s) to %s) � nextBatch�log�debug�type�
isinstance�noser2 �Test�testr �Failurer �context�sharedFixtures�setUp�KeyboardInterrupt�
SystemExit�sys�exc_info�addError�append�factoryr@ �getattr�_multiprocess_can_split_�collect�addtask�len)
r rn � testQueue�tasks� to_teardown�resultr2 Z ancestorsZan� test_addrr r r r| s<
z MultiProcessTestRunner.collectc C s� t dtd��}t dt�� �}t� }tt|||||||| j|jt� | j
�f
d�} || _ || _ || _
t�tjt�}
| �� t�tj|
� | S )N�c� �d)�target�args)r# r �timer" r r[ rV rU �pickle�dumpsrJ � currentaddr� currentstart�keyboardCaughtr �SIGILLra �start) r �iworkerr � resultQueue�
shouldStopr� r� r� r� �pr' r r r � startProcessE s( z#MultiProcessTestRunner.startProcessc C s2 t �d| |t�� � | jj�|�}|dk r.|}| jj�| j�}|dk rL|| _t � }t � }g }g }g }g } t
� }
| � � } t � � } | �
|||| | � t �d| jj� x@t| jj�D ]0}
| �|
|||
| �}|�|� t �d|
d � q�W t|�}| jj}d}�y��xb|�r^t �dt|�||� �yL|j|d�\}}}}t �d||t|�� yNy|�|� W n$ tk
�rx t �d ||� Y nX |t|�7 }|�|� W n: tk
�r� t �d
|� t �d tt|�d �� Y nX |�||g� | � | |� | jj �r| � � �s|
� � P | jj �rbt �d
|� || j!dd� |
�"� �sb|�#� �sbt �d|� | �||||
| �||< W �n� t$k
�r� t �dt|�|�#� t|�� d}�x:t%|�D �],\}}|�&� �r�t'|j(j)d�}t � � |j*j) }t|�d k�r|| jjd k�rt �d|� nd}t|�d k�r�|| jjd k�r�t �d||� t'd�|j(_)|j+�,� t � � }xz|j+�"� �s�|�&� �r�t � � | | j-k�r�t �.d|� |�/� | �||||
| � ||< }P t�0|j1t2j3� t �4d� �qVW �q�W |�s�|�#� �r�t �d� P Y nX | jj}xZ|D ]R}|�&� �rt|j(j)�d k�rt � � |j*j) }|| jjk�rt5|| jj| �}�qW q�W t �dt|�t|�� W nF t6t7fk
�r� } z"t �8d� |}| �9|t:�;� � W dd}~X Y nX �yx^| D ]V} t �d| � y | �<� W n6 t6t7fk
�r � Y n | �9| t:�;� � Y nX �q�W t � � } | �=� | �>| | � | jj�?| � |dk�r�t �d � x&|D ] }|�&� �rh|j@d dd � �qhW xJt%|�D ]>\}} | �&� �r�t �d
|� | �!� | �&� �r�t �d |� �q�W W nT t6t7fk
�r, t �8d � x |D ]} | �&� �r�| �/� �q�W |�r&|�n� Y nX | S )!a
Execute the test (which may be a test suite). If the test is a suite,
distribute it out among as many processes as have been configured, at
as fine a level as is possible given the context fixtures defined in
the suite or any sub-suites.
z%s.run(%s) (%s)NzStarting %s workerszStarted worker process %s� z5Waiting for results (%s/%s tasks), next timeout=%.3fs)�timeoutz1Results received for worker %d, %s, new tasks: %dz)worker %s failed to remove from tasks: %sz Got result for unknown task? %sz current: %sr zjoining worker %sz!starting new process on worker %sz8Timed out with %s tasks pending (empty testQueue=%r): %sF�asciig�������?zLworker %d has finished its work item, but is not exiting? do we wait for it?Tztimed out worker %s: %sr� zterminating worker %szAll workers deadz Completed %s tasks (%s remain)z4parent received ctrl-c when waiting for test resultsz#Tearing down shared fixtures for %szTell all workers to stop�STOP)�blockzfailed to join worker %sz=parent received ctrl-c when shutting down: stop all processes)Arh ri �os�getpidrJ �pluginsZ prepareTestZsetOutputStreamrX r r" � _makeResultr� r| r5 �ranger� rx r~ r< r@ �removerM r �extendrF r0 �list� consolidateZ stopOnError�
wasSuccessful�setr> �join�is_set�emptyr � enumerate�is_aliver r� r r� r� �clear� waitkilltime�error� terminate�kill�pidr r� �sleep�minrs rt �inforw ru rv �tearDown� printErrorsZ printSummary�finalize�put) r rn �wrapper�wrappedr r� r� Z completedrQ r� r� r� r� �ir� Z total_tasksZ nexttimeoutZ thrownErrorr� �addrZ
newtask_addrs� batch_resultZ any_alive�wZ worker_addrZtimeprocessingZ
startkilltime�er2 �stoprI r r r �run[ s
"
zMultiProcessTestRunner.runc C st d }t |tjj�r.t|jd�r.d |j_|jj}t� |�}| j
||fdd� |d k r^|t |�7 }|d k rp|� |� |S )N�argF)r� )
rk rl r2 rm rG rn Z
descriptorr� rZ �addressr� r0 rx )r r� r2 r� r� r r r r} s
z MultiProcessTestRunner.addtaskc C s� t | d�r| �� \}}}n(t | d�r6t| j�\}}}n td| ��g }|d krp|d krdtd| ��q�|�|� n(tj�|�\}}|� d�r�|}|�|� |d k r�|�|� d�
t t |��S )Nr� rp z Unable to convert %s to addresszUnaddressable case %sr �:)
rG r� r rp � Exceptionrx r� �path�split�
startswithr� �mapr0 )r2 �file�mod�call�parts�dirname�basenamer r r r� ! s"
z MultiProcessTestRunner.addressc c s� t |d�r t|jdd�s d S t|t�r2|�| j�sJt|dd�rJt|tj�s�t|t�r�t |�}t
|�dkr�t|d dd �|jkr�|d }|V n(x&|D ] }x| � |�D ]
}|V q�W q�W d S )Nrp Z_multiprocess_TZ can_splitr� r ) rG rz rp rk r Z hasFixtures�
checkCanSplit�unittest� TestSuiter� r~ rg )r rn Z containedr2 �batchr r r rg : s"
z MultiProcessTestRunner.nextBatchc C s |sdS t | dd�rdS dS )a8
Callback that we use to check whether the fixtures found in a
context or ancestor are ones we care about.
Contexts can tell us that their fixtures are reentrant by setting
_multiprocess_can_split_. So if we see that, we return False to
disregard those fixtures.
Fr{ T)rz )rp Zfixtr r r r� Z s
z$MultiProcessTestRunner.checkCanSplitc C s t |dd �}|sdS t |dd�S )Nrp Frf )rz )r r2 rp r r r rq j s z%MultiProcessTestRunner.sharedFixturesc C s� t �d|� y|\}}}}}W n2 tk
rP t �d|� tjt�� � |� d S X | j�|� | j |7 _ |j
� |� |j � |� xRt
|�� �D ]B\}\} }
} ||jkr�g |
| f|j|< |j| \} }
}
| � | � q�W t �d||j � d S )Nzbatch result is %sz result in unexpected format %szRan %s tests (total: %s))rh ri rM r ro ru rv rX �write�testsRun�failuresr� �errorsr� �items� errorClasses)r r� r� �outputr� r� r� r� �key�storage�label�isfailZ mystorageZ_junkr r r r� p s"
z"MultiProcessTestRunner.consolidate)r r r r� r r| r� r� r} � staticmethodr� rg r� rq r� �
__classcell__r r )rU r rZ s ( 7 rZ c
C sf y@yt | ||||||||| �
S tk
r< t�d| � Y nX W n tk
r` t�d| � Y nX d S )Nz&Worker %s keyboard interrupt, stoppingz%Worker %s timed out waiting for tasks)�__runnerrs rh ri r )
�ixr r� r� r� r� r� rV � resultClassrJ r r r r[ � s r[ c
s� t �� �� � �� }
td k rFx*tD ]"} | � } | �|
i � � j�| � q W � j�� j� � � j� � t
� d| t �
� � |� d�}
t|
j_� �fdd�}� �fdd�}dd� }�xt|d �D �]\}}|�� r�t
�d
| � P |� }|
�|g�}�|_g |_||_t
� d | ||� yZ|d k �r"|t|� }t|�|_t�� |_||� td �|_|�| ||j||�f� W �nP t k
�r> } z�t |t �}|�r�|� � t |j��r�|�r�d
}nd}t
�|| |� td �|_t!j"t#�$� � |� |�| ||j||�f� n6|�r�d}nd}t
� || |� |�| ||j||�f� |�s.� W d d }~X Y nx t%k
�rj td �|_t
�d| � � Y nL td �|_t
�d| � t!j"t#�$� � |� |�| ||j||�f� Y nX � j&r�P q�W t
� d| � d S )NzWorker %s executing, pid=%d)rJ c s �j � jd�S )N)r� )r@ r< r )rJ r r r r@ � s z__runner.<locals>.getc s4 t t� �} �| d� j� d�}� j�|�}|r0|S |S )Nr� )� descriptionsrY rJ )r
r
rY r� ZprepareTestResult)rX r� Z plug_result)rJ r� r r �
makeResult� s
z __runner.<locals>.makeResultc S st dd� | j D �}dd� | jD �}i }x8t| j�� �D ]&\}\}}}dd� |D �||f||< q4W | j�� | j|||fS )Nc S s g | ]\}}t |�|f�qS r )r* )�.0r� �errr r r �
<listcomp>� s z+__runner.<locals>.batch.<locals>.<listcomp>c S s g | ]\}}t |�|f�qS r )r* )r� r� r� r r r r� � s c S s g | ]\}}t |�|f�qS r )r* )r� r� r� r r r r� � s )r� r� r� r� r� rX �getvaluer� )r� r� r� r� r� r� r� r� r r r r� � s z__runner.<locals>.batchr� zWorker %d STOPPEDzWorker %s Test is %s (%s)r� z,Worker %s timed out, failing current test %sz5Worker %s keyboard interrupt, failing current test %szWorker %s test %s timed outz$Worker %s test %s keyboard interruptzWorker %s system exitz1Worker %s error running test or returning resultszWorker %s ending)'r� �loadsZ parserClass�_instantiate_pluginsZ
addOptionsr� Z addPluginrT rC �beginrh ri r� r� �NoSharedFixtureContextSuite�
suiteClass�iterr� � exception�loadTestsFromNamesr r� r� r0 r r r� r� rs rk r r� r~ r ro ru rv rt r> )r� r r� r� r� r� r� rV r� rJ Z dummy_parserZ pluginclassZpluginr r@ r� r� r� r� r� rn r� r� �msgr )rJ r� r r r� � s�
r� c s@ e Zd ZdZdZdZdZ� fdd�Z� fdd�Zdd� Z � Z
S ) r� a
Context suite that never fires shared fixtures.
When a context sets _multiprocess_shared_, fixtures in that context
are executed by the main process. Using this suite class prevents them
from executing in the runner process as well.
Nc s$ t |dd�rd S tt| ��|� d S )Nrf F)rz rc r� � setupContext)r rp )rU r r r� � s z(NoSharedFixtureContextSuite.setupContextc s$ t |dd�rd S tt| ��|� d S )Nrf F)rz rc r� �teardownContext)r rp )rU r r r� s z+NoSharedFixtureContextSuite.teardownContextc C s� t �dt| �| | j� | jr0| �|| �| }}n
|| }}y | �� W n4 tk
r\ � Y n d| _|�| | � � � dS z�x�| jD ]�}t
|t j j
�r�| jdk r�| j|j_n| j|_| j|_| j|_|jr�t �d� P y ||� W q� tk
�rn } zjt
|t�}|�rd}nd}t �||| � ttt|��t�� d f}|jj�||� |�||� |�s^� W dd}~X Y q�X q�W W dd| _y | �� W n8 tk
�r� � Y n" d | _|�| | � � � Y nX X dS )
z5Run tests in suite inside of suite fixtures.
z#suite %s (%s) run called, tests: %s�setupNZstoppingz(Timeout when running test %s in suite %sz2KeyboardInterrupt when running test %s in suite %sre TZteardown)rh ri r+ �_testsZ resultProxyrr rs Z
error_contextrw � _exc_infork rl r2 rm r� rn r r� r� r r0 ru rv rJ r� Zhas_runr� )r r� �origrn r� r� r� r� r r r r� s\
z NoSharedFixtureContextSuite.run) r r r r] r r� r� r� r� r� r� r r )rU r r� � s r� )6r] �loggingr� ru r� � tracebackr� r� r Z nose.caserl Z nose.corer r r Znose.plugins.baser Znose.pyversionr Z nose.resultr Z
nose.suiter Z nose.utilr Zunittest.runnerr
r% �queuer �warningsr �ior
r� � getLoggerr rh r r r! r" r# r$ rs r r) r* r3 ra rZ r[ r� r� r r r r �<module>^ sR
_ s a