Workaround is merged, thanks Zita for the review.
Please note: simply re-running failed checks is not enough, merge
master into your branch.
-Attila
-
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
For additional comma
> Can we comment the failed S3 Recon test for now to make CI green if this is
> the only test failing. Because locally it is passing. We can check it once CI
> is green.
No need to disable tests.
Root cause:
https://github.com/actions/runner-images/issues/12178
Workaround:
https://github.com/a
Can we comment the failed S3 Recon test for now to make CI green if this is the
only test failing. Because locally it is passing. We can check it once CI is
green.
Regards
Devesh
> On 13 May 2025, at 2:13 PM, Sumit Agrawal
> wrote:
>
> FYI,
> Started getting above failure continuously for R
FYI,
Started getting above failure continuously for Recon.
TestS3** as above is coming randomly in my run.
On Tue, May 13, 2025 at 1:13 AM Siyao Meng wrote:
> 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 A
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 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
> wrot
I do suspect its environment related because I couldn't reproduce them
locally.
On Mon, May 12, 2025 at 11:52 AM Attila Doroszlai
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
>
> 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
