-
Notifications
You must be signed in to change notification settings - Fork 1
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
Attempt to fix CI test failure, plus bump to go v1.21 #1
base: feature/gomod
Are you sure you want to change the base?
Conversation
I see the same error as wave-k8s#107 (comment) in my local tests. I have created a branch in the main repo to run the workflow: https://github.com/wave-k8s/wave/actions/runs/8472508441/job/23214757845?pr=146 so that everyone has the same starting point. Perhaps for debugging, you can create your own PR that combines your fixes on top of wave-k8s#107 for fast iteration? We can then clean up the mess when we are done… Also, it turns out that |
I think @Dentrax tried to to that here: |
At least the error in the test failure is different there. |
Thanks for your comments, @toelke! Yeah if we figure out the error I got there:
I would be great so that we can move forward here. I spent another a few hours to fix that specific error, but no luck. I don't know if its a refactor issue or something is "really" wrong with testing strategies. Do you see anything? |
Well, If we could get the end2end tests working that would be a great first step. That means that The error you quote makes me think that there is some breaking change in some library since the version from 2016. That was why I hoped (in vain, it seems) that it would be possible to do the "dep -> go mod" without updating anything... |
I have also tried to do that but no luck. Do you have any thoughts/ideas/workarounds/hint about how to do that? There are some attempts on upstream repo but it seems nobody have any luck (Including me :D) here: https://github.com/wave-k8s/wave/pulls |
I think that your current solutions are all pointing the right way. There appears to be some incompatibility with some remaining old code? I unfortunately did not have an opportunity to really dig into the different error messages of your branch(es). My course of action would be:
|
Attempt to fix CI test failure:
Also bumped go to v1.21