Skip to content

LPC MCUXpresso: fix write_fill argument for block write function #4807

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
Jul 25, 2017

Conversation

0xc0170
Copy link
Contributor

@0xc0170 0xc0170 commented Jul 25, 2017

The latest HAL extension was not applied to the LPC MCUXpresso targets.

Tested build for both broken targets (same HAL implementation used).

The latest HAL extension was not applied to the LPC MCUXpresso targets.
@0xc0170
Copy link
Contributor Author

0xc0170 commented Jul 25, 2017

/morph test

@0xc0170
Copy link
Contributor Author

0xc0170 commented Jul 25, 2017

This is broken currently on master, so needs to get in asap, and unblocks other CI jobs.

@mbed-bot
Copy link

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 882

Example Build failed!

@0xc0170
Copy link
Contributor Author

0xc0170 commented Jul 25, 2017

Example build error not related, @studavekar the machine that did this job has proper IAR installed?

/morph test

@mbed-bot
Copy link

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 883

All builds and test passed!

@0xc0170
Copy link
Contributor Author

0xc0170 commented Jul 25, 2017

@tommikas how long it takes for jenkins to run a job, it seems to be 2 hours?

@0xc0170 0xc0170 merged commit 9207365 into ARMmbed:master Jul 25, 2017
@0xc0170 0xc0170 deleted the fix_lpc_write_fill branch July 25, 2017 14:53
@tommikas
Copy link
Contributor

There was a bit of trouble with the build yesterday due to a Jenkins slave image update that happened while nodes were already online. It caused two concurrent executors of a type there should only have been one.

I made sure to restart this job first when I got it sorted out but there were a few builds already in the queue at the time. Sorry for the inconvenience.

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.

3 participants