If currentTrackBundle is updated at the start of the block and then something goes wrong in the middle (e.g. one of the skipFully calls) then the extractor wont resume from the correct place. This would be caught by our extractor tests if we had a test sample that requires skipping to the sample data. I'll try and construct one of those. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=131191174
| Name |
Last commit
|
Last Update |
|---|---|---|
| demo | Loading commit data... | |
| extensions | Loading commit data... | |
| gradle/wrapper | Loading commit data... | |
| library | Loading commit data... | |
| playbacktests | Loading commit data... | |
| testutils | Loading commit data... | |
| .gitignore | Loading commit data... | |
| CONTRIBUTING.md | Loading commit data... | |
| ISSUE_TEMPLATE | Loading commit data... | |
| LICENSE | Loading commit data... | |
| README.md | Loading commit data... | |
| RELEASENOTES.md | Loading commit data... | |
| build.gradle | Loading commit data... | |
| gradle.properties | Loading commit data... | |
| gradlew | Loading commit data... | |
| gradlew.bat | Loading commit data... | |
| settings.gradle | Loading commit data... |