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

update test results summary after BLS 0.10.1 update #810

Merged
merged 1 commit into from
Mar 13, 2020
Merged

update test results summary after BLS 0.10.1 update #810

merged 1 commit into from
Mar 13, 2020

Conversation

tersec
Copy link
Contributor

@tersec tersec commented Mar 13, 2020

Intentionally isolating this in its own PR.

The removed tests are legitimately removed/skipped for now, but random PRs ideally shouldn't have to be updating this -- so, this way, make the awareness/consciousness clear.

@tersec tersec merged commit 794b374 into devel Mar 13, 2020
@delete-merged-branch delete-merged-branch bot deleted the rag branch March 13, 2020 15:18
@@ -205,11 +198,10 @@ OK: 9/9 Fail: 0/9 Skip: 0/9
OK: 1/1 Fail: 0/1 Skip: 0/1
## [Unit - Spec - Block processing] Attestations [Preset: minimal]
```diff
+ Empty aggregation bit OK
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this one should appear in SKIPPED

@@ -68,11 +68,9 @@ OK: 20/20 Fail: 0/20 Skip: 0/20
```diff
+ [Invalid] att1_bad_extra_index OK
+ [Invalid] att1_bad_replaced_index OK
+ [Invalid] att1_duplicate_index_double_signed OK
Copy link
Contributor

Choose a reason for hiding this comment

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

and this

+ [Invalid] att1_duplicate_index_normal_signed OK
+ [Invalid] att2_bad_extra_index OK
+ [Invalid] att2_bad_replaced_index OK
+ [Invalid] att2_duplicate_index_double_signed OK
Copy link
Contributor

Choose a reason for hiding this comment

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

and this

Copy link
Contributor Author

Choose a reason for hiding this comment

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

As with the others, this is just rendering consistent/reaching a fixpoint on the interaction between #794 and #780

@@ -129,7 +127,6 @@ OK: 2/2 Fail: 0/2 Skip: 0/2
OK: 9/9 Fail: 0/9 Skip: 0/9
## Official - Sanity - Blocks [Preset: mainnet]
```diff
+ [Invalid] expected_deposit_in_block OK
Copy link
Contributor

Choose a reason for hiding this comment

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

and this

Copy link
Contributor Author

Choose a reason for hiding this comment

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

okay, well, that might be true, regarding all these "OK" statuses that should be "Skipped", but I just wanted to get devel internally consistent

@arnetheduck
Copy link
Member

shouldn't CI check that the MD is accurate, so that if someone forgets to update it, it fails?

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.

3 participants