-
-
Notifications
You must be signed in to change notification settings - Fork 19.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
Tests for Color UI and Robin Nano Boards (and fixes) #19118
Tests for Color UI and Robin Nano Boards (and fixes) #19118
Conversation
@ivankravets seems pio dev is broken....
Take a look in the failing tests. |
This is a legacy Core 3.x API. Please use |
Should revert back this 3.x API and add warning? We just wanted to clean up a code. |
Is not our scripts. Is the esp32 framework package
Seems there’re packages that use some legacy code, and they aren’t migrated yet. |
Sorry for these issues. We don't do a major refactoring of our codebase so often. 1 time per a few years. This time it has happened with refactoring our package management infrastructure. Maybe, it makes sense to release it as PIO Core 5.0. However, we don't see a reason in PIO Core 5.0 if all user projects are compatible with PIO Core 4.4 changes. @rhapsodyv thanks for your report. It is an outdated version of ESP32 dev platform. I've just back ported @thinkyhead "PIO-dev unsuitable for CI", why it is unsuitable? Is it better if we fix all known issues before the final releases of both projects? How about if we switch back to "develop" branch after PIO Core 4.4 release? We plan to have it on Tuesday. We don't have any significant changes in PIO Core in our roadmap for the next months. Thanks! |
@thinkyhead we need release 2.0.6.1 with #19034 before Tuesday. If we don't, any build using the upcoming pio will be broken. 🙁 |
Do you have any blockers for 2.0.6.1? Indeed, we can wait in this case. |
@ivankravets I think we have more issues:
|
|
@rhapsodyv thanks for the report! Fixed in platformio/platformio-core@24f85a3 P.S: It was a typo with excluding "no-member" from PyLint. |
F23:09, 23 августа 2020 г., Ivan Kravets <[email protected]>:
@rhapsodyv thanks for the report! Fixed in platformio/platformio-core@24f85a3
P.S: It was a typo with excluding "no-member" from PyLint.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.
egor
|
23:09, 23 августа 2020 г., Ivan Kravets <[email protected]>:
@rhapsodyv thanks for the report! Fixed in platformio/platformio-core@24f85a3
P.S: It was a typo with excluding "no-member" from PyLint.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.
egor
|
I find it frustrating to have to stop at random times to deal with a morphing PlatformIO when there are so many notifications and pull requests piling up. To avoid these interruptions I would prefer to stick with a known working version of PlatformIO until the kinks are worked out. If the build of Marlin is helpful for catching errors in PlatformIO, perhaps we can set up a copy of Marlin under a different GitHub account, have it re-build itself each time there's a new push to PlatformIO, and then have it ping you if there's a build failure of any kind.
Before tagging 2.0.6.1 I had hoped to find and fix:
But so far I haven't been able to narrow down the cause of either of these issues. |
@thinkyhead thanks for the honest feedback! I think I asked to switch to PIO dev-version at the wrong moment. However, you are right. You have tons of own issues and it does not make sense to spent time on our issues. So, should we postpone 4.4 release? We want to do this tomorrow becase there huge update of PlatformIO IDE 2.0 for VSCode. It depends on PlatformIO Core 4.4. It might be useful for Marlin project as well. It bring support for custom targets and IDE automatically provides UI for them. |
I don't want anything to hold up your schedule, and Marlin needs to be adaptable. If you feel confident you've got all the breaking issued solved, I defer to your judgment. I've been using the 4.4 alpha / beta for a while and the most important thing is that it builds the project just fine and we don't need to make any changes to
That's good news! I look forward to seeing it in action. I believe that, now, if an environment uses |
This also has been fixed. We rewrote INI parser in Node.JS. |
@thinkyhead @ivankravets CI using PIO dev is broken again. 🥳 😅
Maybe @p3p need to do some adjustment? |
No idea, I will need to look up all the major changes that required the platformio major version bump and make sure every thing is compatible before doing a release with the platformio version requirement updated. If the only breaking changes are the manifest file deprecation then it will be an easy update, I will just have to get used to publishing packages ^^. |
@ivankravets Is there any way to lock users in a specific pio version? |
We have decided to release everything under 5.0. A lot of changes... So, it should close any questions about why we modified our internal package structure, and etc. In any case, all projects and dev-platforms are compatible between 1.0 and 5.0. 5.0.0-beta.2 is out. I hope this is the last issue. We know automatically mark all PIO Core 1.0-4.0 dev-platforms compatible with 5.0. See platformio/platformio-core@0db39cc P.S: Thanks for pinging to me! |
Description
Some recent menu changes broke the compilation for New Color UI. I noted that it have no tests.
Benefits
Add test for new color ui.
Related Issues