Closed thc202 closed 3 years ago
Browser tests are failing for some reason (they are passing locally).
Amend and push again?
Just checked (in a private repo) with the main
branch and it has the same problem. Will continue investigating...
Is checkout@v2 really usually the original v2 and not one of the newer versions that falls back to default branch? (Checking out master not main?) I haven’t read through the logs, sorry if it’s obvious.
Generally it should checkout the one that's being acted upon. (This repo no longer has the master
branch.)
Agreed I just wondered if 2.0 had it hard coded because fallback wasn’t added till 2.3 or something like that.
Okay I finally read the log, I guess it isn’t checkout. The code is there and it is UnitTests which are failing.
Right, that's what I tried to say with https://github.com/zaproxy/zest/pull/227#issuecomment-822376525
This is now passing again (no changes...).
I'm fine with it being merged. It could have been something timing or infrastructure related.
Done :)
Build passed in main
branch.
Update Gradle Wrapper and build to 7.0. Update Spotless to 5.12.1. Migrate CI tweaks to GitHub, missed in #224.