ChenSammi commented on PR #11042: URL: https://github.com/apache/ozone/pull/11042#issuecomment-5366532529
> > I tried to add a property test([branch](https://github.com/ChenSammi/ozone/tree/refs/heads/HDDS-16186-reorder-expiration-test)) to lower the minimal allowed expiration to 1s. But the STS failed due to the "aws sts assume-role" command used in the robot test, which still enforce the 900s low boundary. > > Fabian, can you collect the sts and total CI execution time, with and without the tests that require the 15 minutes expiration wait? > > hi @ChenSammi - here is run with all expired token tests skipped: https://github.com/fmorg-git/ozone/actions/runs/32315114256/job/96268439903 (`27m 25s`) Here is run with all the expired token tests run (not sure why it went down): https://github.com/fmorg-git/ozone/actions/runs/32320469400/job/96283505022 (`24m56s`) If it does not increase the sts suits execution time obviously, then I think it's safe to include the expiration tests. The time went down could be the running environment turbulence. We have seen that Recon test suits, in some CI, it costs 30+ mins, while in other CI, it cannot finish in 1h 30m. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
