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

test tidy failing on some systems with sed and seq errors. #461

Open
mercere99 opened this issue Jan 5, 2022 · 0 comments
Open

test tidy failing on some systems with sed and seq errors. #461

mercere99 opened this issue Jan 5, 2022 · 0 comments
Assignees

Comments

@mercere99
Copy link
Member

Some of the test tidy scripts are running smoothly, but others are reporting errors. In particular, it fails on MacOS reporting errors in find, sed, and seq.

Actions taken:
In the main Empirical directory I typed:
./ci/test_tidy.sh

Many thousands of lines of output followed, beginning with:

Running tidyness enforcement tests...
See https://empirical.readthedocs.io/en/latest/dev/guide-to-testing.html#tidyness-enforcement for info on tidyness enforcement.
(Including how to automatically generate tidyness fixes if tidyness enforcement detects tidyness issues.)
./ci/test_alphabetize_includes.sh: line 11: sha1sum: command not found
find: illegal option -- p
usage: find [-H | -L | -P] [-EXdsx] [-f path] path ... [expression]
       find [-H | -L | -P] [-EXdsx] -f path [path ...] [expression]
.............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
./ci/test_alphabetize_includes.sh: line 15: sha1sum: command not found
find: illegal option -- p
usage: find [-H | -L | -P] [-EXdsx] [-f path] path ... [expression]
       find [-H | -L | -P] [-EXdsx] -f path [path ...] [expression]
✔ include alphabetization ok
./ci/test_alphabetize_imports.sh: line 11: sha1sum: command not found
find: illegal option -- p
usage: find [-H | -L | -P] [-EXdsx] [-f path] path ... [expression]
       find [-H | -L | -P] [-EXdsx] -f path [path ...] [expression]

...

Later errors include many lines like:

seq: needs negative decrement
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
seq: needs negative decrement
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text
sed: 1: "include/emp/matching/ma ...": command i expects \ followed by text

And finally it ends with:

./ci/test_license_notices.sh: line 15: sha1sum: command not found
find: illegal option -- p
usage: find [-H | -L | -P] [-EXdsx] [-f path] path ... [expression]
       find [-H | -L | -P] [-EXdsx] -f path [path ...] [expression]
✔ license notices ok
✔ conflict markers ok
./ci/test_end_of_file_newlines.sh: line 11: sha1sum: command not found
find: illegal option -- p
usage: find [-H | -L | -P] [-EXdsx] [-f path] path ... [expression]
       find [-H | -L | -P] [-EXdsx] -f path [path ...] [expression]
./ci/test_end_of_file_newlines.sh: line 15: sha1sum: command not found
find: illegal option -- p
usage: find [-H | -L | -P] [-EXdsx] [-f path] path ... [expression]
       find [-H | -L | -P] [-EXdsx] -f path [path ...] [expression]
✔ EOF newlines ok
=========================================================================
uncommitted changes detected,
refusing to perform potentially destructive tidy operation!

1. commit your changes (including untracked files)
   -> hint: make clean; git add .; git commit

or

2. stash your changes (including untracked files)
   -> hint: git stash --include-untracked
   -> hint (to recover your stashed changes later): git stash pop

or

3. copy your changes elsewhere and remove them here
   -> hint: cp -r . ../Empirical_bak
   -> hint: git clean -fxd
(base) charles@Charless-MacBook-Pro Empirical % s
On branch MABE_devel
Your branch is ahead of 'origin/MABE_devel' by 1 commit.
  (use "git push" to publish your local commits)

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	.bumpversion.cfg-e
	.editorconfig-e
	.github/ISSUE_TEMPLATE/bug_report.md-e
	.github/ISSUE_TEMPLATE/feature_request.md-e
	.github/workflows/CI.yml-e
	.gitignore-e

...

The list of files continues with every single Empirical file (I think) all with a -e appended to their end.

NOTE: The first time through it DID successfully alphabetize all of my includes... This problem occurred on the second time I ran it.

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

No branches or pull requests

2 participants