-
Notifications
You must be signed in to change notification settings - Fork 12
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
Enable Raven notebooks in nightly runs of Jenkins #423
Comments
raven-nb-on-Jenkins.txt: Logs for Raven nb with 8 failing notebooks:
|
Back in May 17, 2021, there was only 2 broken Raven notebooks on Jenkins, see comment bird-house/birdhouse-deploy#170 (comment) All passed except 2 notebooks:
|
Raven nb with 6 failing notebooks to go:
|
@huard @richardarsenault To eventually run automatically under Jenkins, those S3 and Google drive credentials should be given to Jenkins. There are 2 errors that seem to be code related:
See all details in previous comment #423 (comment). |
Description
Meta issue to link to other issues blocking this issue.
#383
#410
#353
#424
Also have to avoid the need to use
--nbval-lax
with Raven notebooks. This should be easier now that PR has been merged Ouranosinc/PAVICS-e2e-workflow-tests#73Remember to test against test PAVICS server than production server. CRIM will spawn an fresh new PAVICS test server for each PR so support for test server is crucial to not break our automated testing pipeline. Any new test data needed by raven notebooks, need to be available on the test server.
The text was updated successfully, but these errors were encountered: