Update build type to release & remove multi-step build in CI - #3745
Conversation
9d6da81 to
7721d68
Compare
|
If we go ahead with this, no reason not to implement it across all the pipelines. |
|
I want to see the impact on compile times. If there's none or little, So far, looks like not using DebugInfo actually reduced the compile times |
SergioRAgostinho
left a comment
There was a problem hiding this comment.
@kunaltyagi Feel free to merge once you're happy with the compile times.
taketwo
left a comment
There was a problem hiding this comment.
Apply to Ubuntu 16.04 as well?
Tested it out 2 separate configurations, Release is around 1.4x faster. Config 1: Config 2:
Should I do that in a separate PR since we can apply the same thing to macOS and Windows as well? |
|
I'd switch all jobs (including tutorials) to release mode at the same time in this PR. Just change the title accordingly ;) Edit: also rebase on the current HEAD to get updated MacOS jobs. |
|
I have been testing out the integration with Ubuntu 16 and noticed the flag |
|
Yes. It is our goal to eventually have
Are there many warnings and they trivial to fix? If so, it would be nice to do so and switch to Release in 16.04 job. If that requires more work, then let's leave 16.04 out for now. |
7721d68 to
5ce24ba
Compare
Done that. Merged all the CI changes into this PR.
There were not many warnings, so I was able to fix them. They need a review. |
c9b6ba6 to
1aa0440
Compare
|
Any reason why only the ubuntu builds have |
I remember windows having troubles with non 3 char extensions back in the days. Not sure what's the current status on this. It was most likely a random inconsistency we overlooked. Ideally, yaml should be used. source |
1aa0440 to
c350800
Compare
kunaltyagi
left a comment
There was a problem hiding this comment.
🚀 (yml -> yaml can be here or elsewhere)
Release doesn't make MSVC x64 happier. It stills OOMs out.
Yeah, older versions of Windows had this problem, don't think its there anymore. WIll test out and rename if it works. |
Yeah, not sure was building fine before. |
|
MSVC is a weird camper. I have manually restarted the job so many times only for the jobs that OOMed out to be successful (most likely due to variation caused by the parallel build, which isn't as managed per target as the unix ones are) |
kunaltyagi
left a comment
There was a problem hiding this comment.
Is the CI hardcoded to the file names? The renamed files didn't run on the CI.
Changeset LGTM
Yup, they are hardcoded for filenames so they will need to be updated. |
9d94eed to
58a56c1
Compare
Will do once this is merged. |
SergioRAgostinho
left a comment
There was a problem hiding this comment.
LGTM. Despite the messed up casts :')
In terms of commit organization I would squash things into the following 4 topics:
- Update build type to release
- Removing of multistep build
- File renaming
- All commits related to suppressing warnings.
|
Pinging @shrijitsingh99 |
Using Release occupies less space and is also around 1.4x faster compared to RelWithDebInfo
Compiling some of the test targets with -j2 option used to lead to pipeline failures but now that issue is no longer present
* leaf_node may have been uninitialized * signed overflow may have occurred for m_count & m_capacity
e6c13c8 to
1d1fb6b
Compare
Done |
|
Updated the filenames on Azure 🚀 |
Resolves #3656.
Edit: Changed build type for all OS and removed the multi-step builds since there were no longer any OOM issues.