Skip to content
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

download errors, no kernel #151

Open
kegl opened this issue Oct 1, 2018 · 10 comments
Open

download errors, no kernel #151

kegl opened this issue Oct 1, 2018 · 10 comments
Assignees

Comments

@kegl
Copy link
Contributor

kegl commented Oct 1, 2018

There are weird errors in the full test: https://travis-ci.org/paris-saclay-cds/rampwf-kits-test-master

@kegl
Copy link
Contributor Author

kegl commented Oct 1, 2018

The storage is up, so I'm not sure what's happening. The titanic error is even stranger.

@jorisvandenbossche
Copy link
Member

some first observations:

  • The titanic one is an error with testing the notebook: it's again a problem with the notebook's kernel being python2 when ran from python 3. I think we have handled it before, but there might have been a change on the nbconvert side.
    This actually seems to have been failing for several months

  • The mars craters one fails complaining about the data_train.npy and labels_train.csv not being found. @aboucaud any idea what is happening here? I don't think we changed the naming of the files in the summer ?

  • The california one: FileNotFoundError: [Errno 2] No such file or directory: '/home/travis/build/paris-saclay-cds/rampwf-kits-test-master/california_rainfall/data/train_TS.nc'.
    This one also has been failing since the beginning.

@aboucaud
Copy link
Contributor

aboucaud commented Oct 1, 2018 via email

@jorisvandenbossche
Copy link
Member

@aboucaud
Copy link
Contributor

aboucaud commented Oct 1, 2018 via email

@kegl
Copy link
Contributor Author

kegl commented Oct 1, 2018

I think I deleted mars_craters for space. Then I discovered it was the DB :).

But this failure is not in the kit, rather the full test of ramp-workflow. Is that calling the kit's test? I don't remember.

@jorisvandenbossche
Copy link
Member

But this failure is not in the kit, rather the full test of ramp-workflow. Is that calling the kit's test? I don't remember.

What do you mean with "the full test of ramp-workfow"?
What you linked above was https://travis-ci.org/paris-saclay-cds/rampwf-kits-test-master, which are the individual kit tests.

@kegl
Copy link
Contributor Author

kegl commented Oct 1, 2018

so then it's weird that the kit tests work but not https://travis-ci.org/paris-saclay-cds/rampwf-kits-test-master

@jorisvandenbossche
Copy link
Member

OK, found the problem: with the changes in the summer, we didn't update the "testing" mode to keep it working.

On the kit's tests (https://travis-ci.org/ramp-kits/mars_craters), we actually download the full data, but on the cron job (https://travis-ci.org/paris-saclay-cds/rampwf-kits-test-master) we use the testing mode (os.environ['RAMP_TEST_MODE'] = '1')

@kegl
Copy link
Contributor Author

kegl commented Oct 2, 2018

It's still failing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants