I believe that the unable to access file: corrupted zip file indicates some transient failure in GCP? I remember seeing it in the past, but I don't think we ever got to the bottom of it.
To respond to your other email, yeah, I think bumping your PR to re-fire might be the best way to proceed? As it stands, since the build failed, none of the JDK11 tests would've run, which mildly worries me, even if the build failure is understood. We could look into separating the build and test tasks in Concourse, so that the build step would retry on these failures. I'm not sure if it would end up caching things in a way that would cause us to not actually ameliorate the issue, though. tl;dr: I think you just rolled snake-eyes. Imagination is Change. ~Patrick On Mon, Nov 26, 2018 at 12:20 PM Kirk Lund <kl...@apache.org> wrote: > Just the first few compilation failures are listed below. Is the image > for AcceptanceTestOpenJDK11 precheckin broken in some way? > > > /home/geode/geode/geode-core/src/main/java/org/apache/geode/internal/InternalInstantiator.java:20: > error: cannot access Constructor > import java.lang.reflect.Constructor; > ^ > bad class file: > > /usr/lib/jvm/java-8-openjdk-amd64/lib/ct.sym(META-INF/sym/rt.jar/java/lang/reflect/Constructor.class) > unable to access file: corrupted zip file > Please remove or make sure it appears in the correct subdirectory of > the classpath. > > /home/geode/geode/geode-core/src/main/java/org/apache/geode/internal/cache/LocalRegion.java:18: > error: cannot find symbol > import static > > org.apache.geode.internal.offheap.annotations.OffHeapIdentifier.ENTRY_EVENT_NEW_VALUE; > ^ > symbol: static ENTRY_EVENT_NEW_VALUE > location: class > > /home/geode/geode/geode-core/src/main/java/org/apache/geode/internal/cache/LocalRegion.java:17: > error: cannot find symbol > import static org.apache.geode.internal.lang.SystemUtils.getLineSeparator; > ^ > symbol: static getLineSeparator > location: class >
