Summer versionless test #495
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hey! It worked! "Nothing to do" is the message I've been looking for. I'll update the slim CI issue w/ the before-and-after comparison once CI finishes running here. But this is great news: 
|
|
Woohoo! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Testing the CI job timing with the same change, now that the prod environment is working in Versionless and we've had a successful Nightly build.
The hope here is that there is a noticeable difference in CI timing from the test I ran yesterday, and (more importantly, since timing might have been affected by the missing data from the detector source tables yesterday) that the logs show that CI is not rebuilding incremental models that had no changes made to them in this PR.