The GitHub Actions job "Build" on texera.git/perf/try-remove-test-limit has failed. Run started by GitHub user Yicong-Huang (triggered by Yicong-Huang).
Head commit for run: 31b8fe845f833dc343721516b651b41179503845 / Yicong Huang <[email protected]> perf(test): truncate tables on each spec setup With Tags.limit lifted, specs that share a database (the singleton EmbeddedPostgres in MockTexeraDB or the CI's texera_db_for_test_cases service) saw uid=1 / wid=1 collisions because rows from a previous spec were not always cleaned up at afterEach/afterAll boundaries. Have both setup paths run TRUNCATE on every table in the texera_db schema before the caller does its inserts: - MockTexeraDB.initializeDBAndReplaceDSLContext now calls truncateAllTables() after ensureInitialized(); the singleton stays alive but its tables are reset for each spec. - TestUtils.initiateTexeraDBForTestCases similarly truncates the external Postgres before specs that use it (PauseSpec, ReconfigurationSpec, DataProcessingSpec) issue their inserts. This is robust against rows left over by failed tests, retried tests, or specs whose afterAll/afterEach skipped cleanup. Report URL: https://github.com/apache/texera/actions/runs/24950570370 With regards, GitHub Actions via GitBox
