GITHUB . COM {}

Matching Content Categories {📚}

• Education
• DIY & Home Improvement
• Transportation

Content Management System {📝}

What CMS is github.com built with?

Github.com relies on WORDPRESS.

Traffic Estimate {📈}

What is the average monthly size of github.com audience?

🚀🌠 Tremendous Traffic: 10M - 20M visitors per month


Based on our best estimate, this website will receive around 10,000,019 visitors per month in the current month.
However, some sources were not loaded, we suggest to reload the page to get complete results.

check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush

How Does Github.com Make Money? {💸}

Subscription Packages {💳}

How Much Does Github.com Make? {💰}

Subscription Packages {💳}

Prices on github.com are in US Dollars ($). They range from $4.00/month to $21.00/month.
We estimate that the site has approximately 4,989,889 paying customers.
The estimated monthly recurring revenue (MRR) is $20,957,532.
The estimated annual recurring revenues (ARR) are $251,490,385.

Wordpress Themes and Plugins {🎨}

What WordPress theme does this site use?

It is strange but we were not able to detect any theme on the page.

What WordPress plugins does this website use?

It is strange but we were not able to detect any plugins on the page.

Keywords {🔍}

pytest, python, xdist, test, fixtures, tests, footestpytest, fail, linux, commented, collection, order, aldanor, passed, ronnypfannschmidt, mentioned, sign, nondeterministic, makes, issue, related, cwd, hometestfoo, gcc, red, type, plugin, pull, requests, projects, deterministic, pytestxdist, fixture, def, member, nicoddemus, hectorv, navigation, code, issues, actions, security, parametrized, fixturerequest, return, requestparam, pass, works, session, starts,

Topics {✒️}

test_1[bar-bar] foo/test_1 test_1[bar-bar] -foo/test_1 test_1[foo-bar] +foo/test_1 test_1[bar-foo] -foo/test_1 test_1[foo-foo] +foo/test_1 loadscheduling foo/test_1 test_1[2-3] foo/test_1 test_1[1-3] foo/test_1 test_1[1-4] foo/test_1 ronnypfannschmidt mentioned test collection mechanism duplicate test ids legacy test suite hectorv edits assigned labels plugin python hash-seed pytest-xdist 2 pytest-xdist==1 comment metadata assignees parametrized fixtures type projects distribute tests latest pytest projects milestone session-scoped aldanor changed params=['foo' test script sort collected code xdist related refi64 mentioned issue tests 30 -- pytest-2 pytest 2 11 pytest==2 fixtures addressed type fail 'bar'] 'foo'] gw1 test test xdist xdist-1 params=['baz' red hat 4

Payment Methods {📊}

• Braintree

Questions {❓}

• Already have an account?
• By the way, I wonder why should it care about the order at all if the sets are the same?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:Non-deterministic test collection order for deterministic fixtures makes xdist fail
      articleBody:Issues that may be related: #437, #594, #596, #669. `pytest-xdist` seems to fail sometimes because it orders parametrized fixtures differently -- e.g., when a fixture depends on two or more parametrized fixtures. Using the latest pytest and pytest-xdist on Python 3.4 with this test script: ``` python import pytest @pytest.fixture(params=['foo', 'bar']) def fixture1(request): return request.param @pytest.fixture(params=['baz', 'foo']) def fixture2(request): return request.param def test_1(fixture1, fixture2): pass ``` Sometimes it works: ``` sh $ py.test -v -n 2 ============================ test session starts ============================ platform linux -- Python 3.4.3 -- py-1.4.30 -- pytest-2.7.2 -- /home/test/env/bin/python3 plugins: xdist [gw0] linux Python 3.4.3 cwd: /home/test/foo [gw1] linux Python 3.4.3 cwd: /home/test/foo [gw1] Python 3.4.3 [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] [gw0] Python 3.4.3 [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] gw0 [4] / gw1 [4] scheduling tests via LoadScheduling foo/test_1.py::test_1[2-3] foo/test_1.py::test_1[1-3] [gw0] PASSED foo/test_1.py::test_1[2-3] [gw1] PASSED foo/test_1.py::test_1[1-3] foo/test_1.py::test_1[1-4] foo/test_1.py::test_1[2-4] [gw0] PASSED foo/test_1.py::test_1[2-4] [gw1] PASSED foo/test_1.py::test_1[1-4] ========================= 4 passed in 0.60 seconds ========================== ``` And sometimes it doesn't (because it chose to sort the fixtures by the second parameter first for some reason): ``` sh $ py.test -v -n 2 ============================ test session starts ============================ platform linux -- Python 3.4.3 -- py-1.4.30 -- pytest-2.7.2 -- /home/test/env/bin/python3 plugins: xdist [gw0] linux Python 3.4.3 cwd: /home/test/foo [gw1] linux Python 3.4.3 cwd: /home/test/foo [gw1] Python 3.4.3 [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] [gw0] Python 3.4.3 [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] gw0 [4] / gw1 [4] scheduling tests via LoadScheduling collecting 0 items / 1 errors ================================== ERRORS =================================== ___________________________ ERROR collecting gw0 ____________________________ Different tests were collected between gw1 and gw0. The difference is: --- gw1 +++ gw0 @@ -1,4 +1,4 @@ foo/test_1.py::test_1[foo-foo] +foo/test_1.py::test_1[foo-bar] +foo/test_1.py::test_1[bar-bar] foo/test_1.py::test_1[bar-foo] -foo/test_1.py::test_1[bar-bar] -foo/test_1.py::test_1[foo-bar] ========================== 1 error in 0.65 seconds ========================== ```
      author:
         url:https://github.com/aldanor
         type:Person
         name:aldanor
      datePublished:2015-08-06T15:11:24.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:13
      url:https://github.com/920/pytest/issues/920
      context:https://schema.org
      headline:Non-deterministic test collection order for deterministic fixtures makes xdist fail
      articleBody:Issues that may be related: #437, #594, #596, #669. `pytest-xdist` seems to fail sometimes because it orders parametrized fixtures differently -- e.g., when a fixture depends on two or more parametrized fixtures. Using the latest pytest and pytest-xdist on Python 3.4 with this test script: ``` python import pytest @pytest.fixture(params=['foo', 'bar']) def fixture1(request): return request.param @pytest.fixture(params=['baz', 'foo']) def fixture2(request): return request.param def test_1(fixture1, fixture2): pass ``` Sometimes it works: ``` sh $ py.test -v -n 2 ============================ test session starts ============================ platform linux -- Python 3.4.3 -- py-1.4.30 -- pytest-2.7.2 -- /home/test/env/bin/python3 plugins: xdist [gw0] linux Python 3.4.3 cwd: /home/test/foo [gw1] linux Python 3.4.3 cwd: /home/test/foo [gw1] Python 3.4.3 [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] [gw0] Python 3.4.3 [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] gw0 [4] / gw1 [4] scheduling tests via LoadScheduling foo/test_1.py::test_1[2-3] foo/test_1.py::test_1[1-3] [gw0] PASSED foo/test_1.py::test_1[2-3] [gw1] PASSED foo/test_1.py::test_1[1-3] foo/test_1.py::test_1[1-4] foo/test_1.py::test_1[2-4] [gw0] PASSED foo/test_1.py::test_1[2-4] [gw1] PASSED foo/test_1.py::test_1[1-4] ========================= 4 passed in 0.60 seconds ========================== ``` And sometimes it doesn't (because it chose to sort the fixtures by the second parameter first for some reason): ``` sh $ py.test -v -n 2 ============================ test session starts ============================ platform linux -- Python 3.4.3 -- py-1.4.30 -- pytest-2.7.2 -- /home/test/env/bin/python3 plugins: xdist [gw0] linux Python 3.4.3 cwd: /home/test/foo [gw1] linux Python 3.4.3 cwd: /home/test/foo [gw1] Python 3.4.3 [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] [gw0] Python 3.4.3 [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] gw0 [4] / gw1 [4] scheduling tests via LoadScheduling collecting 0 items / 1 errors ================================== ERRORS =================================== ___________________________ ERROR collecting gw0 ____________________________ Different tests were collected between gw1 and gw0. The difference is: --- gw1 +++ gw0 @@ -1,4 +1,4 @@ foo/test_1.py::test_1[foo-foo] +foo/test_1.py::test_1[foo-bar] +foo/test_1.py::test_1[bar-bar] foo/test_1.py::test_1[bar-foo] -foo/test_1.py::test_1[bar-bar] -foo/test_1.py::test_1[foo-bar] ========================== 1 error in 0.65 seconds ========================== ```
      author:
         url:https://github.com/aldanor
         type:Person
         name:aldanor
      datePublished:2015-08-06T15:11:24.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:13
      url:https://github.com/920/pytest/issues/920
Person:
      url:https://github.com/aldanor
      name:aldanor
      url:https://github.com/aldanor
      name:aldanor
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:13
      interactionType:https://schema.org/CommentAction
      userInteractionCount:13

External Links {🔗}(2)

• What's the revenue for https://github.blog?
• What's https://www.githubstatus.com/'s gross income?

Analytics and Tracking {📊}

• Site Verification - Google

Libraries {📚}

• Clipboard.js
• D3.js
• Lodash

Emails and Hosting {✉️}

Mail Servers:

• aspmx.l.google.com
• alt1.aspmx.l.google.com
• alt2.aspmx.l.google.com
• alt3.aspmx.l.google.com
• alt4.aspmx.l.google.com

Name Servers:

• dns1.p08.nsone.net
• dns2.p08.nsone.net
• dns3.p08.nsone.net
• dns4.p08.nsone.net
• ns-1283.awsdns-32.org
• ns-1707.awsdns-21.co.uk
• ns-421.awsdns-52.com
• ns-520.awsdns-01.net