testing with -run-only
does not detect fails
#22778
Labels
Bug
This tag is applied to issues which reports bugs.
-run-only
does not detect fails
#22778
Describe the bug
Using
-run-only
argument to test only a single test function within a file does not detect a failure, or seems does not check anything.By the way
-run-only
is documented if you typev help test
but it doesn't if you typev test help
.Reproduction Steps
I have a simple test file with two functions one should pass and another shouldn't:
I test the whole file and fails as expected:
Then I use the flag
-run-only
for the function that should pass and "passes":Then I use the flag
-run-only
for the function that should fail and "passes" too:The same happens using
-stats
just printing the extra info...Expected Behavior
Test correctly a single function using the filter
-run-only
.Current Behavior
Seems argument
-run-only
does not perform any test at all.Possible Solution
No response
Additional Information/Context
No response
V version
V 0.4.8 b30be51
Environment details (OS name and version, etc.)
V full version: V 0.4.8 da3112e.b30be51
OS: linux, Ubuntu 20.04.6 LTS
Processor: 4 cpus, 64bit, little endian, Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz
vexe: /home/jorge/v/v
vexe mtime: 2024-11-06 15:56:20
vroot: OK, value: /home/jorge/v
VMODULES: OK, value: /home/jorge/.vmodules
VTMP: OK, value: /tmp/v_1000
Git version: git version 2.25.1
Git vroot status: weekly.2024.36-458-gb30be518
.git/config present: true
CC version: cc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
emcc version: N/A
thirdparty/tcc status: thirdparty-linux-amd64 0134e9b9
Huly®: V_0.6-21224
Note
You can use the 👍 reaction to increase the issue's priority for developers.
Please note that only the 👍 reaction to the issue itself counts as a vote.
Other reactions and those to comments will not be taken into account.
The text was updated successfully, but these errors were encountered: