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

Disable ccache in Windows CPU CI pipeline #19131

Merged
merged 2 commits into from
Jan 14, 2024
Merged

Disable ccache in Windows CPU CI pipeline #19131

merged 2 commits into from
Jan 14, 2024

Conversation

snnn
Copy link
Member

@snnn snnn commented Jan 13, 2024

Description

Disable ccache for all the jobs in in Windows CPU CI pipeline.
Before disabling it, the build has a warning that:

"MSIL .netmodule or module compiled with /GL found; restarting link with /LTCG; add /LTCG to the link command line to improve linker performance"

After disabling it, the warning is gone and the build doesn't use /GL or /LTCG.

Cache itself should not cause this difference.

Motivation and Context

@snnn snnn requested a review from a team as a code owner January 13, 2024 17:36
@snnn snnn changed the title Disable ccache for winml CI build Disable ccache in Windows CPU CI pipeline Jan 13, 2024
@snnn snnn merged commit 5558912 into main Jan 14, 2024
92 of 94 checks passed
@snnn snnn deleted the snnn/disable_ccache branch January 14, 2024 02:40
mszhanyi pushed a commit that referenced this pull request Jan 15, 2024
### Description
Disable ccache for all the jobs in in Windows CPU CI pipeline.
Before disabling it, the build has a warning that:

"MSIL .netmodule or module compiled with /GL found; restarting link with
/LTCG; add /LTCG to the link command line to improve linker performance"

After disabling it, the warning is gone and the build doesn't use /GL or
/LTCG.

Cache itself should not cause this difference. 

### Motivation and Context
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.

2 participants