Oracle tests take 30+ minutes per test method on test classes not setting the target schema

Description

Some tests do not test, or reset of purpose, the target schema (because they are creating tables in the default schema, which might not be the configured one). These tests take over 30 minutes per method running against a Oracle 12c enterprise edition setup.

Since Oracle is the only database having this particular oddity, and setting the schema makes other database test fails, I'll setup a method the test can call to verify if resetting the schema is a good idea, or not.

Environment

None

Status

Assignee

Andrea Aime

Reporter

Andrea Aime

Triage

None

Components

Fix versions

Priority

Medium
Configure