CI Exporters: failing uvision5

[0xc0170]

Description

One of the jobs that recently failed, different targets, same toolchain (uvision5):
http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/8072/ . From this report is obvious it started building but failed somewhere. From CI logs, there is a traceback, more investigation needed. Please review the exporters log.

@ARMmbed/mbed-os-maintainers @ARMmbed/mbed-os-test

Issue request type

[ ] Question
[ ] Enhancement
[x] Bug

[0xc0170]

This is from CI

10:33:45 Traceback (most recent call last):
10:33:45   File "../mbed-os/tools/test/examples/examples.py", line 133, in <module>
10:33:45     sys.exit(main())
10:33:45   File "../mbed-os/tools/test/examples/examples.py", line 84, in main
10:33:45     return args.fn(args, config, examples)
10:33:45   File "../mbed-os/tools/test/examples/examples.py", line 90, in do_export
10:33:45     results = lib.export_repos(config, args.ide, args.mcu, examples)
10:33:45   File "C:\builds\ws\exporter-build-matrix\2802\DISCO_L475VG_IOT01A_uvision5\sources\mbed-os\tools\test\examples\examples_lib.py", line 297, in export_repos
10:33:45     if EXPORTERS[ide].build(example_project_name, cleanup=False):
10:33:45   File "C:\builds\ws\exporter-build-matrix\2802\DISCO_L475VG_IOT01A_uvision5\sources\mbed-os\tools\export\uvision\__init__.py", line 294, in build
10:33:45     with open(log_name, 'r') as f:
10:33:45 IOError: [Errno 2] No such file or directory: 'build_log.txt'

@OPpuolitaival @studavekar @theotherjimmy Any suggestions?

I can't reproduce this locally (using the same example_lib command I get 9 errors). I suspect this might be due to cmsis pack, so checking uvision5 export:

mbed export -m DISCO_L475VG_IOT01A -i uvision5 , using uvision 5.24 - it requests device pack that I have installed. Once I install, still complains that L475VG is not available anyway and I am in the circle - I selected one of L475VGx targets, the local blinky compiles then. Did cmsis pack change ? I tried uninstall L4 cmsis pack , did not help.

@ARMmbed/team-st-mcd Are you able to export for this target for uvision5?

[0xc0170]

Looking at this closer - STM32L4xx DFP 2.0.0 is requested for me locally and does not fit the target definiiton in case for L475. Looking at other failures, all failures we have now in CI are related to this DFP. Did something corrupt since the update - cmsis pack was updated yesterday

I suspect this is related to cmsis pack and exporters now fails due to it. Although not all L4 are affected so why we can see some are failing, some not?

@miklis

[0xc0170]

@ARMmbed/mbed-os-test Need to review this one ticket IOTTESTINF-3857

[0xc0170]

I have this locally

Still uvision 5.24 complains if I export DISCO_L475VG_IOT01A - cant set the target. The cmsis pack date is really old, what did break here?

[bcostm]

@ARMmbed/team-st-mcd Are you able to export for this target for uvision5?

Yes it works for me. I have the same L4 pack version as you.

[0xc0170]

Are you able to build the blinky project? From the targets taht fail in our exporters CI, they are showing the same errors when I export and open in uvision 5.24. Restarting entire machine just in case

When I build using example_lib.py script (to export and build blinky), I get 9 errors - one of them indicate that cmsis pack is missing:

startup_stm32l475xx.S: Error:  #5: cannot open source input file "__UVISION_VERSION SETA 524": No such file or directory

startup_stm32l475xx.S: __UVISION_VERSION SETA 524: 0 warnings, 1 error

[0xc0170]

Attaching uvision build log, using python -u ./mbed-os/tools/test/examples/examples.py export uvision5 --mcu DISCO_L475VG_IOT01A command (having mbed-os latest master, plus blinky in the same folder , from this folder run this script):

build_log.txt

[bcostm]

I have the same "Device not found" error when the project is loaded. I have selected the STM32L475VGTx in the Options>Device tab and the build was OK.

But I don't have the "__UVISION_VERSION SETA 524" error ? I use uvision V5.24.2.0.

[0xc0170]

I have the same "Device not found" error when the project is loaded. I have selected the STM32L475VGTx in the Options>Device tab and the build was OK.

If I fix the MCU, build is OK. If I don't I get that error .this is however locally , still does not fully explain what is going on with L4 targets in export and why they started failing. PR 8301 shows that process fails and returns windows error.