Skip to content

Conversation

0xgouda
Copy link

@0xgouda 0xgouda commented May 31, 2025

This adds a test that runs sqlsmith on a sqlsmith_test database that has pg_duckdb extension enabled and any caused crashes will get detected by the logs in the teardown of pg fixture

...
assert (
    "was terminated by signal 6" not in logs
), "Postgres crashed! Check the logs above."
assert (
    "was terminated by signal 11" not in logs
), "Postgres crashed! Check the logs above."

closes: #222

@0xgouda 0xgouda force-pushed the sqlsmith-test branch 2 times, most recently from 1413085 to 29b3996 Compare June 6, 2025 20:02
@0xgouda
Copy link
Author

0xgouda commented Aug 26, 2025

@JelteF
It's been about 3 months since I opened this. Can I have a review when convenient?

Actually, the failing test after i rebased is because SQLSmith detected a crash:

_________________ ERROR at teardown of test_fuzzy_pg_crashing __________________
...
E   AssertionError: Postgres crashed! Check the logs above.
E   assert 'was terminated by signal 6' not in '2025-08-26 ...\tlimit 78\n'

@JelteF JelteF added this to the 1.1.0 milestone Aug 27, 2025
@JelteF
Copy link
Collaborator

JelteF commented Aug 27, 2025

Sorry for not responding. I've been trying to focus on getting 1.0 out (which has been going less well than intended). I'll get back to this after I've actually done that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fuzzing using SQLsmith
2 participants