-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Add check to travis to make sure new boards are built, fix #1886 #2003
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
…ds based on board_info and TRAVIS_BOARDS
Output of the script:
|
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.
Looks good! In addition to the change marked, could you go ahead and add the command to run the script to .travis.yml
so we can see how Travis treats it?
Done, let me know if i did something wrong :) |
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.
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'd say the placement is good in the Travis. That's my opinion though, and easily overruled. 😄
Found one last thing, and then I'll approve. I won't merge though, as I'd like @tannewt to weigh in on it, and I have an open question:
- Are there any boards that actually should be ignored? Like say
trinket_m0_haxpress
?
About the boards to ignore, i think we can make a list of boards to ignore and remove them from the I will be away from the keyboard for a couple of days, can you do the lasts fixes? |
I should be able to handle it. Just a matter of git cooperating. 😄 |
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.
Thank you for doing this!
I think we should either add the boards to travis if we want to keep them on the downloads page or delete the board def if they aren't worth it. I'd choose to just add them for now. We'll need to speed up the build regardless of whether we build these four extra boards.
Also, did someone manually stop the last test job? I'd hope that the rest of the build continues if this test fails. It's important to find as many failures in a single build since they take so long.
Hi, there's a |
That's on me. I recommended that this be placed in the |
@sommersoft failing fast is interesting actually! That makes sense since it'll have to be run anyway. @C47D We definitely do want to fail. It's just a question of when. I'd suggest adding the sys.exit back and adding the missing boards to .travis.yml so the build passes. Thank you both! |
@tannewt I've fixed both requests, I added all the missing TRAVIS_BOARDS to travis.yml |
I think the only board that isn't properly building is
|
Adding another means a build would be 6 concurrent jobs and make two not fit side by side in the 10 total we have.
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 tweaked a couple small things to get it to build and then this should be ready. Thank you so much!
Make it match feather_m0_express
@sommersoft @tannewt np, always happy to help and learn new things :) |
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.
This will definitely be a useful check! Thanks again @C47D.
Still a draft and my python isn't perfect so let me know if I'm doing something silly.
TODO:
TRAVIS_BOARDS
on the.travis.yml
file.EDIT:
Now i have two lists with the boards names got from board_info and TRAVIS_BOARDS: