Skip to content

Update mbed_mem_tracing config option #8487

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

Merged
merged 1 commit into from
Oct 29, 2018

Conversation

kegilbert
Copy link
Contributor

Description

This reverts most of commit 9b53d12

#8106 taught me that I can use a default value of null to have the config macro be not defined in mbed_config.h. Reverting my old changes that moved all of the mbed_mem_tracing option checks from #if !defined(....) to #if ... which caused minor breaking changes.

Move the memory tracing enabled macro to a config option but revert the !defined -> #if changes to no longer cause breaking changes as #7402 did.

Pull request type

[ ] Fix
[X] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

@kegilbert kegilbert requested a review from cmonr October 19, 2018 21:06
@cmonr cmonr requested a review from c1728p9 October 19, 2018 22:33
"error-filename-capture-enabled": {
"help": "Enables capture of filename and line number as part of error context capture, this works only for debug and develop builds. On release builds, filename capture is always disabled",
"value": false
},

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This spacing fix should be a separate commit

@0xc0170
Copy link
Contributor

0xc0170 commented Oct 23, 2018

#8106 taught me that I can use a default value of null to have the config macro be not defined in mbed_config.h. Reverting my old changes that moved all of the mbed_mem_tracing option checks from #if !defined(....) to #if ... which caused minor breaking changes.

As you learned the lesson about #ifdef vs #if and config options, is this documented anywhere ?

@kegilbert
Copy link
Contributor Author

@0xc0170 Good point, we do have some tickets for improving the config systems docs for 5.11 that we're working on.

@kegilbert kegilbert force-pushed the mbed_mem_trace_config_patch2 branch 4 times, most recently from d5d5358 to 0f661fb Compare October 24, 2018 14:44
@cmonr
Copy link
Contributor

cmonr commented Oct 25, 2018

So if we're revering a breaking change, does that make this a breaking change?

@kegilbert
Copy link
Contributor Author

@cmonr This is not a full revert of the last change. The breaking change from before was having a macro defined would cause a warning. If someone is using the old PR (say 5.10.2) and they updated to this they should see no issue as they'd have already moved to using the config system. If a user is still using the old macro define (<5.9) this will work as expected too.

@kegilbert kegilbert force-pushed the mbed_mem_trace_config_patch2 branch from 0f661fb to d8782c0 Compare October 26, 2018 14:00
@kegilbert
Copy link
Contributor Author

Fixed the merge conflict.

@0xc0170 are the whitespace changes alright now?

@0xc0170
Copy link
Contributor

0xc0170 commented Oct 26, 2018

Removing breaking change, as this is not.

@0xc0170
Copy link
Contributor

0xc0170 commented Oct 26, 2018

@0xc0170 are the whitespace changes alright now?

I still see them as part of the commit that does other changes, can you create a new one?

@kegilbert
Copy link
Contributor Author

Ahhh shoot rebase put the spaces back in...one second

@kegilbert kegilbert force-pushed the mbed_mem_trace_config_patch2 branch 2 times, most recently from 33465f8 to 7ecb974 Compare October 26, 2018 22:28
Move the memory tracing enabled macro to a config option but
revert the !defined -> #if changes to no longer cause breaking
changes.
@kegilbert kegilbert force-pushed the mbed_mem_trace_config_patch2 branch from 7ecb974 to a2ac895 Compare October 26, 2018 22:35
@kegilbert
Copy link
Contributor Author

@0xc0170 Updated

@0xc0170 0xc0170 requested a review from a team October 29, 2018 10:16
@0xc0170
Copy link
Contributor

0xc0170 commented Oct 29, 2018

I requested also core team to review (meanwhile we run CI)

/morph build

@mbed-ci
Copy link

mbed-ci commented Oct 29, 2018

Build : FAILURE

Build number : 3490
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/8487/

@0xc0170
Copy link
Contributor

0xc0170 commented Oct 29, 2018

The errors looks unrelated (one example does not fit, another failure is in the example python script)

/morph build

@mbed-ci
Copy link

mbed-ci commented Oct 29, 2018

Build : FAILURE

Build number : 3493
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/8487/

@cmonr
Copy link
Contributor

cmonr commented Oct 29, 2018

Found in the build_wrapper job:

10:18:36 abort: HTTP Error 502: Bad Gateway

/morph build

@cmonr
Copy link
Contributor

cmonr commented Oct 29, 2018

@kegilbert This should probably be fixed:

doxygen doxyfile_options
/builds/ws/mbed-os-pipeline/features/netsocket/emac-drivers/TARGET_Silicon_Labs/sl_emac_config.h:4: warning: multiple use of section label 'License' while adding section, (first occurrence: /builds/ws/mbed-os-pipeline/features/netsocket/emac-drivers/TARGET_Silicon_Labs/sl_emac.h, line 4)
/builds/ws/mbed-os-pipeline/features/netsocket/emac-drivers/TARGET_Silicon_Labs/sl_eth_hw.h:4: warning: multiple use of section label 'License' while adding section, (first occurrence: /builds/ws/mbed-os-pipeline/features/netsocket/emac-drivers/TARGET_Silicon_Labs/sl_emac.h, line 4)
/builds/ws/mbed-os-pipeline/features/netsocket/emac-drivers/TARGET_Silicon_Labs/sl_eth_phy.h:4: warning: multiple use of section label 'License' while adding section, (first occurrence: /builds/ws/mbed-os-pipeline/features/netsocket/emac-drivers/TARGET_Silicon_Labs/sl_emac.h, line 4)
/builds/ws/mbed-os-pipeline/features/netsocket/EthInterface.h:31: warning: @copybrief or @copydoc target 'NetworkInterface::ethInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/MeshInterface.h:30: warning: @copybrief or @copydoc target 'NetworkInterface::meshInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/EthInterface.h:31: warning: @copybrief or @copydoc target 'NetworkInterface::ethInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/EthInterface.h:31: warning: @copybrief or @copydoc target 'NetworkInterface::ethInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/EthInterface.h:31: warning: @copydetails or @copydoc target 'NetworkInterface::ethInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/EthInterface.h:31: warning: @copybrief or @copydoc target 'NetworkInterface::ethInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/EthInterface.h:31: warning: @copybrief or @copydoc target 'NetworkInterface::ethInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/EthInterface.h:31: warning: @copydetails or @copydoc target 'NetworkInterface::ethInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/MeshInterface.h:30: warning: @copybrief or @copydoc target 'NetworkInterface::meshInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/MeshInterface.h:30: warning: @copybrief or @copydoc target 'NetworkInterface::meshInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/MeshInterface.h:30: warning: @copydetails or @copydoc target 'NetworkInterface::meshInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/MeshInterface.h:30: warning: @copybrief or @copydoc target 'NetworkInterface::meshInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/MeshInterface.h:30: warning: @copybrief or @copydoc target 'NetworkInterface::meshInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/MeshInterface.h:30: warning: @copydetails or @copydoc target 'NetworkInterface::meshInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/EthInterface.h:31: warning: @copybrief or @copydoc target 'NetworkInterface::ethInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/EthInterface.h:31: warning: @copybrief or @copydoc target 'NetworkInterface::ethInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/EthInterface.h:31: warning: @copydetails or @copydoc target 'NetworkInterface::ethInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/MeshInterface.h:30: warning: @copybrief or @copydoc target 'NetworkInterface::meshInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/MeshInterface.h:30: warning: @copybrief or @copydoc target 'NetworkInterface::meshInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/MeshInterface.h:30: warning: @copydetails or @copydoc target 'NetworkInterface::meshInterface' not found
/builds/ws/mbed-os-pipeline/features/netsocket/CellularBase.h:108: warning: @copybrief or @copydoc target 'NetworkInterface::cellularBase' not found
/builds/ws/mbed-os-pipeline/features/netsocket/CellularBase.h:108: warning: @copybrief or @copydoc target 'NetworkInterface::cellularBase' not found
/builds/ws/mbed-os-pipeline/features/netsocket/CellularBase.h:108: warning: @copydetails or @copydoc target 'NetworkInterface::cellularBase' not found

Also found in the build_wapper job

@mbed-ci
Copy link

mbed-ci commented Oct 29, 2018

Build : SUCCESS

Build number : 3495
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/8487/

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

@mbed-ci
Copy link

mbed-ci commented Oct 29, 2018

@mbed-ci
Copy link

mbed-ci commented Oct 29, 2018

@cmonr
Copy link
Contributor

cmonr commented Oct 29, 2018

For the occasional historian or lurker, it turns out that #8487 (comment) was allowed into master because the Travis CI version of doxygen is woefully out of date (Dec 2013 was when it was released).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants