Open lue97 opened 3 years ago
Just a tip: Look at the commits page of the PR to identify at which commit the CI started failing first. Hopefully, that commit has a smaller diff compared to the full diff of the PR. The cause of the problems is likely to be within the code you changed in that commit.
I think it is a good idea to commit codes every once in a while. This is to make sure you can easily track which part of code is wrong since if a code works in commit #n and fails at #(n+1), then it is very likely that the one failing it is whatever you are writing between those 2 commits. Hence, the lower the number of lines between those transitions, the easier you can find the impostor code :)
Usually, NoClassDefFoundError means that the class exists compile time, but not runtime. Do you add things manually by chance? Also, a little bit unrelated, but CI can somehow randomly fails because of server failure. You can try to re run all jobs, maybe it helps. Good luck :D
Usually, NoClassDefFoundError means that the class exists compile time, but not runtime. Do you add things manually by chance? Also, a little bit unrelated, but CI can somehow randomly fails because of server failure. You can try to re run all jobs, maybe it helps. Good luck :D
I've conducted tests on both Windows and Linux locally and both passes with no issues. It however happens when I push it to Github.
Did anyone encounter the same issue? This is the PR I'm referring to.