Karma modules not found since this morning



Hey there,

i noticed that my karma tests are not working anymore.

I changed simple html in a project and now internal karma modules are not found.

my config:

version: 2
    working_directory: ~/project
      - image: node:6.11.1
      - checkout
      - run:
          name: "Checking Versions"
          command: |
            node --version
            npm --version
      - restore_cache:
          key: dependency-cache-{{ .Branch }}-{{ checksum "package.json" }}
      - run:
          name: install-npm-wee
          command: npm install
      - save_cache:
          key: dependency-cache-{{ .Branch }}-{{ checksum "package.json" }}
            - .node_modules
      - persist_to_workspace:
          root: .
          paths: .
    working_directory: ~/project
      - image: node:6.11.1
      - attach_workspace:
          at: ~/project
      - run:
          name: test
          command: npm test
  version: 2
      - build
      - test:
            - build

yesterday everything works quite well (sometimes caching failed, but that is “okay” i think).

But since my last commit karma can not find ./lib/cli, but i am calling the local karma installation in my package.json

test": "./node_modules/.bin/karma start ./test-config/karma.conf.js --single-run

if i additionally install karma-cli i get the error: Cannot find module './log'.

Maybe there were some changes in version 2.0 since the last day?

Thanks in advance.

EDIT: if i execute the build and test in a single step without workflows it is working. Seems like there is getting something lost during persistent storage step? But the “attach” is working because all node_modules are in the project folder --> i checked this with an extra step in the test job run: ls -l node_modules


having similar issues
something to do with symlink being converted into actual files by npm

but it doesn’t explain why it occurred all of a sudden. We were not having this issue during the 2.0 beta.


yeah but for me it works since last week with workflows, caching ans persistent build. And without changing something it gets broken…

So i hoped a circleci member just put a statement in here like —> we deployed a new version … there are changes in “blablubb”.


This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.