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

test: Explicitly state change detector split for test #1228

Merged
merged 1 commit into from Mar 24, 2023

Conversation

AndrewSisley
Copy link
Contributor

Relevant issue(s)

Resolves #1227

Description

Explicitly states the change detector split for TestSchemaSimpleErrorsGivenDuplicateSchema. This test caused the change detector to auto-split between setup and run incorrectly causing a test failure. Here we explicitly tell it to split between the two schema changes.

This test caused the change detector to auto-split between setup and run incorrectly causing a test failure. Here we explicitly tell it to split between the two schema changes.
@AndrewSisley AndrewSisley added bug Something isn't working area/testing Related to any test or testing suite labels Mar 24, 2023
@AndrewSisley AndrewSisley added this to the DefraDB v0.5 milestone Mar 24, 2023
@AndrewSisley AndrewSisley requested a review from a team March 24, 2023 18:21
@AndrewSisley AndrewSisley self-assigned this Mar 24, 2023
@codecov
Copy link

codecov bot commented Mar 24, 2023

Codecov Report

Merging #1228 (6c3a14b) into develop (0cddca5) will decrease coverage by 0.04%.
The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #1228      +/-   ##
===========================================
- Coverage    68.61%   68.58%   -0.04%     
===========================================
  Files          181      181              
  Lines        17144    17144              
===========================================
- Hits         11764    11758       -6     
- Misses        4422     4426       +4     
- Partials       958      960       +2     

see 4 files with indirect coverage changes

@source-devs
Copy link

Benchmark Results

Summary

  • 0 Benchmarks successfully compared.
  • 0 Benchmarks were ✅ Better.
  • 0 Benchmarks were ❌ Worse .
  • 0 Benchmarks were ✨ Unchanged.
✅ See Better Results...
time/opdelta
 
❌ See Worse Results...
time/opdelta
 
✨ See Unchanged Results...
time/opdelta
 
🐋 See Full Results...

@AndrewSisley AndrewSisley added the action/no-benchmark Skips the action that runs the benchmark. label Mar 24, 2023
Copy link
Member

@jsimnz jsimnz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ezpz

@AndrewSisley AndrewSisley merged commit 55f4e05 into develop Mar 24, 2023
11 checks passed
@AndrewSisley AndrewSisley deleted the sisley/fix/I1227-schema-change-detector-test branch March 24, 2023 21:56
shahzadlone pushed a commit that referenced this pull request Apr 13, 2023
This test caused the change detector to auto-split between setup and run incorrectly causing a test failure. Here we explicitly tell it to split between the two schema changes.
shahzadlone pushed a commit to shahzadlone/defradb that referenced this pull request Feb 23, 2024
…1228)

This test caused the change detector to auto-split between setup and run incorrectly causing a test failure. Here we explicitly tell it to split between the two schema changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action/no-benchmark Skips the action that runs the benchmark. area/testing Related to any test or testing suite bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TestSchemaSimpleErrorsGivenDuplicateSchema fails change detector
3 participants