Skip to content
This repository has been archived by the owner on May 17, 2019. It is now read-only.

Fix "Client vendor file sourcemap gets compiled" tests #112

Closed
KevinGrandon opened this issue Jan 5, 2018 · 0 comments
Closed

Fix "Client vendor file sourcemap gets compiled" tests #112

KevinGrandon opened this issue Jan 5, 2018 · 0 comments

Comments

@KevinGrandon
Copy link
Contributor

After 959f73e landed there are perma-failures in master CI.

Example failure:

not ok 111 Client vendor file gets compiled
  ---
    operator: ok
    expected: true
    actual:   false
    at: Test.test (/fusion-cli/test/cli/build.js:91:5)
  ...
not ok 112 Client vendor file sourcemap gets compiled
  ---
    operator: ok
    expected: true
    actual:   false
at: Test.test (/fusion-cli/test/cli/build.js:92:5)
KevinGrandon added a commit to KevinGrandon/fusion-cli that referenced this issue Jan 5, 2018
These tests are currently failing in master and creating build failures for unrelated PRs. Let's disable the tests for now and we can work on fixing them in fusionjs#112.
KevinGrandon added a commit to KevinGrandon/fusion-cli that referenced this issue Jan 5, 2018
These tests are currently failing in master and creating build failures for unrelated PRs. Let's disable the tests for now and we can work on fixing them in fusionjs#112.
KevinGrandon added a commit to KevinGrandon/fusion-cli that referenced this issue Jan 5, 2018
These tests are currently failing in master and creating build failures for unrelated PRs. Let's disable the tests for now and we can work on fixing them in fusionjs#112.
KevinGrandon added a commit to KevinGrandon/fusion-cli that referenced this issue Jan 5, 2018
These tests are currently failing in master and creating build failures for unrelated PRs. Let's disable the tests for now and we can work on fixing them in fusionjs#112.
KevinGrandon added a commit that referenced this issue Jan 5, 2018
These tests are currently failing in master and creating build failures for unrelated PRs. Let's disable the tests for now and we can work on fixing them in #112.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant