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

Setting up continuous integration #118

Closed
antiagainst opened this issue Mar 3, 2017 · 5 comments
Closed

Setting up continuous integration #118

antiagainst opened this issue Mar 3, 2017 · 5 comments

Comments

@antiagainst
Copy link
Contributor

antiagainst commented Mar 3, 2017

It would be nice to have a bot to automatically check pull requests to make sure they are not breaking the master branch. Appveyor is quite popular on GitHub as a Windows continuous integration service, and it is already used by vscode. Is it possible to enable Appveyor for this project? Or actually there are other plans for continuous integration?

cc @dneto0 @ehsannas

@marcelolr
Copy link
Contributor

Thanks for bringing this up.

Right now we have a couple of internal systems that are keeping an eye on things for us, mostly because we have a pretty specific setup right now in terms of OS/hardware/drivers to run the execution tests. Perhaps a starting point would be to simply need to tweak stuff so we post back the results to the pull request threads.

I don't have experience with Appveyor myself, but I can educate myself and have a better-informed opinion. Again, thanks for bringing this up - I'll update this thread with progress.

@antiagainst
Copy link
Contributor Author

Hi @marcelolr,

That's good to know. As for Appveyor, if it's OK to enable it for this project, I can contribute the configuration file.

Actually I've already started one, but just experiencing some problems right now.

@antiagainst
Copy link
Contributor Author

The problem is that dxgi1_4.h cannot be found during compiling. But it does exist in C:\Program Files (x86)\Windows Kits\10\Include\10.0.14393.0\shared as printed here. Not clear why yet.

@marcelolr
Copy link
Contributor

@antiagainst, is there anything else missing to close this issue? thx

@antiagainst
Copy link
Contributor Author

Nope, all done for this issue. I'll close it. :)

pow2clk pushed a commit to pow2clk/DirectXShaderCompiler that referenced this issue Jan 2, 2024
There is a bug in pandoc-2.9 that causes it to fail processing the
language spec. The issue is resolved on pandoc-3.1 which is not
currently in the Ubuntu Jammy packages. This change just downloads the
release from GitHub and installs it into the VM image.
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

No branches or pull requests

2 participants