-
Notifications
You must be signed in to change notification settings - Fork 930
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
CI Profiling precursor changes #14051
Conversation
2e936bf
to
0fa25b0
Compare
74e7c57
to
7a7d5db
Compare
Signed-off-by: Thomas Parrott <[email protected]>
7a7d5db
to
e41bd89
Compare
No need to run this repeatedly on every system test workflow. Signed-off-by: Thomas Parrott <[email protected]>
af0cf2c
to
94cbf89
Compare
Build lxd project binaries only, and not all of the test and client binaries too. Signed-off-by: Thomas Parrott <[email protected]>
Rather than build it all again. Signed-off-by: Thomas Parrott <[email protected]>
Signed-off-by: Thomas Parrott <[email protected]>
We use the same dqlite built during the code tests now for consistency. Also avoids delays with ppa being built. Signed-off-by: Thomas Parrott <[email protected]>
Like its done in snap. Signed-off-by: Thomas Parrott <[email protected]>
As doesn't link against sqlite3. Signed-off-by: Thomas Parrott <[email protected]>
Signed-off-by: Thomas Parrott <[email protected]>
So errors are more visible. Signed-off-by: Thomas Parrott <[email protected]>
Like its done in snap. Signed-off-by: Thomas Parrott <[email protected]>
Signed-off-by: Thomas Parrott <[email protected]>
Signed-off-by: Thomas Parrott <[email protected]>
4756b12
to
a858141
Compare
Signed-off-by: Thomas Parrott <[email protected]>
ff04671
to
0427f63
Compare
Signed-off-by: Thomas Parrott <[email protected]>
0427f63
to
fce81c5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thanks! There might be some things to further remove but those can wait till later.
One thing we lose with that is we are now only testing/building on Go 1.22. That said, maybe you wanted to have that done first and then we add another step to the Code
job later on.
Note, thanks for highlighting. |
This PR: