Skip to content

Conversation

carlopi
Copy link
Contributor

@carlopi carlopi commented Jul 20, 2025

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.

@duckdb-draftbot duckdb-draftbot marked this pull request as draft July 21, 2025 05:21
@carlopi carlopi marked this pull request as ready for review July 21, 2025 05:21
@carlopi carlopi force-pushed the osx_extension_tests branch from 6e24799 to 8968899 Compare July 21, 2025 06:55
@duckdb-draftbot duckdb-draftbot marked this pull request as draft July 21, 2025 06:55
@carlopi carlopi marked this pull request as ready for review July 21, 2025 06:56
@carlopi
Copy link
Contributor Author

carlopi commented Jul 21, 2025

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)

@Mytherin Mytherin merged commit 10fee32 into duckdb:v1.3-ossivalis Jul 22, 2025
49 of 50 checks passed
@Mytherin
Copy link
Collaborator

Thanks!

github-actions bot pushed a commit to duckdb/duckdb-r that referenced this pull request Jul 22, 2025
Restore OSX tests, moving them to single `--autoloading available` step (duckdb/duckdb#18335)
github-actions bot added a commit to duckdb/duckdb-r that referenced this pull request Jul 22, 2025
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);
Copy link
Collaborator

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?

@carlopi carlopi deleted the osx_extension_tests branch August 17, 2025 20:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants