PGO builds are a three stage process - build chromium with chrome_pgo_phase=1, run profiles, then build chromium again with chrome_pgo_phase=2. This is the sort of thing that should normally only be done on a build machine when you are ready to ship a production build. I don't know if PGO is supported with VS 2017 community edition. That is probably the root cause of the failure.
So, don't set chrome_pgo_phase. Also be aware that official builds - especially if using VC++ - can take a really long time to build.
If the problem persists then you will need to debug Chromium, using windbg or VS.
What are you trying to do?