It's an interesting issue.
I didn't observe this behaviour on our deployments.
Our Travis build is starting with a clean database, deploys latest release, deploys develop branch and then runs unit tests using last release version to test develop version.

I didn't observe that behaviour when developing the cache mechanism.
Will need to do some exploratory tests to see if i can reproduce this.
Even out Travis demo project runs fine the with clean database and fresh install.

Can you try to explore the issue on your end a bit more?

@MickeVr
Can you provide info on:

• database version and edition
• operating system of the DB

@MickeVr

The first test suite that is executed results in a empty output file. Also no screen output is displayed. The second test suite is reporting results. Manually executing utPLSQL-sql-cli after this Jenkins job results in a on-empty output file.

If you run:

• utPLSQL-sql-cli first_suite
• utPLSQL-sql-cli first_suite
• utPLSQL-sql-cli second_suite

Do you get expected results?

Hi Jacek,

Oracle database is Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production, running on Windows. I will investigate the issue further.

@jgebal

Indeed, by running
utPLSQL-sql-cli first_suite
utPLSQL-sql-cli first_suite
utPLSQL-sql-cli second_suite
I get my 'correct' output. The first run of the first suite does not execute anything, and acts in the same way as running it with a suitepath that does not exist on the schema.

Hi @MickeVr
I took the following steps to reproduce.

1. Drop user containing utPLSQL
2. Install fresh utPSQL v3.0.4 into database.
3. Install tests into separate schema (UT3_TESTER)
4. run:
   ut_run UT3_TESTER/ut3@xe -p=UT3_TESTER -f=ut_documentation_reporter -s -f=ut_xunit_reporter -o=xunit.xml

I see results on first run using utPLSQL-sql-cli as well as utPLSQL-cli.
I've tested on 11gR2XE, 12.1SE and 12.2SE

Please let me know if you're still facing this issue. I'm unable to reproduce.

Hi @jgebal,

Suddenly the issue didn't occur any more, starting with a commit where we solved an occurrence of issue 516 (no new line between the suite and the unit test annotations).

I removed a new line from an existing unit test and the issue reoccurs, so I conclude it is already a known issue.

Duplicate of #516

Ok, now that makes sense.
If you would look into log file of background process of sql-cli after the empty run, you would see the exception related to 3.0.4 restriction on package level annotations.

Related to #523
I'm closing this issue for now - it will be more obvious after additional logging on annotations is added.