Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roll out testing 37.20221225.2.2, next 37.20221225.1.2 #625

Merged

Conversation

coreosbot-releng
Copy link

Requested by @dustymabe via GitHub workflow (source).

@github-actions
Copy link

github-actions bot commented Jan 4, 2023

next
    version: 37.20221225.1.2 (latest)
    start: 2023-01-05 14:00:00+00:00 UTC (in 1 day, 13:44:49)
           2023-01-05 09:00:00-05:00 Raleigh/New York/Toronto
           2023-01-05 15:00:00+01:00 Berlin/France/Poland
    duration: 1440m (24.0h)
stable
    version: 37.20221211.3.0 (latest)
    start: 2022-12-27 18:00:00+00:00 UTC (7 days, 6:15:11 ago)
           2022-12-27 13:00:00-05:00 Raleigh/New York/Toronto
           2022-12-27 19:00:00+01:00 Berlin/France/Poland
    duration: 2880m (48.0h)
testing
    version: 37.20221225.2.2 (latest)
    start: 2023-01-05 14:00:00+00:00 UTC (in 1 day, 13:44:48)
           2023-01-05 09:00:00-05:00 Raleigh/New York/Toronto
           2023-01-05 15:00:00+01:00 Berlin/France/Poland
    duration: 1440m (24.0h)

},
"eu-central-2": {
"release": "37.20221225.1.2",
"image": "ami-066b1dfe86cf21ffc"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wonder why the bot missed this addition and the one below for eu-south-2? cc @bgilbert

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! It turns out that GitHub doesn't render more than 10 warnings: coreos/actions-lib#10

Copy link
Member

@dustymabe dustymabe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - the CI failure is because it looks like there are new AWS regions that have gone live and are enabled in our account now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants