Skip to content

Conversation

@sebastienros
Copy link
Member

Fix aspnetcore CI builds

Unhandled exception. System.NotSupportedException: Unsupported log file format. Latest supported version is 16, the log file has version 17.

This version supports 17

Copy link

@riarenas riarenas left a comment

Choose a reason for hiding this comment

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

This lines up with other updates we've done. So this LGTM I guess? No idea how this gets deployed, and I'm not sure it's expected for this repo to not run any builds during PRs?

@riarenas
Copy link

@garath maybe knows something?

@riarenas
Copy link

It looks like this might just get deployed straight to production after merging when the CI pipeline runs?

We also have merged a bunch of other PRs without any PR validation, so it looks like this is just the state of things right now.

@sebastienros
Copy link
Member Author

Note that I don't have the merge rights, so don't please wait on me ;)

@garath
Copy link
Member

garath commented Oct 27, 2023

I agree this is inline with previous changes. Let's take this and check the state of the main build after the nightly run.

@garath garath merged commit 4b36df6 into dotnet:main Oct 27, 2023
@sebastienros sebastienros deleted the sebros/updatelogger branch October 27, 2023 18:58
@garath
Copy link
Member

garath commented Oct 27, 2023

By request I've started an early build to get this published: Pipelines - Run 20231027.2 (azure.com)

@riarenas
Copy link

Couldn't this wait until Monday? We shouldn't get in the habit of deploying services on a Friday

@sebastienros
Copy link
Member Author

Couldn't this wait until Monday? We shouldn't get in the habit of deploying services on a Friday

Right, it could break the SourceIndex build steps. Oh wait! 😁

No worries, there might be other things that get broken. I can't estimate the impact of these change and I don't think it's a big problem for a WE.

@garath
Copy link
Member

garath commented Oct 27, 2023

I hear you, it is not a risk-free thing.

CI/CD normally runs every night, so this would have happened in a few hours anyway. Unfortunately or not, this was never set up like a proper service.

@sebastienros
Copy link
Member Author

I assume nothing will get through until another change gets into arcade, right?

https://github.com/dotnet/arcade/blob/main/eng/common/templates/job/source-index-stage1.yml#L3

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.

3 participants