pkg/tensorflow-lite: blacklist esp32 architecture [backport 2020.01]

[aabadie]

Backport of #13140

Contribution description

As proposed in #13133 (comment), this PR blacklists the ESP32 architecture in the tensorflow-lite package.

Testing procedure

• Check that pkg/tensorflow-lite build is forbidden by the build system on esp32 architecture:

BUILD_IN_DOCKER=1 make BOARD=esp32-wroom-32 -C tests/pkg_tensorflow-lite
make: Entering directory '/work/riot/RIOT/tests/pkg_tensorflow-lite'
ESP32_SDK_DIR should be defined as /path/to/esp-idf directory
ESP32_SDK_DIR is set by default to /opt/esp/esp-idf
Some feature requirements are blacklisted: arch_esp32
/work/riot/RIOT/tests/pkg_tensorflow-lite/../../Makefile.include:843: *** You can let the build continue on expected errors by setting CONTINUE_ON_EXPECTED_ERRORS=1 to the command line.  Stop.

Issues/PRs references

This is a workaround for the problem reported in #13133 on ESP32 (details in #13133 (comment))

[gschorcht]

A straightforward solution as tested in the master.

[fjmolinas]

ACK.

[aabadie]

@fjmolinas, it seems that your ACK was dismissed when I force pushed the updated branch (the branch must be up to date with the release branch..., btw why this? )

[fjmolinas]

(the branch must be up to date with the release branch..., btw why this? )

Rebased on the release branch? No idea.

[fjmolinas]

re-ACK

[aabadie]

Rebased on the release branch? No idea.

In fact, each backport PR in the queue must be rebased when another one is merged in the meantime. This is quite annoying.

[kaspar030]

In fact, each backport PR in the queue must be rebased when another one is merged in the meantime. This is quite annoying.

It is, but it ensures that CI tested the actual result of a merge to the current release branch HEAD. Without this, there are merge interaction race conditions.

[aabadie]

It is, but it ensures that CI tested the actual result of a merge to the current release branch HEAD

Agreed, and I'm not against this. It is annoying because there are 3 backport PRs in the queue and Murdock takes 30m to build each PRs including random PRs that target master.

Would it be possible to reorder the priority of backport PRs in the Murdock queue ?

[kaspar030]

Would it be possible to reorder the priority of backport PRs in the Murdock queue ?

Not at the moment.

[aabadie]

Not at the moment.

No problem, but would be a great feature to add to Murdock ;)