Skip to content
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

[chores] split long running destination tests for nightly builds #997

Closed
rudolfix opened this issue Feb 24, 2024 · 0 comments · Fixed by #1159
Closed

[chores] split long running destination tests for nightly builds #997

rudolfix opened this issue Feb 24, 2024 · 0 comments · Fixed by #1159
Assignees
Labels
tech-debt Leftovers from previous sprint that should be fixed over time

Comments

@rudolfix
Copy link
Collaborator

There are several tests that run very slowly. Most of them are merge and replace tests with various configurations. They are especially slow on lakehouses. What we need to do

  1. identify long running tests and move them to separate workflows that we will run nightly
  2. make sure that workflows triggered by PR run within 1-2 hours
  3. make sure that (2) is more or less covered. it would be good to keep single comprehensive merge and replace tests in there
@rudolfix rudolfix added the tech-debt Leftovers from previous sprint that should be fixed over time label Feb 24, 2024
@rudolfix rudolfix moved this from Todo to Planned in dlt core library Mar 5, 2024
@rudolfix rudolfix moved this from Planned to In Progress in dlt core library Apr 2, 2024
@sh-rp sh-rp linked a pull request Apr 3, 2024 that will close this issue
@github-project-automation github-project-automation bot moved this from In Progress to Done in dlt core library Apr 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tech-debt Leftovers from previous sprint that should be fixed over time
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants