-
-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ceedling Upgrade from 0.31.1 to 1.0.1 #1024
Comments
Hi @minne2021 -- it'd be helpful to see the full error. Can you rerun ceedling with
|
Thank you @mvandervoord. I use docker image in my CICD pipeline configuration file (.gitlab-ci.yml). The Ceedling was installed in this docker image container. I ran "ceedling test:all --verbosity debug" in .gitlab-ci.yml. file and got a very long log. Here is part of the log with more information about the error:
|
@mvandervoord -- I closed the issue accidentally yesterday and tried to reopen later. I am not sure if this issue is still on your list. Just double check. More details have been provided in this issue. Thank you very much!
|
Hi @minne2021 -- thanks for checking in! I |
I run "ceedling test:all" with the Ceedling example project (temp_sensor) and got the same issue after I enabled report_build_warnings_log plugin from project.yml. By the way, in this example project, TestUsartIntegrated.c includes "calculators/MockUsartBaudRateRegisterCalculator.h". But this header file is not in calculators directory. I have to remove "calculators/" to make Ceedling continue. |
My existing project uses Ceedling V0.31.1 and works fine. I need to upgrade it to Ceedling V1.0.1.
My issue is on the plugin "warnings_report". It looks like V1.0.1 changes its name to "report_build_warnings_log". I enabled it in my project.yml:
But I got error message when running Ceedling:
🪲 ERROR: Exception raised in plugin report_build_warnings_log within build hook :post_test_preprocess
🧨 EXCEPTION: undefined method `[]' for nil:NilClass
Are there anything I need to do to fix this issue? Thanks!
The text was updated successfully, but these errors were encountered: