I’m trying to use the docker image for tests both on my mac, and also on travis . For a while now the qunit tests have been failing on exactly the same tests, and I can’t figure out why. The steps I’m taking are the same on my mac and on travis: ./bin/docker/boot_dev # Load the Discourse developmen…

Works fine for me on Linux with the latest tests-passed branch checked out: ~/Projects/discourse sudo d/bundle exec rake "qunit:test['200000']" phantomjs /src/vendor/assets/javascripts/run-qunit.js http://localhost:60099/qunit 200000 Unable to access network phantomjs://code/run-qunit.js:34 Puma…

Yeah, it also works fine for me running the tests natively on my mac. And natively on travis it also seems to be fine (judging by discourse’s own CI tests). It’s just the discourse_dev image that seems to be breaking things for me, and I can’t figure out what’s different about it… :confused:

Try installing the latest version of PhantomJS in the image. I believe we’re running an outdated version.

We should get that fixed I thought @Falco posted a new dev image recently? no

I’ll give that a try - thanks :slight_smile: I was under the impression that you guys used the docker image for the internal CI server that runs before pushing to tests_passed? Or is this thread out of date?

The boot_dev is using a somewhat old image, just a sec.

[imagen] david: It’s just the discourse_dev image that seems to be breaking things for me, and I can’t figure out what’s different about it… :confused: Sorry, that’s what I meant. Running the discourse_dev image in docker (in Linux) the tests pass fine for me… I see how I wasn’t as clear as I…

[imagen] LeoMcA: I frequently do d/shutdown_dev, d/reset_db, d/boot_dev cycles, could that be affecting things? Yes, though we should be a bit smarter about checking once a week for a new dev image, or something along those lines.

OK, boot_dev --init will use the latest image: https://github.com/discourse/discourse/commit/2e152f4d39e3b0f46769851d5840b30624d17b39 Be sure to nuke old image first… do docker ps to see if it is running.

Thanks @Falco . That new image certainly initialises quicker now that all the dependencies are up-to-date. When I ran boot_dev --init I got this warning Migrating database... rake aborted! Gem::LoadError: You have already activated rake 12.0.0, but your Gemfile requires rake 11.3.0. Prepending `bun…

QUnit tests won't pass in discourse_dev docker image

Development

Falco (Falco) 25 Julio, 2017 15:41 20

Awesome, just tested this locally and it’s working. Merging the PR.

Tema		Respuestas	Vistas
Qunit in Docker Development	6	1715	14 Mayo 2020
Plugin QUnit tests are not running as part of rake qunit:test Development	7	2183	17 Julio 2017
Issue regarding Docker development image Development	25	6725	27 Julio 2017
RSpec tests won't pass on discourse_dev docker image Development	4	1998	26 Abril 2017
Developing Discourse Plugins - Part 6 - Add acceptance tests Developer Guides testing , plugin-guides , tutorial	32	18074	2 Junio 2022

QUnit tests won't pass in discourse_dev docker image

Temas relacionados