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

CI tests failing due to renamed folder structure #62

Open
nelsonomuto opened this issue Jul 19, 2018 · 2 comments
Open

CI tests failing due to renamed folder structure #62

nelsonomuto opened this issue Jul 19, 2018 · 2 comments
Assignees

Comments

@nelsonomuto
Copy link
Contributor

nelsonomuto commented Jul 19, 2018

Expected Behavior

CI tests should be able to find files that are required/imported

Actual Behavior

Tests failing due to module not found in circle CI job

Steps to Reproduce the Problem

  1. fresh git checkout
  2. switch to branch add/testingToUpdatedStructure
  3. yarn install
  4. yarn test

Specifications

  • Version: latest
  • Browser: N/A
  • Operating System: Unix w/ case-sensitive file system

screen shot 2018-07-19 at 3 25 48 pm

@nelsonomuto nelsonomuto self-assigned this Jul 19, 2018
@nelsonomuto
Copy link
Contributor Author

Adding a postinstall script to rename the folders. I will re-test the circle job once circle ci is back up.

@nelsonomuto
Copy link
Contributor Author

nelsonomuto commented Jul 19, 2018

another issue related to the renaming is we now have both common and Common as well as container and Container when the code is merged.

we may want to just delete the old directories if this is the case and sacrifice history or create a new legacy repo to maintain the history.
screen shot 2018-07-19 at 3 17 09 pm

And after cloning the repo in the circle ci file system the common and container lower case directories still exists and some of their files are not in the Common and Container directories. Complicating matters further as it is not consistent with how this is handled on the mac localbox.

screen shot 2018-07-19 at 3 40 52 pm

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

1 participant