19:00:47 <jeffro256[m]> Do y’all ever have the tests inside the CI builds mismatch the tests actually pushed to GitHub ? The functional tests are failing on one of my PRs but if you look at the line numbers of the python files (one of the files I changed in the PR) they don’t match was it pushed to GitHub
19:01:00 <jeffro256[m]> * Do y’all ever have the tests inside the CI builds mismatch the tests actually pushed to GitHub ? The functional tests are failing on one of my PRs but if you look at the line numbers of the python files (one of the files I changed in the PR) they don’t match what was pushed to GitHub
19:01:39 <jeffro256[m]> so my tests look like they’re failing because the test file is slightly different
19:02:10 <jeffro256[m]> Is there a way to completely wipe the environment and restart it ?
19:09:18 <UkoeHB> you can wipe the build directory and recompile everything, that usually fixes mismatched test results I encounter
20:28:30 <jeffro256[m]> How could I do that on GitHub?
20:41:12 <UkoeHB> Oh the problem is entirely on github? Sometimes you can get test success locally and test failure on github if your build tree is messed up locally, that's what I meant (e.g. maybe you can reproduce locally by recompiling).
20:43:16 <selsta> jeffro256[m]: is the correct version locally or on github?
20:43:26 <selsta>  or maybe I misunderstood the question
20:44:58 <jeffro256[m]> It works perfectly fine normally, but the CI tests running on Github appear to be running outdated python functional tests. The Github CI tests error out, but if you check the line numbers, they're all different from what was pushed to Github
20:45:00 <jeffro256[m]> s/normally/locally/
21:18:22 <selsta> jeffro256[m]: did you compare that you are on the same git commit locally and remote?
21:19:23 <selsta> the only other thing I can suggest is to rebase locally