-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Restore OSX tests, moving them to single --autoloading available
step
#18335
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.
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
Conversation
…ll/load from logs
…ticular being flaky
…sking changing behaviour for duckdb
6e24799
to
8968899
Compare
OSX.yml is a pass after this: https://github.com/carlopi/duckdb/actions/runs/16410520032/job/46365478159 LinuxRelease.yml failure is networking, can be either restarted or also verified on the fork: https://github.com/carlopi/duckdb/actions/runs/16410520037 (once that completes) |
Thanks! |
Restore OSX tests, moving them to single `--autoloading available` step (duckdb/duckdb#18335)
Restore OSX tests, moving them to single `--autoloading available` step (duckdb/duckdb#18335) Co-authored-by: krlmlr <krlmlr@users.noreply.github.com>
@@ -112,6 +112,15 @@ void SQLLogicTestRunner::EndLoop() { | |||
} | |||
} | |||
|
|||
ExtensionLoadResult SQLLogicTestRunner::LoadExtension(DuckDB &db, const std::string &extension) { | |||
Connection con(db); | |||
auto result = con.Query("LOAD " + extension); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change means that every single test we run by default runs into at least one exception ("core_functions" failed to load). Can we only run LOAD ...
when autoloading is set to a non-default value, instead of enabling this behavior by default?
This is on top of #18306, moving away from custom logic in the unittester and moving toward using queries (in this case,
LOAD <extension_name>
).Also remove
DUCKDB_TEST_REMOTE_INSTALL
, now available via config--autoloading all
.