You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm testing the release candidate, and I have this unexpected behavior:
no matter the verbosity level, a venom.log file is always generated
the same venom.log file used to be overridden at every run. It's not the case anymore so you quickly get dozens of venom*.log file in your current dir.
[...]
$ ./venom1.1.0 run tests [trac] writing venom.9.log • Title of TestSuite (tests/deploy.yml) • TestCase-with-default-value-exec-cmd-Check-if-exit-code-1 PASSfinal status: PASS
$ ./venom1.1.0 run tests [trac] writing venom.10.log • Title of TestSuite (tests/deploy.yml) • TestCase-with-default-value-exec-cmd-Check-if-exit-code-1 PASSfinal status: PASS
$ ll venom*log | wc -l35
I tested with the latest stable version (1.0.1), and it worked as expected:
$ ./venom1.0.1 versionVersion venom: v1.0.1
$ ./venom1.0.1 run tests • Title of TestSuite (tests/deploy.yml) • TestCase-with-default-value-exec-cmd-Check-if-exit-code-1 SUCCESS
$ ./venom1.0.1 run tests • Title of TestSuite (tests/deploy.yml) • TestCase-with-default-value-exec-cmd-Check-if-exit-code-1 SUCCESS
$ ./venom1.0.1 run tests • Title of TestSuite (tests/deploy.yml) • TestCase-with-default-value-exec-cmd-Check-if-exit-code-1 SUCCESS
$ ./venom1.0.1 run tests -v [trac] writing venom.log • Title of TestSuite (tests/deploy.yml) • TestCase-with-default-value-exec-cmd-Check-if-exit-code-1 SUCCESS
$ ./venom1.0.1 run tests -v [trac] writing venom.log • Title of TestSuite (tests/deploy.yml) • TestCase-with-default-value-exec-cmd-Check-if-exit-code-1 SUCCESS
$ ./venom1.0.1 run tests -v [trac] writing venom.log • Title of TestSuite (tests/deploy.yml) • TestCase-with-default-value-exec-cmd-Check-if-exit-code-1 SUCCESS
The text was updated successfully, but these errors were encountered:
Okay so the "write in another file every time" is expected. But still, it should not create a log file when the verbosity level is 0 (unspecified) it think?
It is an expected behaviour.
When a test fails, it is regularly necessary to check the log file venom.log, without having to relaunch the full test.
On CI/CD environment, we don't care about the file creation as the 'workspace' is often ephemeral. If you run venom outside the ci/cd, you probably need to manage the log file as you want matching the exit code. venom run && rm venom*.log
mlcdf
changed the title
Running venon v1.1.0-rc.1 always create a venom.log file even with verbosity = 0
Running venom v1.1.0-rc.1 always create a venom.log file even with verbosity = 0
Nov 8, 2022
Hi there,
I'm testing the release candidate, and I have this unexpected behavior:
I tested with the latest stable version (1.0.1), and it worked as expected:
The text was updated successfully, but these errors were encountered: