-
Notifications
You must be signed in to change notification settings - Fork 7
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
🐛 [BUG]: Failing CI tests from nbval output diff #496
🐛 [BUG]: Failing CI tests from nbval output diff #496
Comments
Your other errors are Raven's notebooks? You intending to run them everytime now? They are known to not all pass. I don't think they are related to JupyterHub v5. We never ran Raven notebooks during the regular pipeline before anyways. Any specific reason you want to activate them during the pipeline now? |
I noticed from previous runs that many repos that were originally tested were omitted, so I decided to toggle the test switches dynamically according to the service/components enabled by |
Raven nbs were not enabled by default because they were very unstable at the time. Now things are getting better. I could take some time to get them to pass in Jenkins. |
@fmigneault Quick update:
Was fixed in Ouranosinc/pavics-sdi#344
All except one will be fixed by The only last Raven nb failure is |
To be used together with Ouranosinc/jenkins-config#17. If Jenkins `env.local` contains `export DEFAULT_CONFIG_PARAMETERS_SCRIPT_URL="https://raw.githubusercontent.com/Ouranosinc/PAVICS-e2e-workflow-tests/refs/heads/master/test-override/jenkins-params-default.include.sh"` notebooks that are known to have problems will be skipped so that Jenkins do not fail for known reasons. This is related to bird-house/birdhouse-deploy#496. If raven notebooks are enabled by default, then we need to blacklist one of them because that one never passed, see `test-override/jenkins-params-default.include.sh` (the file that Jenkins will be pointed to). The raven notebook is finally disabled by this PR CSHS-CWRA/RavenPy#460. In this same effort, we also add the ability to blacklist notebooks only at the "generating output.ipynb" stage, but not in "pytest stage". The reason is that those notebooks have some cells that are disabled during the "pytest stage" because they take too long so then there are no reason to generate the output because 1) it will timeout anyways, 2) the output won't match since some cells are disabled during "pytest stage". @fmigneault CRIM should simply point to our `https://raw.githubusercontent.com/Ouranosinc/PAVICS-e2e-workflow-tests/refs/heads/master/test-override/jenkins-params-default.include.sh` file so we will be responsible for keeping up-to-date this list of known failures to prevent breaking CRIM pipeline.
@fmigneault This issue should be completely fixed with this last PR CSHS-CWRA/RavenPy#463 |
Summary
Following the DACCS CI Jenkins update to handle JupyterHub v5 (#493), multiple tests are failing.
It seems to be related to output diffs, either from jupyter itself or underlying packages installed in the docker of workflow-tests.
Details
From http://daccs-jenkins.crim.ca/job/PAVICS-e2e-workflow-tests/job/master/29/consoleFull
To Reproduce
Steps to reproduce the behavior:
Related issues
The text was updated successfully, but these errors were encountered: