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

Fix Travis CI Build #2

Open
sunjay opened this issue Aug 16, 2019 · 2 comments · May be fixed by #4
Open

Fix Travis CI Build #2

sunjay opened this issue Aug 16, 2019 · 2 comments · May be fixed by #4

Comments

@sunjay
Copy link
Owner

sunjay commented Aug 16, 2019

Right now our builds are timing out because we're running all of our examples, even the ones that take forever.

Create a file in examples/ called ".test_examples" where each line is either a path relative to the examples directory (maybe starting with !), a line starting with #, or a blank line.

  • All paths listed will be run during the CI build.
  • All paths starting with ! will not be run.
  • All paths in the examples directory must be listed in this file. That will be checked so CI fails if a file isn't listed.

The run all examples script (rewrite in Python) will be the one to read all of this and check those invariants. It should take a command line parameter for the number of groups and the group to run. Then we can split the examples into N groups and run those in parallel.

@sunjay
Copy link
Owner Author

sunjay commented Dec 17, 2019

Apparently public projects in Azure Pipelines get unlimited minutes. We can probably copy the config from turtle and use that in this repo to fix the build issues.

@sunjay sunjay linked a pull request Dec 31, 2019 that will close this issue
@sunjay
Copy link
Owner Author

sunjay commented Feb 27, 2020

Another idea is to create a single example that uses all the features of the ray tracer and run that instead of running every example. Note that we should still ensure that all examples are compiled.

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 a pull request may close this issue.

1 participant