Hey Clay, Thanks for the insights. You are right the S3 cache is not functional at the moment and there is CALCITE-5034[1] to remove/replace it.
Best, Stamatis [1] https://issues.apache.org/jira/browse/CALCITE-5034 On Wed, Jul 31, 2024 at 9:56 PM Clay Johnson <[email protected]> wrote: > > Hi Calcite folks, I am a Solutions Engineer at Gradle working on build > optimization and the rollout of Build Scans to ge.apache.org within the > Apache Software Foundation. > > I have a question regarding the usage of the S3 Build Cache, defined here > <https://github.com/apache/calcite/blob/main/settings.gradle.kts#L134>. Is > this cache currently functional? I see some data points that make me think > it is not: > > - This graph > > <https://ge.apache.org/scans/performance?performance.metric=avoidanceSavings,avoidanceSavingsRemoteBuildCache&search.query=project:calcite&search.relativeStartTime=P90D&search.timeZoneId=America%2FChicago> > shows that Calcite CI builds have not saved any time from the remote cache > over the last 90 days: > - This graph > > <https://ge.apache.org/scans/trends?search.query=project:calcite%20gradle.buildCache.hasError&search.relativeStartTime=P90D&search.timeZoneId=America%2FChicago> > shows that ~552 Calcite builds have had cache errors in the last 90 days: > - Looking at the details, most seem to indicate that the S3 bucket was > not found, like in this build > > <https://ge.apache.org/s/chsz2emskhndk/performance/build-cache#remote-cache-failure-0-0> > > This makes me wonder if Calcite builds are losing time by trying the S3 > build cache, not to mention that the "Seed build cache" job is spending CI > compute resources attempting to seed a cache it cannot access (15.5 hours > over the last 90 days, according to this graph > <https://ge.apache.org/scans/trends?search.names=CI%20workflow&search.rootProjectNames=calcite&search.timeZoneId=America%2FChicago&search.values=Seed%20build%20cache> > ). > > Is this remote cache configuration something that can just be removed? Or > can it be repaired? > > An alternative may be to use the cache provided by ge.apache.org. It is not > available today, but should be available over the next few months. > > Thanks, > > Clay Johnson > Lead Solutions Engineer > Gradle > W. gradle.com > > -- > * > CONFIDENTIALITY NOTICE*: The contents of this email message, and any > attachments, are intended solely for the addressee(s) and may contain > confidential, proprietary and/or privileged information legally protected > from disclosure. If you are not the intended recipient of this > communication, or if you received this communication by mistake, please > notify the sender immediately and delete this message and any attachments. > If you are not the intended recipient, you are hereby notified that any > use, retransmission, dissemination, copying or storage of this message or > its attachments is strictly prohibited.
