* Add a hexagon build presubmit
Also update Hexagon Docker file
* Add a todo for to enable unit test for hexagon
Co-authored-by: Advait Jain <advaitjain@users.noreply.github.com>
* Make size check workflow error out if memory footprint increase
between head of main and this PR.
This error can be disabled by putting MEM_CHANGE_OK= tag.
In either case, a memory footprint comparison report will be produced
as part of this workflow action.
The plan is for the code reviewer to audit the report when the
PR increase memory footprint and only
allow the PR that increase memory footprint to be merged with
MEM_CHANGE_OK=what_is_the_reason_for_this_increase_and_why_this_is_ok
The PR shall be up to date for the comparison to be accurate.
So before applying MEM_CHANGE_OK=, please make the PR branch up to date.
BUG=http://b/196637015
* Fix an if condition
* Fix size_check failure for ci:test label
* Add debug message to debug live
* Update comment
* Remove redundant checkout and add HEAD
This is an attempt to fix size_check workflow not
working for ci:test label
BUG=http://b/196637015
Co-authored-by: Advait Jain <advaitjain@users.noreply.github.com>
* Update size_check.yml and rename fusion_f1.json to more general
binary_size.json.
Updte the size_check workflow to be able to launched it
manually for test. Also update it so that it can build image.
The next step is to test whether this will lead to two
PR to have merge conflict always.
BUG=http://b/196637015
* Remove currently unused code
* Add option to only do a build for the vision_p6.
BUG=http://b/196459172
* Only build for Vision P6 as part of presubmit checks.
* make running the tests optional.
* fix whitespace.
* Address review comments.
Fixes#294
Copy from xtensa ci scripts to run the test script inside of a docker
container.
We use the espressif/idf:release-v4.3 image.
Add a build that builds the full tensorflow-microlite.a library.
The person detection example is more complicated and not fixed here.
Co-authored-by: Michael O'Cleirigh <michael.ocleirigh@gmail.com>
Co-authored-by: Advait Jain <advaitjain@users.noreply.github.com>
I copied the sparkfun-edge action and then adjusted to call the esp32 ci test script.
Changed the job name from cortex_m to esp32.
Inserted the Readme entry at the alphabetically appropriate index.
Signed-off-by: Michael O'Cleirigh <michael.ocleirigh@gmail.com>
Co-authored-by: Michael O'Cleirigh <michael.ocleirigh@gmail.com>
* modify a tflite file in the tflite-micro repository.
* fix the path
* Update workflow logic to complete workflow without error with NO_CHECK_TFLITE_FILES
* revert change to the tflite files.
* fail PRs that overwrite a set of files from upstream
* Change some names, modify Python script logic etc.
* small fixes.
* Use more restrictive TFLM-bot token.
Co-authored-by: Advait Jain <advaitjain@users.noreply.github.com>
Co-authored-by: Advait Jain <advaitjain@google.com>
* check PR description for a BUG= line
* Changed file name and added some more documentation.
* move the if to be on the steo instead of at the job.
This is to allow for the job to succeed (instead of being skipped) when
the BUG= text is found. And as a result we can have it be a required
status check.
Co-authored-by: Advait Jain <advaitjain@users.noreply.github.com>
Co-authored-by: Advait Jain <advaitjain@google.com>
This is required only because some of the third_party_downloads are
still using the Makefile functions and thus require an explicit
`make third_party_downloads`.
Additionally, we sometimes also want to avoid all downloads and this PR
adds in a flag for that as well.
Fixes#119 and the corresponding internal bug http://b/184886633
Related bugs are http://b/143904317 and http://b/183229719
Since we trigger the CI workflow on any label change, when the cla:yes
label is applied the CI workflow will be run, and there is no way around
that with the current setup.
If the sync PR does not have the ci:run label, the checks will be
skipped but will still need to be run again prior to merge since
skipping the checks invalidates the previous completion of the required checks.
As a result, we are keeping the ci:run label. What this means is that
the reviewer can manually apply the cla:yes label and then start
auto-merge (which will wait for another round of the required checks to
be run).
cla:yes can only be applied by someone from Google, so will be done
manually. However, the goal here is to have the PR be ready to merge
once a Google engineer reviews it.
Without the additional step of `git add`, any untracked files will not
be part of the PR that is created with the sync workflow.
Manually tested this change on my fork of tensorflow by removing a file,
pushing it to main and then confirming that the sync workflow does not
add to the PR prior to this change, but does add it to the PR after this
change.
Adding the cla: yes label seems error prone so we are going to stick to
only applying the ci:run label automatically and manually toggle the cla
status.
For some reason the actions dashboard has stopped showing me the name of
the sync workflow. Instead it is showing me the path to the yml file
which is somewhat annoying.
* Added a (presubmit) suffix to all the status checks that shold be
required prior to merging.
* trying out automatically removeing the "cla: no" label for the sync
PRs.
