How to debug side effects? Is there a log which tests run with the same TEST_TOKEN #931
Answered
by
Slamdunk
alexander-schranz
asked this question in
Q&A
Replies: 1 comment 3 replies
-
code@fd5b7382a832:/paratest/test/fixtures/common_results$ ../../../bin/paratest --verbose --processes=2 .
ParaTest 7.x-dev@be947b2 upon PHPUnit 12.0.3 by Sebastian Bergmann and contributors.
Processes: 2
Runtime: PHP 8.4.4
Starting process 1: '/usr/local/bin/php' '/paratest/bin/phpunit-wrapper.php' '--status-file' '/tmp/worker_01_stdout_67b5e0786f67b_status' '--progress-file' '/tmp/worker_01_stdout_67b5e0786f67b_progress' '--unexpected-output-file' '/tmp/worker_01_stdout_67b5e0786f67b_unexpected_output' '--test-result-file' '/tmp/worker_01_stdout_67b5e0786f67b_test_result' '--result-cache-file' '/tmp/worker_01_stdout_67b5e0786f67b_result_cache' '--phpunit-argv' 'a:5:{i:0;s:62:"/paratest/vendor/phpunit/phpunit/phpunit";i:1;s:21:"--do-not-cache-result";i:2;s:12:"--no-logging";i:3;s:13:"--no-coverage";i:4;s:11:"--no-output";}'
Starting process 2: '/usr/local/bin/php' '/paratest/bin/phpunit-wrapper.php' '--status-file' '/tmp/worker_02_stdout_67b5e0786fe6d_status' '--progress-file' '/tmp/worker_02_stdout_67b5e0786fe6d_progress' '--unexpected-output-file' '/tmp/worker_02_stdout_67b5e0786fe6d_unexpected_output' '--test-result-file' '/tmp/worker_02_stdout_67b5e0786fe6d_test_result' '--result-cache-file' '/tmp/worker_02_stdout_67b5e0786fe6d_result_cache' '--phpunit-argv' 'a:5:{i:0;s:62:"/paratest/vendor/phpunit/phpunit/phpunit";i:1;s:21:"--do-not-cache-result";i:2;s:12:"--no-logging";i:3;s:13:"--no-coverage";i:4;s:11:"--no-output";}'
Process 1 executing: ErrorTest.php
Process 2 executing: FailureTest.php
EProcess 1 executing: IncompleteTest.php
FProcess 2 executing: RiskyTest.php
IProcess 1 executing: SkippedTest.php
RProcess 2 executing: SuccessTest.php
SProcess 1 executing: WarningTest.php
.W 7 / 7 (100%)
Time: 00:00.246, Memory: 8.00 MB
There was 1 error: The |
Beta Was this translation helpful? Give feedback.
3 replies
Answer selected by
alexander-schranz
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to debug why some tests are flacky but only in case of using paratest.
So what I'm searching on to find out which tests did run with the same
TEST_TOKEN
as the one which did fail. Is there some log to active all previous run with the same token?In the
-verbose --debug
I didn't find infos about TEST_TOKEN or which process did use the same token.Beta Was this translation helpful? Give feedback.
All reactions