-
Notifications
You must be signed in to change notification settings - Fork 3k
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
REALTEK_RTL8195AM binary timestamp #9658
Conversation
@alekla01, thank you for your changes. |
@alekla01, thank you for your changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems fine to me
Looks ok to me. If you can squash three commits into one, that will be easier to track. |
What is this ? I can't read it.. |
@alekla01 Doesn't this run the risk of not running tests when they need to? |
CI started |
Test run: SUCCESSSummary: 12 of 12 test jobs passed |
MBEDOSTEST-458
Description
what: REALTEK_RTL8195AM test binary hash depends on build timestamp.
reason: https://github.com/ARMmbed/mbed-os/blob/master/tools/targets/REALTEK_RTL8195AM.py#L150
why does this matter: CI greentea-test skips binaries which have already passed. REALTEK_RTL8195AM test binary hashes are always different, which means CI cannot identify which binaries have already passed and which have not, thus all binaries for REALTEK_RTL8195AM are tested for (almost) every pull request for no reason.
solution: Keep binary hashes the same if dependencies have not been modified. Either remove the timestamp or enable timestamp redefining.
Pull request type
Reviewers
@ARMmbed/team-realtek