I found other users reporting a similar issue:
https://github.com/actions/deploy-pages/issues/188
The root cause seems to be that the deploy-pages action changed to stop
correcting permissions problems in the upload since it was slowing down
deployment. The recommended fix is to set the permissions before
uploading the artifact.
Let's see if this works.
Fixes#5376
This change introduces three new issue templates for DXC. The three
issue templates are:
* feature_request - Issues filed with this template will get
automatically tagged with the `enhancement` label
* bug_report - Issues filed with this template will get automatically
get tagged with the `bug` label
* bug_report_spirv - Issues filed with this template will get
automatically tagged with the `bug` and `spirv` labels
The bug_report and bug_report_spirv templates are otherwise identical,
but could diverge to better meet the needs of the supporting teams.
Fixes#4975.
* Enable lit by default.
* Update README for git user bin.
* Add DXC_DISABLE_LIT to replace DXC_ENABLE_LIT
* Set -DDXC_DISABLE_LIT=Off for appveyor.
* Keep original name for ClangSPIRVTests
* Set correct path for unit tests binary.
* Remove doc about DXC_DISABLE_LIT
* Remove extra space.
* Remove DxcOnUnix.rst.
This action just verifies that PRs contain descriptions. Our policy
requires PR descriptions, but we don't have consistent application of
the policy. This should help correct that.
* Update Linux build and test workflows to use lit
This change updates the build and test workflows in our azure pipelines
and the GitHub action for code coverage data to use lit instead of ctest
as the test runner. This adds additional test coverage by running some
of the LLVM & Clang tests.
* Fix missing dependency between LLVMAnalysis & DXIL
The default Linux linker fails because LLVMAnalysis depends on LLVMDXIL
and BFD doesn't cycle libraries.
* Updating pipelines to remove mkdir and cd
This just cleans up the pipeline shell commands to avoid unnecissary
mkdir and cd invocations.
Based on feedback from @Keenuts. Thanks!
* Disable LLVM LIT tests that use garbage collection
DXC disabled support for the LLVM garbage collection intrinsics.
The coverage builds take a _long_ time to run on the standard GitHub
action bots. I initially thought cancelling and restarting was a good
idea and have since reconsidered...
There were a few things missing in the initial attempt at this workflow. I left off the file extension for the CMake cache file, and also forgot to initialize the submodules.
Additionally using make is... slow. Using make `-j` causes the VM to run out of memory. To resolve those issues I'm installing ninja and using ninja instead. I'm also setting `LLVM_USE_LINKER=lld` to reduce linker memory usage and `LLVM_PARALLEL_LINK_JOBS=1` to only run one link at a time.
I've also added `--rerun-failed` and `--output-on-failure` to the ctest invocation so that if it fails we get some hopefully helpful output.
Chris B
Xiang Li
Daniele Vettorel
Chris