Hi I am learning to use cucumberjs on ember.
Using yeoman for it.
when I try to run cucumberjs from command prompt I get below error
$ grunt cucumberjs
No "cucumberjs" targets found.Warning: Task "cucumberjs" failed. Use --force to continue.
Aborted due to warnings.
Related
I am currently trying to set up some system testing for my rails web application (using Rails version 7.0.3.1)
When running rails test:system to run a single system test I had written, I am getting the below setup-related error
Command '/usr/bin/chromium-browser' requires the chromium snap to be installed.
Please install it with:
snap install chromium
.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/webdrivers-5.0.0/lib/webdrivers/system.rb:190:in `call': Failed to make system call: ["/usr/bin/chromium-browser", "--product-version"] (RuntimeError)
And then, when I try to run
snap install chromium
as suggested by the error I am getting back, I then run into the following error
error: cannot communicate with server: Post http://localhost/v2/snaps/chromium: dial unix /run/snapd.socket: connect: no such file or directory
I am lost as to how to move forward with this issue, which is preventing me from being able to run any system tests. There also seem to not be too many related issues online currently that applied to this case. Any help/ suggestions on where to look to further troubleshoot this error would be greatly appreciated.
Try to install it from the Google, depends on your ubuntu versions:
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
apt install ./google-chrome-stable_current_amd64.deb
I'm at my wit's end. I'm trying to push a new rails 5 application to heroku, and i keep getting the error message "yarn executable was not detected in system" whenever the rake assets:precompile starts.
I have followed all of the instructions from this post, the installation instructions from the yarn site, and even tried the solutions from this post.
Every time that I run yarn --version from the command line, it looks as if it's installed perfectly fine, and I get the following result: 1.7.0
If anybody else can recommend something else to try, I would greatly appreciate it.
Thanks!
I am trying to compile tensorflow in a bit difficult environment (Centos 6.2 with a load of "own" compilations).
A lot of problems I have solved already, but the one baffling me is a SWIG error. I run with "--verbose_failures" and I can see the command that bazel tries to run:
(cd /home/../.cache/bazel/_bazel../[long-hexa]/execroot/org_tensorflow && \
exec env - \
bazel-out/host/bin/external/swig/swig -c++ ...
It fails with "Exit 1: swig failed: error executing command.
However, when I cd to the mentioned directory and run the mentioned bazel-out/../swig command it succeeds! What I have understood is that this probably is a problem of bazel trying to sanitize the environment.
How can I go to debug this? Is there a way to show what environment variables bazel is using?
I'm running a composer install after a docker-compose up and am unable to get the CI process to continue. All of the output shows the install was successful except for travis' interpretation of the output. See https://travis-ci.org/BibleBowl/account/builds/125161543#L1454
Is there something I can do to show more verbose output?
I'm following the sample Yeoman workflow listed on yeoman.io:
npm install -g generator-angular generator-karma # install generators
yo angular # scaffold out a AngularJS project
bower install angular-ui # install a dependency for your project from Bower
*grunt test # test your app
grunt server # preview your app
grunt # build the application for deployment
Everything works great except the grunt test command:
C:\yeoman2>grunt test
(logging omitted for brevity)
Running "connect:test" (connect) task
Starting connect web server on localhost:9000.
Running "karma:unit" (karma) task
Fatal error: listen EACCES
I haven't updated my gruntfile or made any other modifications to the configs. Has anyone seen this EACCESS error before? I'm on Windows 8, with a fresh node install.
This was happening because the karma server was running on port 8080. I changed it (in karma.conf.js) to 9999 and all is well.