I guess you pull'd the api submodule to run the tests? If you did, you need to commit the api directory so it takes into account the lib upgrade. If you didn't pull the api submodule... Well, you need to do it ^^
Sorry if I didn't explain what this task was about, I was planning to do it myself so I didn't really bothered. More info on submodules: https://git-scm.com/book/en/v2/Git-Tools-Submodules
That's weird. How did you manage to push this diff then? Arcanist doesn't normally let you diff when the tests do not pass. Please tell me what you did, there might a bug there.
Other than that, the procedure for the lib on Linux is:
- ./api.sh (let it run in the background)
- ./gradlew build
- git submodule init
- git submodule update
- Run the API by following the steps on the wiki (or the contents of the script api.sh)
- gradlew.bat build
Again, if you did not do this, there's a big problem because it shouldn't be possible to diff without doing those.
All I did is arc diff as shown in the user guide... If you scroll up, it says under Diff Detail, Unit Test Coverage is none, maybe it's because I didn't modify a main source file, so it was looking for a test test?
Yes and no, because of how Arc works, unit tests are categorized as "lint", it's normal (as of now, I will try to change that someday if I get time). It's possible that it doesn't run tests because you only modified tests? I need to check into that.