eden
eden copied to clipboard
lf-edge
gha: add neoeden job to test.yml workflow
Instead of adding additional workflow to eden, we run neoeden alongside with older version intent is that end user (EVE CI/CD pipeline) will not require any changes, it will still call test.yml there will be an additional test suite. End goal is to gradually move all the test suites to golang-based tests, so at some point smoke tests will be running in neoeden, or networking tests, etc. etc.
@uncleDecart but do we really need this workflow? I thought that golang tests are just compiled and run with the rest of Eden tests in the regular test workflow
@andrewd-zededa, I'm using fedge/eve:0.0.0-master-8cf1b2da-kubevirt-amd64 image for kubevirt, is there other image we should use?
We have neoeden? oh man I abandoned my child...
It only became stronger, fear not @shjala
@uncleDecart I'm checking back on this, can you help me understand where it sits now? I don't see the Neoeden run in PR CI runs above, does this need to be merged before gha runs it?
Looks like the Networking test suite failed due to "TOOMANYREQUESTS: You have reached your unauthenticated pull rate limit", are we past that now? Do the /rerun commands work here?
took me a while to get back to it @andrewd-zededa , rebasing now and updating code to increase timer to 30 minutes
Will we see the new workflows only after merge? Or should they be already visible under this PR?
Will we see the new workflows only after merge? Or should they be already visible under this PR?
We will see after the merge (we can check on fork)