Skip to content
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

tests/emb6: msb-430 insufficient memory #6482

Merged
merged 1 commit into from
Jan 26, 2017

Conversation

cgundogan
Copy link
Member

According to Jenkins, the msb-430 has not enough memory for the emb6 test. So linking needs to be ignored. I wonder why Murdock is not linking this board, although it is not listed here in BOARD_INSUFFICIENT_MEMORY @kaspar030 ? Is the buildtest target using wildcards, so that msb-430 is matching msb-430h?

@cgundogan cgundogan added Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation Area: build system Area: Build system CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR labels Jan 26, 2017
@cgundogan cgundogan added this to the Release 2017.01 milestone Jan 26, 2017
@cgundogan
Copy link
Member Author

Is the buildtest target using wildcards, so that msb-430 is matching msb-430h?

Yep, see #6483 for an explanation.

Copy link
Member

@miri64 miri64 left a comment

Choose a reason for hiding this comment

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

ACK

@miri64 miri64 merged commit 7cb379c into RIOT-OS:master Jan 26, 2017
@cgundogan cgundogan deleted the pr/emb6_msb430h_no_linking branch January 26, 2017 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: build system Area: Build system CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants