Torizon Local deployment task failed

Technical Support
, ,
1

Since yesterday, I am not able any more to “build the release or debug container” in Torizon 1.4.0 (VScode).

When I invoke the palette (F1) on vscode Torizon : build release container for the application, it fails with Local deployment task failed. after a few seconds.

Actually, the release container is not even built (there is only 4 seconds between build and deployment, so deployment failed because no image is built).

The work/Dockerfile.release or work/Dockerfile.debug is not even re-generated.

The complete OUTPUT message is :

[03-01 10:21:36.893] Initializing Torizon Extension
[03-01 10:21:36.912] Checking system setup...
[03-01 10:21:36.913] Checking Moses ...
[03-01 10:21:37.035] Starting backend local instance running on port 5001
[03-01 10:21:49.181] Torizon Backend version 1.0.0 API version: 1.1.5
[03-01 10:21:49.183] Torizon IDE backend started
[03-01 10:21:49.184] Checking Docker ...
[03-01 10:21:49.242] Docker version 20.10.13 build 906f57f
[03-01 10:21:49.318] Trying connect to Toradex Apalis iMX8QM V1.1 on Apalis Evaluation Board(06852340)
[03-01 10:21:50.498] Active configuration has been selected 513050ae-f541-4a8a-baef-1599a9e43911, updating it.
[03-01 10:21:50.501] Initializing Torizon C/C++ application.
[03-01 10:21:50.919] SDK-related features are enabled for this project.
[03-01 10:21:50.946] Torizon: Qt5 arm64v8-vivante bullseye - phosddvr - 513050ae-f541-4a8a-baef-1599a9e43911
[03-01 10:21:50.948] Torizon Extension Initialized
[03-01 10:21:50.986] LA_OPT_NXP_Software_License v5 January 2019 EULA accepted
[03-01 10:22:04.622] Toradex Apalis iMX8QM V1.1 on Apalis Evaluation Board(06852340) connected
[03-01 10:22:04.623] Torizon: all devices refreshed
[03-01 10:23:41.395] Preparing debug environment for C/C++ application...
[03-01 10:23:41.396] Your current build configuration is set to release, this may prevent generation of debugging symbols or enable optimization that prevent debugging features like breakpoints, watches or call stack from working or showing correct inforamation.
[03-01 10:23:41.403] Running preLaunchTask build_release...
[03-01 10:24:00.544] preLaunchTask completed.
[03-01 10:24:05.383] Local deployment task failed.
[03-01 10:24:21.267] Building release container for C/C++ application...
[03-01 10:24:25.971] Local deployment task failed.

Note that I did a deep rechecking before writing this message :

  • the SDK container builds and run correctly, and my application compiles nicely.
  • the target device (apalis-iMX8) is working nice and can be accessed.
  • I even erased all my Docker images and reflashed the SoC to start from scratch again.

But still it does not work (but it used to work before yesterday!).

I cannot find any useful information in the logs. But I am not quite sure what log I should look to.

Could you give me some hints to find more relevant output messages in order to debug this issue ?

Best regards,
Fabian

2

Greetings @fdortu,

This is certainly a strange sounding issue. So everything in your project was working fine up till recently?

First of all, did you do any changes to your project that may have caused this sudden issue?

Also as a sanity check does the issue happen if you create a fresh new project and attempt the same there?

Finally, in case we need to try and debug/reproduce this on our side. What is your steps for reproducing? From your logs it looks like you have a C/C++ Qt based project is that correct?

So I imagine the steps would be:

  • Create new C/C++ Qt project (What type of Qt project? QML/QtCore/Widgets)
  • Then try to run Torizon : build release container for the application

Is that it? Or are you doing anything else special in your project?

Best Regards,
Jeremias

3

Dear Jeremias,

I finally reimported my project from scratch (qmake) using the most recent version of Torizon (early access 1.5.200) which made me understand what was the issue, by comparing the newly generated tasks.json with my older one : I renamed the task labelled deploy with another name so that Torizon could not find the task any more. Sorry for the noise generated by this post !

Anyway, an error message could have been generated. Is there a log file where this error is reported ?

I also noticed that that TORIZON_PROP_ARG env variable in tasks.json, got erased but then reappeared later. It is not clear when the change is made and what it is useful for ?

"options": {
        "env": {
            "TORIZON_PROP_ARG": "ARG SSHUSERNAME=#%application.username%#\n"
        }

Regards,
Fabian

4

Ahh glad to see the issue was just a minor thing.

Anyway, an error message could have been generated. Is there a log file where this error is reported ?

I believe if you go to the extension settings there is an option to turn on additional backend debugging. This should produce more debug messages, not sure if they’d be more descriptive though.

There’s also another option, to specify a path for the log file. I don’t believe this enables additional logging. But it will write all current logging to the path specified.

I also noticed that that TORIZON_PROP_ARG env variable in tasks.json , got erased but then reappeared later. It is not clear when the change is made and what it is useful for ?

This is just setting an environment variable inside the container. Users can set their own environment variables as well, but the extension uses TORIZON_PROP_ARG for this purpose as to not conflict with user set variables.

Best Regards,
Jeremias