Skip to content

Conversation

@cbezault
Copy link
Contributor

@cbezault cbezault commented Apr 3, 2020

We have decided that it is worth gating any builds and test runs behind a successful format validation step.

Also since doing this needed me to figure out how to set up a dev environment without vcpkg's help do a drive-by and enable the /BE testing.

In order to get /BE working I also need to update the VMs.

@cbezault cbezault added enhancement Something can be improved infrastructure Related to repository automation labels Apr 3, 2020
@cbezault cbezault self-assigned this Apr 3, 2020
@cbezault cbezault force-pushed the separate-clang-format branch from 1fb6eb7 to 2736e6f Compare April 3, 2020 17:28
@cbezault cbezault marked this pull request as ready for review April 3, 2020 18:00
@cbezault cbezault requested a review from a team as a code owner April 3, 2020 18:00
@cbezault
Copy link
Contributor Author

cbezault commented Apr 3, 2020

I'm not sure what to make the displayName of the job under the "Code Format Validation" stage without it sounding silly. I've settled on "Run" for now so that on Github we see "Code Format Validation Run" for the job.

parameters:
targetPlatform: x86
variables:
agentPool: 'StlBuild-2020-03-28'
Copy link
Contributor

Choose a reason for hiding this comment

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

@CaseyCarter CaseyCarter removed enhancement Something can be improved work in progress labels Apr 3, 2020
@cbezault cbezault changed the title Try running format validation as its own stage Run format validation as its own stage Apr 3, 2020
@cbezault
Copy link
Contributor Author

cbezault commented Apr 3, 2020

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@cbezault cbezault force-pushed the separate-clang-format branch 2 times, most recently from c4d2475 to a26bd31 Compare April 4, 2020 00:06
@cbezault cbezault changed the title Run format validation as its own stage Run format validation as its own stage and enable /BE Apr 4, 2020
@cbezault cbezault added test Related to test code and removed work in progress labels Apr 4, 2020
@cbezault
Copy link
Contributor Author

cbezault commented Apr 4, 2020

I always bite off more than I can chew on these PRs. It appears the VMs don't have cpfe.dll on them and so can't run the /BE tests.

@AdamBucior
Copy link
Contributor

I'm not sure what to make the displayName of the job under the "Code Format Validation" stage without it sounding silly.

Maybe make the stage name "Code Format" and the job name "Validation".

@cbezault
Copy link
Contributor Author

cbezault commented Apr 4, 2020

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@cbezault cbezault force-pushed the separate-clang-format branch from b12783c to 8374ef2 Compare April 5, 2020 04:52
@cbezault cbezault force-pushed the separate-clang-format branch from c39d78a to 075b9e6 Compare April 9, 2020 01:18
-Name Path `
-Value "$($environmentKey.Path);C:\Program Files\CMake\bin;C:\Program Files\LLVM\bin"

Write-Host 'Configuring AntiVirus exclusions...'
Copy link
Contributor

Choose a reason for hiding this comment

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

Why is "AntiVirus" PascalCased here? PowerShell-ism leaking into the output?

@cbezault cbezault merged commit 2597e24 into microsoft:master Apr 10, 2020
fengjixuchui added a commit to fengjixuchui/STL that referenced this pull request Apr 10, 2020
Run format validation as its own stage and enable /BE (microsoft#682)
StephanTLavavej added a commit to StephanTLavavej/STL that referenced this pull request Aug 19, 2020
This was skipped by microsoftGH-682 on 2020-04-09. At the time, we were using
VS 2019 16.6 Preview 2 (microsoftGH-645 merged on 2020-03-28). Now we're using
VS 2019 16.8 Preview 1, and I can't reproduce this ICE locally. I ran
x86 and x64, 30 times each, and they all passed. Let's try restoring
this configuration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

infrastructure Related to repository automation test Related to test code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants