FYI I just tried one of them (testScmSnapshot). And I can't repro that
locally either.

-Siyao

On Mon, May 12, 2025 at 11:55 AM Wei-Chiu Chuang <weic...@apache.org> wrote:

> I do suspect its environment related because I couldn't reproduce them
> locally.
>
> On Mon, May 12, 2025 at 11:52 AM Attila Doroszlai <adorosz...@apache.org>
> wrote:
>
> > > Hi it looks like a few recon tests are not stable today.
> >
> > It's not only Recon, few other tests too:
> >
> > org.apache.hadoop.ozone.TestSecureOzoneCluster
> > org.apache.hadoop.ozone.s3.awssdk.v1.TestS3SDKV1
> > org.apache.hadoop.ozone.s3.awssdk.v1.TestS3SDKV1WithRatisStreaming
> > org.apache.hadoop.ozone.s3.awssdk.v2.TestS3SDKV2
> > org.apache.hadoop.ozone.s3.awssdk.v2.TestS3SDKV2WithRatisStreaming
> >
> > It started with an unrelated commit:
> >
> >
> https://github.com/apache/ozone/commit/d92f0ed87e7396665972628463cce3b55daa0626
> >
> > It is also failing on feature branch HDDS-10685, which is 17 commits
> > behind master, 15 commits behind the one that first failed on master.
> >
> > I assume it's due to GitHub environment changes: tests are failing
> > with runner version 20250427.1.0, passing with 20250504.1.0.
> >
> > Which is strange, since 20250427.1.0 is supposed to be a rollback.
> > The same tests were passing with that version last week.
> >
> > -Attila
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
> > For additional commands, e-mail: dev-h...@ozone.apache.org
> >
> >
>

Reply via email to