-
Notifications
You must be signed in to change notification settings - Fork 68
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
Regressions in integration tests since the 20.10 upgrade #309
Comments
@lmbarros Want to divide and conquer? Can one of us start from the bottom and one start from the top or do they need to be run sequentially? |
These tests are passing in Moby, might be worth checking out, or talk about best ways to sync their fixes. |
Hi @zoobot ! Yup, as far as I know these tests have always passed on Moby. They started failing after we merged 20.10 from Moby into balenaEngine (on this PR -- my links on the issue description were wrong, I corrected it now.) I cannot look at this right now, need to finish other stuff first. (But feel free, of course!) |
Internal balena link with some notes about this I wrote some months back. Summary: some of the failures are because our fork is using Buildkit (unlike upstream at the corresponding point in time). Buildkit and non-buildkit error messages are different, so some tests fail because they are expecting to fail with a different error message. |
Several of "CLI integration tests" are failing since we upgraded to 20.10 (this PR
this PR, and specifically this commit).We must investigate and fix these failures. I looked at just a few of them, which are related with building images and seem like legit issues we should look into.
Here's a list of failures I get on my laptop when running
TIMEOUT=240m make TEST_INTEGRATION_DIR=./integration-cli/ test-integration
:The text was updated successfully, but these errors were encountered: