Git Product home page Git Product logo

Comments (6)

jmhodges avatar jmhodges commented on September 1, 2024

It's just the platform_http_file.bzl load that's the problem, but I can't figure out why.

from rules_webtesting.

jmhodges avatar jmhodges commented on September 1, 2024

Ah, the default visibility in that BUILD.bazel seems to not be public?

So, I also tried adding "browser_repositories" to my other load statement with an arg asking for it to set up chromium for me with browser_repositories(chromium=True).

But Chromium seems to be crashing whole cloth[1] once it gets to the logout part of all of my tests, so maybe that's not actually the supported way to get a browser going?

What's the right way?

[1] From my Go test logs:

2018/11/03 21:40:16 "GET /assets/js/fakestripe.js HTTP/1.1" 200 "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/68.0.3440.0 Safari/537.36"
 2018/11/03 21:40:21.744522 /private/var/tmp/_bazel_jmhodges/ee957dabdee1b1a9e1f2fe90369cf80f/sandbox/darwin-sandbox/1/execroot/founding/bazel-out/darwin-fastbuild/bin/go/svc/howsmyssl-billing/integration_test_chromium-local.runfiles/io_bazel_rules_webtesting/third_party/chromedriver/chromedriver.out/chromedriver has exited: <nil>
2018/11/03 21:40:24.733644 Error shutting down driver: os: process already finished

from rules_webtesting.

DrMarcII avatar DrMarcII commented on September 1, 2024

The actual problem is that I forgot to include @io_bazel_rules_webtesting at the beginning of the load. I have updated the README.

As for the crashing problem, I don't know why that is happening. Using browser_repositories should work (although I don't recommend it as it means you are tied to whatever version of Chromium rules_webtesting in using). Without having the actual test code to play with myself, there is not much I can do to help you.

from rules_webtesting.

jmhodges avatar jmhodges commented on September 1, 2024

Yeah that was it.

For the crash, is there some easy way to get chromedriver to start logging somewhere? I tried with custom_browser and a patching .json with a "--log_file=welp.log" in the "google:wslConfig"->"args" section but that didn't take.

from rules_webtesting.

jmhodges avatar jmhodges commented on September 1, 2024

(Using chrome-external lets the tests pass, but I need to use chromium-local in CI)

from rules_webtesting.

jmhodges avatar jmhodges commented on September 1, 2024

I'm going to close this since the primary problem is handled

from rules_webtesting.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.