nimbus-eth1/TracerTests.md

TracerTests
===
## TracerTests
```diff
  block46147.json                                                 Skip
  block46400.json                                                 Skip
  block46402.json                                                 Skip
  block47205.json                                                 Skip
  block48712.json                                                 Skip
  block48915.json                                                 Skip
  block49018.json                                                 Skip
  block97.json                                                    Skip
```
OK: 0/8 Fail: 0/8 Skip: 8/8

---TOTAL---
OK: 0/8 Fail: 0/8 Skip: 8/8
add tracer test 2018-12-12 22:18:46 +07:00			`TracerTests`
			`===`
			`## TracerTests`
			```diff
Remove `RawData` from possible leaf payload types (#2794) This kind of data is not used except in tests where it is used only to create databases that don't match actual usage of aristo. Removing simplifies future optimizations that can focus on processing specific leaf types more efficiently. A casualty of this removal is some test code as well as some proof generation code that is unused - on the surface, it looks like it should be possible to port both of these to the more specific data types - doing so would ensure that a database written by one part of the codebase can interact with the other - as it stands, there is confusion on this point since using the proof generation code will result in a database of a shape that is incompatible with the rest of eth1. 2024-11-02 10:29:16 +01:00			`block46147.json Skip`
			`block46400.json Skip`
			`block46402.json Skip`
			`block47205.json Skip`
			`block48712.json Skip`
			`block48915.json Skip`
			`block49018.json Skip`
			`block97.json Skip`
add tracer test 2018-12-12 22:18:46 +07:00			```
Remove `RawData` from possible leaf payload types (#2794) This kind of data is not used except in tests where it is used only to create databases that don't match actual usage of aristo. Removing simplifies future optimizations that can focus on processing specific leaf types more efficiently. A casualty of this removal is some test code as well as some proof generation code that is unused - on the surface, it looks like it should be possible to port both of these to the more specific data types - doing so would ensure that a database written by one part of the codebase can interact with the other - as it stands, there is confusion on this point since using the proof generation code will result in a database of a shape that is incompatible with the rest of eth1. 2024-11-02 10:29:16 +01:00			`OK: 0/8 Fail: 0/8 Skip: 8/8`
update test logs 2019-01-06 14:27:06 +01:00
			`---TOTAL---`
Remove `RawData` from possible leaf payload types (#2794) This kind of data is not used except in tests where it is used only to create databases that don't match actual usage of aristo. Removing simplifies future optimizations that can focus on processing specific leaf types more efficiently. A casualty of this removal is some test code as well as some proof generation code that is unused - on the surface, it looks like it should be possible to port both of these to the more specific data types - doing so would ensure that a database written by one part of the codebase can interact with the other - as it stands, there is confusion on this point since using the proof generation code will result in a database of a shape that is incompatible with the rest of eth1. 2024-11-02 10:29:16 +01:00			`OK: 0/8 Fail: 0/8 Skip: 8/8`