diff options
Diffstat (limited to 'tests/specs')
15 files changed, 15 insertions, 15 deletions
diff --git a/tests/specs/bundle/lockfile/check_error.out b/tests/specs/bundle/lockfile/check_error.out index 2b8bdfc96..6a63a01b4 100644 --- a/tests/specs/bundle/lockfile/check_error.out +++ b/tests/specs/bundle/lockfile/check_error.out @@ -9,4 +9,4 @@ This could be caused by: * the lock file may be corrupt * the source itself may be corrupt -Use the --lock-write flag to regenerate the lockfile or --reload to reload the source code from the server. +Investigate the lockfile; delete it to regenerate the lockfile or --reload to reload the source code from the server. diff --git a/tests/specs/install/future_install_node_modules/corrupted.out b/tests/specs/install/future_install_node_modules/corrupted.out index ade075744..abfbeadda 100644 --- a/tests/specs/install/future_install_node_modules/corrupted.out +++ b/tests/specs/install/future_install_node_modules/corrupted.out @@ -1,2 +1,2 @@ error: Integrity check failed for package: "npm:@denotest/esm-basic@1.0.0".[WILDCARD] -Use the --lock-write flag to regenerate the lockfile at [WILDCARD]
\ No newline at end of file +Investigate the lockfile; delete it to regenerate the lockfile at [WILDCARD]
\ No newline at end of file diff --git a/tests/specs/lockfile/auto_discover_lockfile/main.out b/tests/specs/lockfile/auto_discover_lockfile/main.out index aa24320d1..110f7e85b 100644 --- a/tests/specs/lockfile/auto_discover_lockfile/main.out +++ b/tests/specs/lockfile/auto_discover_lockfile/main.out @@ -10,4 +10,4 @@ This could be caused by: * the lock file may be corrupt * the source itself may be corrupt -Use the --lock-write flag to regenerate the lockfile or --reload to reload the source code from the server. +Investigate the lockfile; delete it to regenerate the lockfile or --reload to reload the source code from the server. diff --git a/tests/specs/lockfile/checksum_at_redirect/run.out b/tests/specs/lockfile/checksum_at_redirect/run.out index 75a34777f..6180bf55d 100644 --- a/tests/specs/lockfile/checksum_at_redirect/run.out +++ b/tests/specs/lockfile/checksum_at_redirect/run.out @@ -9,4 +9,4 @@ This could be caused by: * the lock file may be corrupt * the source itself may be corrupt -Use the --lock-write flag to regenerate the lockfile or --reload to reload the source code from the server. +Investigate the lockfile; delete it to regenerate the lockfile or --reload to reload the source code from the server. diff --git a/tests/specs/lockfile/config_file_lock_boolean/true.main.out b/tests/specs/lockfile/config_file_lock_boolean/true.main.out index 11dfc0740..69b467ef0 100644 --- a/tests/specs/lockfile/config_file_lock_boolean/true.main.out +++ b/tests/specs/lockfile/config_file_lock_boolean/true.main.out @@ -8,4 +8,4 @@ This could be caused by: * the lock file may be corrupt * the source itself may be corrupt -Use the --lock-write flag to regenerate the lockfile or --reload to reload the source code from the server. +Investigate the lockfile; delete it to regenerate the lockfile or --reload to reload the source code from the server. diff --git a/tests/specs/lockfile/config_file_lock_path/config_file_lock_path.out b/tests/specs/lockfile/config_file_lock_path/config_file_lock_path.out index 1383d945d..3043b102a 100644 --- a/tests/specs/lockfile/config_file_lock_path/config_file_lock_path.out +++ b/tests/specs/lockfile/config_file_lock_path/config_file_lock_path.out @@ -8,4 +8,4 @@ This could be caused by: * the lock file may be corrupt * the source itself may be corrupt -Use the --lock-write flag to regenerate the lockfile or --reload to reload the source code from the server. +Investigate the lockfile; delete it to regenerate the lockfile or --reload to reload the source code from the server. diff --git a/tests/specs/lockfile/config_file_lock_path/lock_check_err2.out b/tests/specs/lockfile/config_file_lock_path/lock_check_err2.out index 1383d945d..3043b102a 100644 --- a/tests/specs/lockfile/config_file_lock_path/lock_check_err2.out +++ b/tests/specs/lockfile/config_file_lock_path/lock_check_err2.out @@ -8,4 +8,4 @@ This could be caused by: * the lock file may be corrupt * the source itself may be corrupt -Use the --lock-write flag to regenerate the lockfile or --reload to reload the source code from the server. +Investigate the lockfile; delete it to regenerate the lockfile or --reload to reload the source code from the server. diff --git a/tests/specs/lockfile/lock_check_err/lock_check_err.out b/tests/specs/lockfile/lock_check_err/lock_check_err.out index 25d22490d..031ae85e6 100644 --- a/tests/specs/lockfile/lock_check_err/lock_check_err.out +++ b/tests/specs/lockfile/lock_check_err/lock_check_err.out @@ -8,4 +8,4 @@ This could be caused by: * the lock file may be corrupt * the source itself may be corrupt -Use the --lock-write flag to regenerate the lockfile or --reload to reload the source code from the server. +Investigate the lockfile; delete it to regenerate the lockfile or --reload to reload the source code from the server. diff --git a/tests/specs/lockfile/lock_check_err2/lock_check_err2.out b/tests/specs/lockfile/lock_check_err2/lock_check_err2.out index 1383d945d..3043b102a 100644 --- a/tests/specs/lockfile/lock_check_err2/lock_check_err2.out +++ b/tests/specs/lockfile/lock_check_err2/lock_check_err2.out @@ -8,4 +8,4 @@ This could be caused by: * the lock file may be corrupt * the source itself may be corrupt -Use the --lock-write flag to regenerate the lockfile or --reload to reload the source code from the server. +Investigate the lockfile; delete it to regenerate the lockfile or --reload to reload the source code from the server. diff --git a/tests/specs/lockfile/lock_dynamic_imports/lock_dynamic_imports.out b/tests/specs/lockfile/lock_dynamic_imports/lock_dynamic_imports.out index 2b8bdfc96..6a63a01b4 100644 --- a/tests/specs/lockfile/lock_dynamic_imports/lock_dynamic_imports.out +++ b/tests/specs/lockfile/lock_dynamic_imports/lock_dynamic_imports.out @@ -9,4 +9,4 @@ This could be caused by: * the lock file may be corrupt * the source itself may be corrupt -Use the --lock-write flag to regenerate the lockfile or --reload to reload the source code from the server. +Investigate the lockfile; delete it to regenerate the lockfile or --reload to reload the source code from the server. diff --git a/tests/specs/lockfile/lock_v2_check_err/lock_v2_check_err.out b/tests/specs/lockfile/lock_v2_check_err/lock_v2_check_err.out index 25d22490d..031ae85e6 100644 --- a/tests/specs/lockfile/lock_v2_check_err/lock_v2_check_err.out +++ b/tests/specs/lockfile/lock_v2_check_err/lock_v2_check_err.out @@ -8,4 +8,4 @@ This could be caused by: * the lock file may be corrupt * the source itself may be corrupt -Use the --lock-write flag to regenerate the lockfile or --reload to reload the source code from the server. +Investigate the lockfile; delete it to regenerate the lockfile or --reload to reload the source code from the server. diff --git a/tests/specs/lockfile/lock_v2_check_err2/lock_v2_check_err2.out b/tests/specs/lockfile/lock_v2_check_err2/lock_v2_check_err2.out index 1383d945d..3043b102a 100644 --- a/tests/specs/lockfile/lock_v2_check_err2/lock_v2_check_err2.out +++ b/tests/specs/lockfile/lock_v2_check_err2/lock_v2_check_err2.out @@ -8,4 +8,4 @@ This could be caused by: * the lock file may be corrupt * the source itself may be corrupt -Use the --lock-write flag to regenerate the lockfile or --reload to reload the source code from the server. +Investigate the lockfile; delete it to regenerate the lockfile or --reload to reload the source code from the server. diff --git a/tests/specs/lockfile/lock_v2_dynamic_imports/lock_v2_dynamic_imports.out b/tests/specs/lockfile/lock_v2_dynamic_imports/lock_v2_dynamic_imports.out index 2b8bdfc96..6a63a01b4 100644 --- a/tests/specs/lockfile/lock_v2_dynamic_imports/lock_v2_dynamic_imports.out +++ b/tests/specs/lockfile/lock_v2_dynamic_imports/lock_v2_dynamic_imports.out @@ -9,4 +9,4 @@ This could be caused by: * the lock file may be corrupt * the source itself may be corrupt -Use the --lock-write flag to regenerate the lockfile or --reload to reload the source code from the server. +Investigate the lockfile; delete it to regenerate the lockfile or --reload to reload the source code from the server. diff --git a/tests/specs/lockfile/no_lock/fail.out b/tests/specs/lockfile/no_lock/fail.out index 0d67cd478..14a8d19cf 100644 --- a/tests/specs/lockfile/no_lock/fail.out +++ b/tests/specs/lockfile/no_lock/fail.out @@ -9,4 +9,4 @@ This could be caused by: * the lock file may be corrupt * the source itself may be corrupt -Use the --lock-write flag to regenerate the lockfile or --reload to reload the source code from the server. +Investigate the lockfile; delete it to regenerate the lockfile or --reload to reload the source code from the server. diff --git a/tests/specs/npm/lock_file_integrity_failure/main.out b/tests/specs/npm/lock_file_integrity_failure/main.out index 741edd9d2..1f0fca91e 100644 --- a/tests/specs/npm/lock_file_integrity_failure/main.out +++ b/tests/specs/npm/lock_file_integrity_failure/main.out @@ -9,4 +9,4 @@ This could be caused by: * the lock file may be corrupt * the source itself may be corrupt -Use the --lock-write flag to regenerate the lockfile at "[WILDCARD]lock.json". +Investigate the lockfile; delete it to regenerate the lockfile at "[WILDCARD]lock.json". |