Spawn for running test discovery is not following symlinks properly. #9347

JacekPliszka · 2019-12-31T19:07:28Z

Environment data

VS Code version: 1.41.1 26076a4de974ead31f97692a0d32f90d735645c0
Extension version (available under the Extensions sidebar): 2019.11.50794
OS and version: Fedora Linux 31
Python version (& distribution if applicable, e.g. Anaconda): 3.7.5
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: Python 3.7.5, pytest-4.6.7, py-1.8.0, pluggy-0.12.0
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info How to update the language server to the latest stable version #3977): "python.jediEnabled": true

Expected behaviour

tests are detected

Actual behaviour

tests are not detected, error is issues, running the adapter returns:

$ python /home/jp/.vscode/extensions/ms-python.python-2019.11.50794/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir /home/jp/py/vscode -s --cache-clear
[{"rootid": ".", "root": "/home/jp/py/vscode", "parents": [{"id": "./test_simple.py", "kind": "file", "name": "test_simple.py", "parentid": ".", "relpath": "./test_simple.py"}], "tests": [{"id": "./test_simple.py::test_simple", "name": "test_simple", "source": "./test_simple.py:1", "markers": [], "parentid": "./test_simple.py"}]}]

Steps to reproduce:

Create minimal repo with:

$ cat test_simple.py 
def test_simple():
    assert 2 + 2 == 4
$ cat .vscode/settings.json 
{
    "python.testing.unittestEnabled": false,
    "python.testing.nosetestsEnabled": false,
    "python.testing.pytestEnabled": true
}

run:

code .

open test_simple.py and click Discover Tests

Logs

python /home/jp/.vscode/extensions/ms-python.python-2019.11.50794/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir /home/jp/py/vscode -s --cache-clear
Test Discovery failed: 
TypeError: Cannot read property 'uri' of undefined

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

console.ts:137 [Extension Host] Info Python Extension: 2019-12-31 20:05:49: Cached data exists ActivatedEnvironmentVariables, /home/jp/py/vscode
console.ts:137 [Extension Host] Info Python Extension: 2019-12-31 20:05:49: getActivatedEnvironmentVariables, Class name = b, completed in 1ms, Arg 1: <Uri:/home/jp/py/vscode>, Arg 2: undefined, Arg 3: false
console.ts:137 [Extension Host] Info Python Extension: 2019-12-31 20:05:49: Cached data exists getEnvironmentVariables, /home/jp/py/vscode
console.ts:137 [Extension Host] Info Python Extension: 2019-12-31 20:05:49: > /usr/bin/python ~/.vscode/extensions/ms-python.python-2019.11.50794/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir ~/py/vscode -s --cache-clear
console.ts:137 [Extension Host] Info Python Extension: 2019-12-31 20:05:49: cwd: ~/python-etl/base-code
console.ts:137 [Extension Host] Info Python Extension: 2019-12-31 20:05:49: > /usr/bin/python ~/.vscode/extensions/ms-python.python-2019.11.50794/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir ~/py/vscode -s --cache-clear
console.ts:137 [Extension Host] Info Python Extension: 2019-12-31 20:05:49: cwd: ~/python-etl/base-code
notificationsAlerts.ts:40 Test discovery error, please check the configuration settings for the tests.
onDidNotificationChange @ notificationsAlerts.ts:40
(anonymous) @ notificationsAlerts.ts:26
fire @ event.ts:581
addNotification @ notifications.ts:171
notify @ notificationService.ts:101
(anonymous) @ mainThreadMessageService.ts:83
_showMessage @ mainThreadMessageService.ts:44
$showMessage @ mainThreadMessageService.ts:38
_doInvokeHandler @ rpcProtocol.ts:398
_invokeHandler @ rpcProtocol.ts:383
_receiveRequest @ rpcProtocol.ts:299
_receiveOneMessage @ rpcProtocol.ts:226
(anonymous) @ rpcProtocol.ts:101
fire @ event.ts:581
fire @ ipc.net.ts:453
_receiveMessage @ ipc.net.ts:733
(anonymous) @ ipc.net.ts:592
fire @ event.ts:581
acceptChunk @ ipc.net.ts:239
(anonymous) @ ipc.net.ts:200
t @ ipc.net.ts:28
emit @ events.js:200
addChunk @ _stream_readable.js:294
readableAddChunk @ _stream_readable.js:275
Readable.push @ _stream_readable.js:210
onStreamRead @ internal/stream_base_commons.js:166
console.ts:137 [Extension Host] Error Python Extension: 2019-12-31 20:05:50: Python Extension: displayDiscoverStatus [TypeError: Cannot read property 'uri' of undefined	at /home/jp/.vscode/extensions/ms-python.python-2019.11.50794/out/client/extension.js:1:475432]
t.log @ console.ts:137
$logExtensionHostMessage @ mainThreadConsole.ts:39
_doInvokeHandler @ rpcProtocol.ts:398
_invokeHandler @ rpcProtocol.ts:383
_receiveRequest @ rpcProtocol.ts:299
_receiveOneMessage @ rpcProtocol.ts:226
(anonymous) @ rpcProtocol.ts:101
fire @ event.ts:581
fire @ ipc.net.ts:453
_receiveMessage @ ipc.net.ts:733
(anonymous) @ ipc.net.ts:592
fire @ event.ts:581
acceptChunk @ ipc.net.ts:239
(anonymous) @ ipc.net.ts:200
t @ ipc.net.ts:28
emit @ events.js:200
addChunk @ _stream_readable.js:294
readableAddChunk @ _stream_readable.js:275
Readable.push @ _stream_readable.js:210
onStreamRead @ internal/stream_base_commons.js:166

The text was updated successfully, but these errors were encountered:

ericsnowcurrently · 2019-12-31T20:41:20Z

Thanks for letting us know about this, @JacekPliszka. We'll take a look as soon as we can.

toddljones · 2020-01-02T17:12:42Z

+1. I am having the same issue. Although, intermittently, I am able to reload window then the test discovery starts working. But, even then, when I run the tests it fails out because it can't find the test file. For some reason the relative path test is not included and the test execution fails. See issue #9349

ericsnowcurrently · 2020-01-08T19:29:51Z

@JacekPliszka, I wasn't able to reproduce the problem. Using the simple example you provided, the extension was able to discover the test without problem. Is it happening every time for you?

Since running the command manually worked for you, we know that the problem isn't related to the output of the command. There is something wrong in the extension (at least your install, if not the extension itself). However, it will be hard to determine the cause until we can reliably reproduce the problem.

FWIW, the displayDiscoverStatus reference in the log output you included helps narrow down where the error is originating.

JacekPliszka · 2020-01-08T19:38:24Z

Yes. Happens every time. With any project. This is my first install and the first time I use vscode for anything.

I do not know Javascript so I do not know how to debug it.

What would be useful is better error message/issue detection. Something is undefined but should not be but what and why - I've no idea.

ericsnowcurrently · 2020-01-08T19:46:02Z

Yeah, I agree that the error message is unhelpful. Sorry about that. Would you mind trying the latest version of the extension (released just yesterday)?

JacekPliszka · 2020-01-08T19:52:59Z

updated - no change.

I believe I have something missing in setup and the extension is not detecting it and not telling me and I do not know what to do.

ericsnowcurrently · 2020-01-08T20:01:08Z

Understood. I'll try to narrow down the possible problematic code (based on displayDiscoverStatus) as soon as I can.

ericsnowcurrently · 2020-01-08T20:32:31Z

@JacekPliszka, during discovery did a message like the following pop up?

No tests discovered, please check the configuration settings for the tests.

JacekPliszka · 2020-01-08T20:34:29Z

No

Test discovery error, please check the configuration settings for the tests.

It is at the top of the log I've pasted

ericsnowcurrently · 2020-01-08T20:48:10Z

What is in your settings.json file?

JacekPliszka · 2020-01-08T20:49:37Z

Same what I've pasted under steps to reproduce

$ cat .vscode/settings.json 
{
    "python.testing.unittestEnabled": false,
    "python.testing.nosetestsEnabled": false,
    "python.testing.pytestEnabled": true
}```

ericsnowcurrently · 2020-01-08T20:53:44Z

Do you have a workspace file?

Also, what do you see in the status bar when you discover tests? It should show "Discovering Tests" and then change depending on the outcome. (On success it says "Run Tests".)

JacekPliszka · 2020-01-08T21:09:28Z

This is all I have

$find
.
./test_simple.py
./__pycache__
./__pycache__/test_simple.cpython-37-PYTEST.pyc
./1577819190660.log
./.pytest_cache
./.pytest_cache/v
./.pytest_cache/v/cache
./.pytest_cache/v/cache/stepwise
./.pytest_cache/v/cache/nodeids
./.pytest_cache/v/cache/lastfailed
./.vscode
./.vscode/settings.json

In status bar I have

Discovering Tests

and then

Test discovery failed

ericsnowcurrently · 2020-01-08T21:23:08Z

Thanks. That helps.

ericsnowcurrently · 2020-01-09T18:29:13Z

Given that info, we know that the problem is somewhere under the call to the pytest TestManager's discoverTests() method. There's a lot going on there, so narrowing that down will be somewhat difficult without a consistent reproducer. (FWIW, even though the error mentions displayDiscoverStatus, the problem happens elsewhere and only surfaces in displayDiscoverStatus() due to a promise used there.)

@JacekPliszka, in the Developer Tools console output you included above, we found a relevant error. However, it should have also included a stack trace pointing to the code where the error originated. Were there any such lines there that got missed when you copied the text into this issue? It may help to change the log levels filter at the top of the Developer Tools console (it may say "Default levels"). Change it so only "Errors" is checked.

JacekPliszka · 2020-01-10T11:14:53Z

OK, now I am getting python error too. I do not know why it is calling tests in different directory.

But regardless of it - vscode should be able to handle it gracefully with some meaningful error message.

Errors was checked - I unchecked the other. The result are 3 entries

console.ts:137 [Extension Host] Error Python Extension: 2020-01-10 12:05:56: Failed to parse 
.... <HERE is my python error> ...
Exception: pytest discovery failed (exit code 2)	at ChildProcess.<anonymous> (~/.vscode/extensions/ms-python.python-2020.1.57204/out/client/extension.js:1:438684)	at Object.onceWrapper (events.js:288:20)	at ChildProcess.emit (events.js:200:13)	at maybeClose (internal/child_process.js:1021:16)	at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)]
t.log @ console.ts:137
$logExtensionHostMessage @ mainThreadConsole.ts:39
_doInvokeHandler @ rpcProtocol.ts:398
_invokeHandler @ rpcProtocol.ts:383
_receiveRequest @ rpcProtocol.ts:299
_receiveOneMessage @ rpcProtocol.ts:226
(anonymous) @ rpcProtocol.ts:101
fire @ event.ts:581
fire @ ipc.net.ts:453
_receiveMessage @ ipc.net.ts:733
(anonymous) @ ipc.net.ts:592
fire @ event.ts:581
acceptChunk @ ipc.net.ts:239
(anonymous) @ ipc.net.ts:200
t @ ipc.net.ts:28
emit @ events.js:200
addChunk @ _stream_readable.js:294
readableAddChunk @ _stream_readable.js:275
Readable.push @ _stream_readable.js:210
onStreamRead @ internal/stream_base_commons.js:166
notificationsAlerts.ts:40 Test discovery error, please check the configuration settings for the tests.
onDidNotificationChange @ notificationsAlerts.ts:40
(anonymous) @ notificationsAlerts.ts:26
fire @ event.ts:581
addNotification @ notifications.ts:171
notify @ notificationService.ts:101
(anonymous) @ mainThreadMessageService.ts:83
_showMessage @ mainThreadMessageService.ts:44
$showMessage @ mainThreadMessageService.ts:38
_doInvokeHandler @ rpcProtocol.ts:398
_invokeHandler @ rpcProtocol.ts:383
_receiveRequest @ rpcProtocol.ts:299
_receiveOneMessage @ rpcProtocol.ts:226
(anonymous) @ rpcProtocol.ts:101
fire @ event.ts:581
fire @ ipc.net.ts:453
_receiveMessage @ ipc.net.ts:733
(anonymous) @ ipc.net.ts:592
fire @ event.ts:581
acceptChunk @ ipc.net.ts:239
(anonymous) @ ipc.net.ts:200
t @ ipc.net.ts:28
emit @ events.js:200
addChunk @ _stream_readable.js:294
readableAddChunk @ _stream_readable.js:275
Readable.push @ _stream_readable.js:210
onStreamRead @ internal/stream_base_commons.js:166
console.ts:137 [Extension Host] Error Python Extension: 2020-01-10 12:05:56: Python Extension: displayDiscoverStatus [TypeError: Cannot read property 'uri' of undefined	at ~/.vscode/extensions/ms-python.python-2020.1.57204/out/client/extension.js:1:522555]
t.log @ console.ts:137
$logExtensionHostMessage @ mainThreadConsole.ts:39
_doInvokeHandler @ rpcProtocol.ts:398
_invokeHandler @ rpcProtocol.ts:383
_receiveRequest @ rpcProtocol.ts:299
_receiveOneMessage @ rpcProtocol.ts:226
(anonymous) @ rpcProtocol.ts:101
fire @ event.ts:581
fire @ ipc.net.ts:453
_receiveMessage @ ipc.net.ts:733
(anonymous) @ ipc.net.ts:592
fire @ event.ts:581
acceptChunk @ ipc.net.ts:239
(anonymous) @ ipc.net.ts:200
t @ ipc.net.ts:28
emit @ events.js:200
addChunk @ _stream_readable.js:294
readableAddChunk @ _stream_readable.js:275
Readable.push @ _stream_readable.js:210
onStreamRead @ internal/stream_base_commons.js:166

JacekPliszka · 2020-01-10T11:27:05Z

OK, looks like there was config in ~/.config/Code/ - testing working directory should be per project/workspace, not global.

After fixing this I got

console.ts:137 [Extension Host] Error Python Extension: 2020-01-10 12:24:18: Failed to parse discovered Test [Error: spawn /usr/bin/python ENOENT	at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)	at onErrorNT (internal/child_process.js:456:16)	at processTicksAndRejections (internal/process/task_queues.js:84:9)] {  errno: 'ENOENT',  code: 'ENOENT',  syscall: 'spawn /usr/bin/python',  path: '/usr/bin/python',  spawnargs: [    '~/.vscode/extensions/ms-python.python-2020.1.57204/pythonFiles/testing_tools/run_adapter.py',    'discover',    'pytest',    '--',    '--rootdir',    '~/py/vscode',    '-s',    '--cache-clear'  ]}
t.log @ console.ts:137
$logExtensionHostMessage @ mainThreadConsole.ts:39
_doInvokeHandler @ rpcProtocol.ts:398
_invokeHandler @ rpcProtocol.ts:383
_receiveRequest @ rpcProtocol.ts:299
_receiveOneMessage @ rpcProtocol.ts:226
(anonymous) @ rpcProtocol.ts:101
fire @ event.ts:581
fire @ ipc.net.ts:453
_receiveMessage @ ipc.net.ts:733
(anonymous) @ ipc.net.ts:592
fire @ event.ts:581
acceptChunk @ ipc.net.ts:239
(anonymous) @ ipc.net.ts:200
t @ ipc.net.ts:28
emit @ events.js:200
addChunk @ _stream_readable.js:294
readableAddChunk @ _stream_readable.js:275
Readable.push @ _stream_readable.js:210
onStreamRead @ internal/stream_base_commons.js:166
notificationsAlerts.ts:40 Test discovery error, please check the configuration settings for the tests.
onDidNotificationChange @ notificationsAlerts.ts:40
(anonymous) @ notificationsAlerts.ts:26
fire @ event.ts:581
addNotification @ notifications.ts:171
notify @ notificationService.ts:101
(anonymous) @ mainThreadMessageService.ts:83
_showMessage @ mainThreadMessageService.ts:44
$showMessage @ mainThreadMessageService.ts:38
_doInvokeHandler @ rpcProtocol.ts:398
_invokeHandler @ rpcProtocol.ts:383
_receiveRequest @ rpcProtocol.ts:299
_receiveOneMessage @ rpcProtocol.ts:226
(anonymous) @ rpcProtocol.ts:101
fire @ event.ts:581
fire @ ipc.net.ts:453
_receiveMessage @ ipc.net.ts:733
(anonymous) @ ipc.net.ts:592
fire @ event.ts:581
acceptChunk @ ipc.net.ts:239
(anonymous) @ ipc.net.ts:200
t @ ipc.net.ts:28
emit @ events.js:200
addChunk @ _stream_readable.js:294
readableAddChunk @ _stream_readable.js:275
Readable.push @ _stream_readable.js:210
onStreamRead @ internal/stream_base_commons.js:166
console.ts:137 [Extension Host] Error Python Extension: 2020-01-10 12:24:18: Python Extension: displayDiscoverStatus [TypeError: Cannot read property 'uri' of undefined	at ~/.vscode/extensions/ms-python.python-2020.1.57204/out/client/extension.js:1:522555]
t.log @ console.ts:137
$logExtensionHostMessage @ mainThreadConsole.ts:39
_doInvokeHandler @ rpcProtocol.ts:398
_invokeHandler @ rpcProtocol.ts:383
_receiveRequest @ rpcProtocol.ts:299
_receiveOneMessage @ rpcProtocol.ts:226
(anonymous) @ rpcProtocol.ts:101
fire @ event.ts:581
fire @ ipc.net.ts:453
_receiveMessage @ ipc.net.ts:733
(anonymous) @ ipc.net.ts:592
fire @ event.ts:581
acceptChunk @ ipc.net.ts:239
(anonymous) @ ipc.net.ts:200
t @ ipc.net.ts:28
emit @ events.js:200
addChunk @ _stream_readable.js:294
readableAddChunk @ _stream_readable.js:275
Readable.push @ _stream_readable.js:210
onStreamRead @ internal/stream_base_commons.js:166

command line run:

$ /usr/bin/python ~/.vscode/extensions/ms-python.python-2020.1.57204/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir ~/py/vscode -s --cache-clear
[{"rootid": ".", "root": "~/py/vscode", "parents": [{"id": "./test_simple.py", "kind": "file", "name": "test_simple.py", "parentid": ".", "relpath": "./test_simple.py"}], "tests": [{"id": "./test_simple.py::test_simple", "name": "test_simple", "source": "./test_simple.py:1", "markers": [], "parentid": "./test_simple.py"}]}]

ericsnowcurrently · 2020-01-14T20:21:13Z

Yeah, I agree that the "TypeError: Cannot read property 'uri' of undefined" error is basically useless (both for you and for us). We will work on fixing that (see #9521).

As to the problem, VS Code (actually, Node JS) is saying that your operating system couldn't find /usr/bin/python. Given that you can run that manually without trouble, something fishy is going on. Also, presumably the extension is otherwise working just fine and you can run Python code and debug it without trouble. Is that true?

Please provide the contents of the "Python" output panel. Also, are you using any remote extensions?

eleanorjboyd · 2023-07-14T18:44:35Z

dup of #9347, hopefully, it can be addressed soon now that we are rolling out the rewrite.

eleanorjboyd · 2023-08-16T21:01:55Z

Steps to reproduce:
#9347 (comment)

tried these steps and was able to find and run tests with pytest.

Are people still seeing issues currently on insiders? Could someone provide a minimal repro or steps to create one if so?

eleanorjboyd · 2023-08-18T17:22:05Z

repost from #21373, trying to consolidate discussion of testing with symlinks there.

my msg:
Hi! Looking to fix this but having trouble getting a minimal repro that produces the error. I have tried to replicate it via symlinks on a single disk (but it works) so I think it might only occur when you have symlinks across two different disks. Is that how everyone's setup is?

eleanorjboyd · 2023-09-25T19:37:44Z

Closing this issue since it has been a month and I haven't gotten any response to my above post regarding a minimal repro. Please comment if you are still seeing this and have a repo I can debug with and Ill reopen the issue. Thanks!

eleanorjboyd · 2023-12-18T16:27:19Z

Hello! I was able to figure out a repo and a solution. I have put together a detailed problem report and proposed solution for symlinks. Please check it out here and contribute any thoughts you may have: #22658

eleanorjboyd · 2024-02-26T18:07:20Z

Hello! This bug should be fixed and on vscode insiders! The release to vscode stable will be out by the end of the week. Please let me know if you try it on insiders or stable when it comes out and still doesn't work and I can investigate your specific issue further.

JacekPliszka added triage-needed Needs assignment to the proper sub-team bug Issue identified by VS Code Team member as probable bug labels Dec 31, 2019

kimadeline assigned ericsnowcurrently Dec 31, 2019

kimadeline added the triage label Dec 31, 2019

ghost removed the triage-needed Needs assignment to the proper sub-team label Dec 31, 2019

ericsnowcurrently added area-testing info-needed Issue requires more information from poster labels Jan 8, 2020

ericsnowcurrently removed the info-needed Issue requires more information from poster label Jan 8, 2020

ericsnowcurrently added the info-needed Issue requires more information from poster label Jan 9, 2020

ericsnowcurrently removed the info-needed Issue requires more information from poster label Jan 13, 2020

ericsnowcurrently mentioned this issue Jan 14, 2020

Unhelpful error: "TypeError: Cannot read property 'uri' of undefined". #9581

Closed

ericsnowcurrently added the info-needed Issue requires more information from poster label Jan 14, 2020

This was referenced Jul 11, 2023

Pytest test discovery over SSH does not work #19864

Closed

Tests discovery failing on symlink folder #20718

Closed

Pytest discovery fails on RHEL8 due to symlink #21373

Closed

eleanorjboyd closed this as completed Jul 14, 2023

github-actions bot removed the needs PR Ready to be worked on label Jul 14, 2023

eleanorjboyd reopened this Aug 4, 2023

eleanorjboyd added the needs PR Ready to be worked on label Aug 4, 2023

eleanorjboyd self-assigned this Aug 4, 2023

eleanorjboyd added this to the August 2023 milestone Aug 4, 2023

kieferrm mentioned this issue Aug 6, 2023

Python: Iteration Plan for August 2023 #21771

Closed

28 tasks

eleanorjboyd added the info-needed Issue requires more information from poster label Aug 16, 2023

eleanorjboyd modified the milestones: August 2023, September 2023 Aug 28, 2023

kieferrm mentioned this issue Sep 11, 2023

Python: Iteration Plan for September 2023 #21968

Closed

31 tasks

eleanorjboyd closed this as not planned Won't fix, can't repro, duplicate, stale Sep 25, 2023

github-actions bot removed the needs PR Ready to be worked on label Sep 25, 2023

karthiknadig removed this from the September 2023 milestone Sep 26, 2023

kieferrm mentioned this issue Oct 8, 2023

Python: Iteration Plan for October 2023 #22173

Closed

33 tasks

github-actions bot locked as resolved and limited conversation to collaborators Oct 27, 2023

eleanorjboyd reopened this Dec 18, 2023

github-actions bot added the triage-needed Needs assignment to the proper sub-team label Dec 18, 2023

eleanorjboyd removed info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team labels Jan 25, 2024

eleanorjboyd closed this as completed Feb 26, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Spawn for running test discovery is not following symlinks properly. #9347

Spawn for running test discovery is not following symlinks properly. #9347

JacekPliszka commented Dec 31, 2019 •

edited

Loading

ericsnowcurrently commented Dec 31, 2019

toddljones commented Jan 2, 2020

ericsnowcurrently commented Jan 8, 2020

JacekPliszka commented Jan 8, 2020 •

edited

Loading

ericsnowcurrently commented Jan 8, 2020

JacekPliszka commented Jan 8, 2020

ericsnowcurrently commented Jan 8, 2020

ericsnowcurrently commented Jan 8, 2020

JacekPliszka commented Jan 8, 2020 •

edited

Loading

ericsnowcurrently commented Jan 8, 2020

JacekPliszka commented Jan 8, 2020

ericsnowcurrently commented Jan 8, 2020

JacekPliszka commented Jan 8, 2020 •

edited

Loading

ericsnowcurrently commented Jan 8, 2020

ericsnowcurrently commented Jan 9, 2020

JacekPliszka commented Jan 10, 2020

JacekPliszka commented Jan 10, 2020 •

edited

Loading

ericsnowcurrently commented Jan 14, 2020

eleanorjboyd commented Jul 14, 2023

eleanorjboyd commented Aug 16, 2023 •

edited

Loading

eleanorjboyd commented Aug 18, 2023

eleanorjboyd commented Sep 25, 2023

eleanorjboyd commented Dec 18, 2023

eleanorjboyd commented Feb 26, 2024

Spawn for running test discovery is not following symlinks properly. #9347

Spawn for running test discovery is not following symlinks properly. #9347

Comments

JacekPliszka commented Dec 31, 2019 • edited Loading

Environment data

Expected behaviour

Actual behaviour

Steps to reproduce:

Logs

ericsnowcurrently commented Dec 31, 2019

toddljones commented Jan 2, 2020

ericsnowcurrently commented Jan 8, 2020

JacekPliszka commented Jan 8, 2020 • edited Loading

ericsnowcurrently commented Jan 8, 2020

JacekPliszka commented Jan 8, 2020

ericsnowcurrently commented Jan 8, 2020

ericsnowcurrently commented Jan 8, 2020

JacekPliszka commented Jan 8, 2020 • edited Loading

ericsnowcurrently commented Jan 8, 2020

JacekPliszka commented Jan 8, 2020

ericsnowcurrently commented Jan 8, 2020

JacekPliszka commented Jan 8, 2020 • edited Loading

ericsnowcurrently commented Jan 8, 2020

ericsnowcurrently commented Jan 9, 2020

JacekPliszka commented Jan 10, 2020

JacekPliszka commented Jan 10, 2020 • edited Loading

ericsnowcurrently commented Jan 14, 2020

eleanorjboyd commented Jul 14, 2023

eleanorjboyd commented Aug 16, 2023 • edited Loading

eleanorjboyd commented Aug 18, 2023

eleanorjboyd commented Sep 25, 2023

eleanorjboyd commented Dec 18, 2023

eleanorjboyd commented Feb 26, 2024

JacekPliszka commented Dec 31, 2019 •

edited

Loading

JacekPliszka commented Jan 8, 2020 •

edited

Loading

JacekPliszka commented Jan 8, 2020 •

edited

Loading

JacekPliszka commented Jan 8, 2020 •

edited

Loading

JacekPliszka commented Jan 10, 2020 •

edited

Loading

eleanorjboyd commented Aug 16, 2023 •

edited

Loading