aiidateam / aiida_core / 6078 / 7
73%
develop: 74%

LAST BUILD BRANCH: fix_3032_doc_working_importexport
DEFAULT BRANCH: develop
Ran
Files 387
Run time 22s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 69.165% (-0.1%) from 69.3%
TEST_AIIDA_BACKEND=sqlalchemy TEST_TYPE="tests"

Pull #2820

travis-ci

web-flow 
Automate export file migration for `verdi import`

Fixes #2739.

Invoke `verdi export migrate` in `verdi import`
if it turns out the export file archive cannot be imported
due to an IncompatibleArchiveVersionError.

The default is to automatically migrate it (via a temporary file).

Introduce the `--non-interactive` flag for `verdi import`.

Add tests for new functionality.

Make sure `--non-interactive` does not print confirm messages.
Make sure old export files are automatically migrated, both local files and from URLs.

Introduce the `--migration`/`--no-migration` choice to force migration, if needed
or avoid automatic migration.
This makes sure that an error code != 0 is still present,
when automatic migration is not performed on old export files.

Following behaviour is expected and implemented:

| `migration` | `non_interactive` | Result CLI | Result script |
| ------------- | ---------------------- | ------------- | ---------------- |
| `True`* | `False`* | Query user, migrate | Migrate |
| `True`* | `True` | No query, migrate | Migrate |
| `False` | `False`* | No query, no migrate | No migrate |
| `False` | `True` | No query, no migrate | No migrate |

*Default.

Separate code into two utility functions that help to import and migrate.
Pull Request #2820: Automate export file migration for `verdi import`

22673 of 32781 relevant lines covered (69.17%)

0.69 hits per line

Source Files on job 6078.7 (TEST_AIIDA_BACKEND=sqlalchemy TEST_TYPE="tests")