Skip to content

Incorrect utPLSQL version reported #136

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
jgebal opened this issue Mar 28, 2019 · 4 comments
Closed

Incorrect utPLSQL version reported #136

jgebal opened this issue Mar 28, 2019 · 4 comments
Assignees
@pesse

Comments

@jgebal
Copy link
Member

jgebal commented Mar 28, 2019

version reported by cli is not matching what is in-database.
I get:

Successfully connected to database. UtPLSQL core: 3.1.1
...
Running on utPLSQL 3.1.1

Would expect to see: 3.1.6
@pesse
Copy link
Member

pesse commented Mar 29, 2019

Can you provide the output of utplsql info user/pw@connectstring ?
This is very strange, because we get the right output for all versions tested against:
https://travis-ci.org/utPLSQL/utPLSQL-cli/builds/512875014

@jgebal
Copy link
Member Author

jgebal commented Mar 29, 2019

This is what I get when I run locally.

$ utPLSQL-cli/bin/utplsql info ut3/ut3@127.0.0.1:1551/orclcdb
utPLSQL-cli 3.1.6.local
utPLSQL-java-api 3.1.6.411
utPLSQL 3.1.7.2748

select ut.version from dual;

v3.1.7.2748-develop

 utPLSQL-cli/bin/utplsql run ${UT3_TESTER}/${UT3_TESTER_PASSWORD}@${CONNECTION_STR} \
-source_path=source -owner=ut3 \
-test_path=test -c \
-f=ut_coverage_sonar_reporter -o=coverage.xml \
-f=ut_coverage_html_reporter  -o=coverage.html \
-f=ut_coveralls_reporter      -o=coverage.json \
-f=ut_sonar_test_reporter     -o=test_results.xml \
-f=ut_junit_reporter          -o=junit_test_results.xml \
-f=ut_tfs_junit_reporter      -o=tfs_test_results.xml \
-f=ut_documentation_reporter  -o=test_results.log -s \
-scc
########## utPLSQL cli ###########
#                                #
#   utPLSQL-cli 3.1.6.local      #
#   utPLSQL-java-api 3.1.6.411   #
#   Java-Version: 1.8.0_181      #
#   ORACLE_HOME: null            #
#   NLS_LANG: null               #
#                                #
#   Thanks for testing!          #
#                                #
##################################

Use connection string jdbc:oracle:thin:****/****@127.0.0.1:1551/orclcdb
Skipping Compatibility check with framework version, expecting the latest version to be installed in database
Successfully connected to database. UtPLSQL core: 3.1.1
Oracle-Version: 18.0.0.0.0
Running tests now.
--------------------------------------
TestRunner initialized
Running on utPLSQL 3.1.1
Initializing reporters

@jgebal
Copy link
Member Author

jgebal commented Mar 29, 2019

It seems to be related to -scc option.
When I run without scc, it works fine.

utPLSQL-cli/bin/utplsql run ${UT3_TESTER}/${UT3_TESTER_PASSWORD}@${CONNECTION_STR} \
-source_path=source -owner=ut3 \
-test_path=test -c \
-f=ut_coverage_sonar_reporter -o=coverage.xml \
-f=ut_coverage_html_reporter  -o=coverage.html \
-f=ut_coveralls_reporter      -o=coverage.json \
-f=ut_sonar_test_reporter     -o=test_results.xml \
-f=ut_junit_reporter          -o=junit_test_results.xml \
-f=ut_tfs_junit_reporter      -o=tfs_test_results.xml \
-f=ut_documentation_reporter  -o=test_results.log -s
########## utPLSQL cli ###########
#                                #
#   utPLSQL-cli 3.1.6.local      #
#   utPLSQL-java-api 3.1.6.411   #
#   Java-Version: 1.8.0_181      #
#   ORACLE_HOME: null            #
#   NLS_LANG: null               #
#                                #
#   Thanks for testing!          #
#                                #
##################################

Use connection string jdbc:oracle:thin:****/****@127.0.0.1:1551/orclcdb
Successfully connected to database. UtPLSQL core: v3.1.7.2748-develop
Oracle-Version: 18.0.0.0.0
Running tests now.
--------------------------------------
TestRunner initialized
Running on utPLSQL v3.1.7.2748-develop
Initializing reporters

@pesse
Copy link
Member

pesse commented Mar 29, 2019

There we go - it's the scc and it even says what it does:
Skipping Compatibility check with framework version, expecting the latest version to be installed in database

Two issues:
First of all, it assumes the wrong latest version
Second, even when assuming we should somehow still try to get the actual version and state this in the logs.

Thanks for the finding :)

@pesse pesse self-assigned this Mar 29, 2019
@pesse pesse mentioned this issue Apr 4, 2019
Merged
@pesse pesse reopened this Apr 4, 2019
@pesse pesse closed this as completed in 4317e4e Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pesse pesse

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jgebal @pesse