You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FAQ_dask_parallel.ipynb is a brand new notebook since 4 days not "Jenkins proof" yet, I only have error with this one. Will try to fix that one.
PAVICStutorial_ClimateDataAnalysis-5Visualization.ipynb is a known weirdo error already tracked by Ouranosinc/PAVICS-landing#103.
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 EXTRA_CONFIG_DIRS in the CI. Since raven in included in the test configuration, its tests are run as well. I don't see a reason to skip it, since it is part of the stack. It was probably skipped just because of an undefined default TEST_RAVEN_REPO=false. From all tests available in https://github.com/Ouranosinc/PAVICS-e2e-workflow-tests/blob/master/testall, only TEST_ESGF_COMPUTE_API_REPO should now be disabled because their notebooks don't actually point at the instance being tested.
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.
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: