Improve error handling from repo2docker

[rgaiacs]

When trying to run gesiscss/css_methods_python@481fd88 on https://mybinder.org/, the building process takes a long time and fails with

Step 39/50 : RUN TIMEFORMAT='time: %3R' bash -c 'time ${MAMBA_EXE} env update -p ${NB_PYTHON_PREFIX} --file "binder/environment.yml" && time ${MAMBA_EXE} clean --all -f -y && ${MAMBA_EXE} list -p ${NB_PYTHON_PREFIX} '
 ---> Running in d49ceb6301e1


Looking for: ['beautifulsoup4=4.11.1', 'emoji=2.2.0', 'factor-analyzer=0.4.1', 'feedparser=6.0.8', 'gensim=4.1.2', 'ipywidgets=7.6.5', 'matplotlib=3.5.2', 'networkx=2.8.4', 'nltk=3.7', 'numpy=1.21.5', 'openpyxl=3.0.10', 'pandas=1.4.4', 'pip=22.2.2', 'powerlaw=1.4.6', 'pygraphviz=1.9', 'pyldavis=3.4.1', 'python=3.9.13', 'requests=2.28.1', 'scikit-learn=1.0.2', 'scipy=1.9.1', 'seaborn=0.11.2', 'selenium=3.9.0', 'spacy=3.5.3', 'sqlalchemy=1.4.39', 'statsmodels=0.13.2', 'textacy=0.11.0', 'wikipedia=1.4.0', 'xlsxwriter=3.0.3']


bash: line 1:     9 Killed                  ${MAMBA_EXE} env update -p ${NB_PYTHON_PREFIX} --file "binder/environment.yml"
time: 1628.928
Removing intermediate container d49ceb6301e1
The command '/bin/sh -c TIMEFORMAT='time: %3R' bash -c 'time ${MAMBA_EXE} env update -p ${NB_PYTHON_PREFIX} --file "binder/environment.yml" && time ${MAMBA_EXE} clean --all -f -y && ${MAMBA_EXE} list -p ${NB_PYTHON_PREFIX} '' returned a non-zero code: 137

The above log has zero information that will help the user to have a successful build.

When I build the same repository locally with repo2docker, the log shows

Step 39/50 : RUN TIMEFORMAT='time: %3R' bash -c 'time ${MAMBA_EXE} env update -p ${NB_PYTHON_PREFIX} --file "binder/environment.yml" && time ${MAMBA_EXE} clean --all -f -y && ${MAMBA_EXE} list -p ${NB_PYTHON_PREFIX} '
 ---> Running in bcd61d64578c


Looking for: ['beautifulsoup4=4.11.1', 'emoji=2.2.0', 'factor-analyzer=0.4.1', 'feedparser=6.0.8', 'gensim=4.1.2', 'ipywidgets=7.6.5', 'matplotlib=3.5.2', 'networkx=2.8.4', 'nltk=3.7', 'numpy=1.21.5', 'openpyxl=3.0.10', 'pandas=1.4.4', 'pip=22.2.2', 'powerlaw=1.4.6', 'pygraphviz=1.9', 'pyldavis=3.4.1', 'python=3.9.13', 'requests=2.28.1', 'scikit-learn=1.0.2', 'scipy=1.9.1', 'seaborn=0.11.2', 'selenium=3.9.0', 'spacy=3.5.3', 'sqlalchemy=1.4.39', 'statsmodels=0.13.2', 'textacy=0.11.0', 'wikipedia=1.4.0', 'xlsxwriter=3.0.3']


Could not solve for environment specs
The following packages are incompatible
├─ python 3.9.13**  is installable with the potential options
│  ├─ python 3.9.13, which can be installed;
│  └─ python 3.9.13 would require
│     └─ python_abi 3.9.* *_cp39, which can be installed;
├─ selenium 3.9.0**  is installable with the potential options
│  ├─ selenium 3.9.0 would require
│  │  └─ python_abi * *_cp27mu, which can be installed;
│  ├─ selenium 3.9.0 would require
│  │  └─ python >=2.7,<2.8.0a0 , which conflicts with any installable versions previously reported;
│  ├─ selenium 3.9.0 would require
│  │  └─ python >=3.5,<3.6.0a0 , which conflicts with any installable versions previously reported;
│  ├─ selenium 3.9.0 would require
│  │  └─ python >=3.6,<3.7.0a0 , which conflicts with any installable versions previously reported;
│  ├─ selenium 3.9.0 would require
│  │  └─ python_abi * *_cp35m, which can be installed;
│  └─ selenium 3.9.0 would require
│     └─ python_abi * *_cp36m, which can be installed;
└─ textacy 0.11.0**  is uninstallable because there are no viable options
   ├─ textacy 0.11.0 would require
   │  ├─ python >=3.10,<3.11.0a0 , which conflicts with any installable versions previously reported;
   │  └─ python_abi 3.10.* *_cp310, which conflicts with any installable versions previously reported;
   ├─ textacy 0.11.0 would require
   │  └─ python_abi 3.7.* *_cp37m, which conflicts with any installable versions previously reported;
   ├─ textacy 0.11.0 would require
   │  └─ python_abi 3.8.* *_cp38, which conflicts with any installable versions previously reported;
   └─ textacy 0.11.0 would require
      └─ python_abi 3.9.* *_cp39, which conflicts with any installable versions previously reported.
time: 41.387
Removing intermediate container bcd61d64578c
The command '/bin/sh -c TIMEFORMAT='time: %3R' bash -c 'time ${MAMBA_EXE} env update -p ${NB_PYTHON_PREFIX} --file "binder/environment.yml" && time ${MAMBA_EXE} clean --all -f -y && ${MAMBA_EXE} list -p ${NB_PYTHON_PREFIX} '' returned a non-zero code: 1

Now, the user know that mamba failed to resolve the dependencies.

[manics]

How much memory was used whilst attempting to resolve the dependencies?

[rgaiacs]

I don't know how much memory. How can can I get this information?

[manics]

You'll need to look at your K8s monitoring system e.g. Prometheus and look for the build pod name.