Has anyone mentioned that to Infra? I certainly can, but I do not want to
be repeating what someone else already said

a

Andrew Wetmore
Assistant VP, Marketing and Publicity, The ASF <https://apache.org>
Editor-Writer, Infra team, The ASF

Editor, moosehousepress.com


<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Nov 18, 2026 at 1:26 PM Josh Tynjala via dev <[email protected]>
wrote:

> I noticed that our CI build started failing again. However, the log says
> it's because the machine is running out of disk space. Presumably, Infra
> would need to fix that.
>
> --
> Josh Tynjala
> Bowler Hat LLC
> https://bowlerhat.dev/
>
>
> On Thu, Nov 12, 2026 at 1:52 PM Josh Tynjala <[email protected]>
> wrote:
>
> > It turned out there was a version mismatch in our develop branches, but
> > not exactly in the way that I originally assumed.
> >
> > Currently, the develop branches of royale-compiler and royale-asjs have
> > different version numbers (1.0.2-SNAPSHOT and 1.0.1-SNAPSHOT).
> Technically,
> > that needs to be corrected (probably all to 1.1.0-SNAPSHOT instead).
> > However, it shouldn't actually be affecting whether the build succeeds or
> > not.
> >
> > royale-asjs overrides something from royale-compiler. It was referencing
> > the royale-compiler version as part of this override, but it should have
> > been referencing the royale-asjs version instead because that's where the
> > overriding artifact comes from. I've corrected that on the develop
> branch,
> > and the newest build of royale-asjs succeeded!
> >
> > To be clear, this doesn't affect the current release in any way. It's
> just
> > when version numbers don't match, which would never happen in a release.
> >
> > There's one other thing that we need to do in pom.xml on royale-asjs's
> > develop branch (but it can wait until after the release):
> >
> >
> >
> <project.royale.compiler.version>1.0.0-SNAPSHOT</project.royale.compiler.version>
> > <royale.typedefs.version>1.0.0-SNAPSHOT</royale.typedefs.version>
> >
> > The version numbers on the above lines in royale-asjs/pom.xml need to be
> > updated too. These are custom properties, so Maven won't update them
> > automatically like it does with other version numbers when it increments
> > for a new version.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC
> > https://bowlerhat.dev/
> >
> >
> > On Thu, Nov 12, 2026 at 10:00 AM Josh Tynjala <[email protected]
> >
> > wrote:
> >
> >> When we create a release branch, the Maven build in the develop branch
> >> usually ends up in a bad state until it gets manually cleaned up. I
> think
> >> the build server is trying run Maven on the develop branch once per day,
> >> and it fails because it hasn't been cleaned up yet.
> >>
> >> As I recall, the version number in some (but not all) of our pom.xml
> >> files doesn't get updated automatically, causing a mismatch that
> triggers
> >> the failure.
> >>
> >> --
> >> Josh Tynjala
> >> Bowler Hat LLC
> >> https://bowlerhat.dev/
> >>
> >>
> >> On Thu, Nov 12, 2026 at 9:34 AM Andrew Wetmore <[email protected]>
> >> wrote:
> >>
> >>> The Infra build servers are at 95% capacity, and Royale is on the list
> >>> of high-volume users:
> >>>
> >>> [image: image.png]
> >>>
> >>> I see repeated 'build failed!' messages and have been presuming those
> >>> are related to different builds related to a variety of work, but am I
> >>> wrong? Is this a run that keeps failing and then repeating?
> >>>
> >>> There is a bunch of advice to help projects cut down on their resource
> >>> use. Have you guys been following those threads?
> >>>
> >>> a
> >>>
> >>>
> >>> Andrew Wetmore
> >>> Assistant VP, Marketing and Publicity, The ASF <https://apache.org>
> >>> Editor-Writer, Infra team, The ASF
> >>>
> >>> Editor, moosehousepress.com
> >>>
> >>>
> >>> <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> >
> >>> Virus-free.www.avast.com
> >>> <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> >
> >>>
> <#m_7966056893547099594_m_-4292538015630170750_m_8288543755168220561_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >>>
> >>
>

Reply via email to