-
Notifications
You must be signed in to change notification settings - Fork 1.4k
try to group travis jobs more logically #2074
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
Conversation
|
@dhalbert will they still be available for manual build. That is, will the board definitions remain in the repo? |
|
@jerryneedell Yes, I just am not sure there are many physical instances of these in the real world. Do you have some? It's just an idea. |
|
I have a feather_m0_supersized, but I'm fine with it not be part of the build process. As long as I can build it myself. |
|
Also, if you want to stop maintaining it completely, that is OK with me - Jus t so I know to keep what I need to build it locally in the future. |
|
@tannewt the build time for the first subjob went to 1.5 hours after I accepted the |
jepler
left a comment
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.
I semi-manually checked that the list of boards is the same "before" and "after", and didn't spot any differences.
First try: group by category. Ten jobs, which seems like too many, but let's see how long each one takes to run.