That test sounds like one that fails randomly in CI regardless of which CI
service is used. Makes me wonder where the bug is coming from (test or
library code).
On Tue, Aug 25, 2020 at 06:30 Volkan Yazıcı wrote:
> Problem has been solved after upgrading the Maven wrapper. Now GitHub
>
> Actions
Problem has been solved after upgrading the Maven wrapper. Now GitHub
Actions can issue a successful "./mvnw verify" for both master and
release-2.x branches! 🥳 🎉
Even though "verify" succeeds, for some reason test reports still point to
certain errors. See the latest successful builds on master
<
On a related note, I've figured out how to (safely) enable Jenkins for
PR builds now that infra added a GitHub App token. It'll build for
collaborators which includes previous contributors and some other
people that aren't necessarily committers here. If this option works
out well enough, we may be
My mistake; the problems in master appear to be related to test
failures of some sort. I'll see if migrating those tests to JUnit 5
(along with any related refactorings) helps make them less flakey.
On Sat, 22 Aug 2020 at 21:04, Matt Sicker wrote:
>
> Ok, so whatever the issue is is a problem in
Ok, so whatever the issue is is a problem in both branches now.
On Fri, 21 Aug 2020 at 09:56, Matt Sicker wrote:
>
> I’ve been modifying build settings in master lately that haven’t been merged
> back to this branch. I’d assume there’s a difference in the pom file here.
> I’ll take a closer loo
I’ve been modifying build settings in master lately that haven’t been
merged back to this branch. I’d assume there’s a difference in the pom file
here. I’ll take a closer look later today.
On Fri, Aug 21, 2020 at 04:31 Volkan Yazıcı wrote:
> GitHub Actions CI build is failing on release-2.x
>
>
