Open sgibson91 opened 4 years ago
So this might be a good issue to move over to nbclient as the execute notebook logic now resides over there for the upcoming next release of nbconvert. However, nbconvert should be either raising an exception or launching a new kernel for each notebook even with the proxy to nbclient. I'll mark this as a bug to look into. Thanks for raising.
Hi š
I'm trying to set up nbconvert in my CI pipeline to identify when my notebooks break. I have a
.tests
subdirectory with two notebooks in, one uses the Python kernel and the other uses the R kernel.The command I'd like to execute in my CI is the following:
However, the bug I'm seeing is that nbconvert tries to convert both notebooks using the same kernel. Which kernel it chooses seems to be dependent on which notebook it tries to convert first.
For example:
However when the notebooks are run separately, everything works as expected.
So nbconvert is obviously correctly identifying the kernel from the metadata for each notebook individually. The behaviour I expected is that when nbconvert is passed a list of notebooks, it would identify and use the kernel requested by each notebook in turn, not just stick with the first one that comes up.
Any help you can offer on this topic would be really appreciated! āØ
My CI config: https://github.com/alan-turing-institute/bridge-data-environment/blob/master/.github/workflows/repo2docker-pull-requests.yml PR with broken CI due to this behaviour: https://github.com/alan-turing-institute/bridge-data-environment/pull/25
Nbconvert version: 5.6.1