2.3.7 data.sql are not any longer exectued

[leomayer]

After upgrading from 2.3.6. to 2.3.7. the data.sql scripts are not any longer executed when starting test runs.

The scripts are located in src/test/resources

I've checked this and since I need to load data into my own properties I did it with

public class ApplicationInitDocumat implements ApplicationListener<ContextRefreshedEvent> {

	@Autowired
	private MyDBController consistentChecker;
	/**
	 * Listen to startup/context refresh events
	 */
	@Override
	public void onApplicationEvent(ContextRefreshedEvent event) {
        // failed to load data  from database which is loaded via data.sql

[wilkinsona]

The scripts are loaded from the classpath so it should make no difference if they're in src/test/resources or src/main/resources as long as the resources in those locations have been placed on the classpath by whatever you're using to run your tests.

We have numerous integration and smoke tests that rely on schema.sql and data.sql files being executed and they are all passing so it's not clear to me what may be causing your problem. If you would like us to spend some more time investigating, please spend some time providing a complete yet minimal sample that reproduces the problem. You can share it with us by pushing it to a separate repository on GitHub or by zipping it up and attaching it to this issue.

[leomayer]

I tried to reproduce the issue with a simple project but didn't succeed. I digged little bit deeper and turned on the log level for our real project. I attach the logs to the issue. It seems like the data.sql are exectuted but they are not fetched from the DB. Data which was inserted and could be looked for:

• COUNTRY
• PROPERTY_EXTENSION
  boot2.3.6.log.gz
  boot2.3.7.log.gz

Remark: The logs are up to the point where an JPARepostiory.findAll() was executed. Immediately afterwards a breakpoint was set and the logs ended. While in 2.3.6 the findAll() returned a list of 8 items the 2.3.7 version returned 0 items. Therefore I concluded that the data.sql were not executed. But perhaps the conclusion was too quick and the root cause is somewhere else.

[wilkinsona]

Thanks for the logs. Unfortunately, there's nothing in them that's an immediately obvious reason for the different behaviour. I'm not sure what logging you enabled, but the output doesn't seem to include any Spring Framework or Spring Boot code. For example, I'd expect to see logging from org.springframework.jdbc.datasource.init.ScriptUtils but didn't see any in either file. Could you change you logging configuration to include org.springframework.jdbc to confirm whether or not the files are being processed?

I tried to reproduce the issue with a simple project but didn't succeed

This would suggest that the problem's somehow specific to your environment or to your main application's dependencies. The former will make it hard for us to diagnose the problem. The latter will too without a sample with which we can reproduce the problem.

[leomayer]

Sorry, I have no clue what kind of options I should enable. I did already on

logging:
  level:
    root: DEBUG

Since they are not sufficient plz advice which one to set.

[wilkinsona]

That's a strange one too. Root-level debug logging should have been sufficient. I suspect you may have some configuration elsewhere that's overriding that configuration for all but Hibernate and handful of other loggers. Unfortunately, I can't tell if that's definitely the case without knowing more about your application and its configuration. I think we've reached the point where we need a sample that reproduces the problem to make some progress.