GITHUB . COM {}

Matching Content Categories {📚}

• Automotive
• Technology & Computing
• Animals & Wildlife

Content Management System {📝}

What CMS is github.com built with?

Github.com is powered by 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 5,013,426 paying customers.
The estimated monthly recurring revenue (MRR) is $21,056,387.
The estimated annual recurring revenues (ARR) are $252,676,649.

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 {🔍}

durationsmin, durations, displayed, top, issue, duration, pytest, julianjvn, behavior, zachd, sign, options, work, type, pull, projects, problem, documentation, effect, bug, durationsn, durationsminx, added, fix, navigation, solutions, code, requests, actions, security, override, closed, feature, verbose, default, specific, option, theyre, explicitly, precedence, addressed, commented, compatibility, github, milestone, footer, skip, content, menu, product,

Topics {✒️}

zac-hd added pytest/src/_pytest/runner custom --durations-min values displayed alternative solutions julianjvn/durations-min-precedence assigned labels type type projects comment metadata assignees addressed type personal information `-vv` projects milestone code julianjvn mentioned 3eba628 fix durations-min durations-min 0 durations-min= durations-min=0 issue full output test failures debugging purposes asymmetric/inconsistent specific option easily restored sounds good milestone relationships displayed describe bug problem pytest pytest pytest' pytest-8 github previous behavior documentation bug 5037c7f sign default behavior vv precedence durations durations durations= displayed problem default behavior documentation sign duration ≥ 0

Payment Methods {📊}

• Braintree

Questions {❓}

• Already have an account?
• What's the problem this feature will solve?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:`-vv` should not override `--durations-min`
      articleBody:<!-- Thanks for suggesting a feature! Quick check-list while suggesting features: --> #### What's the problem this feature will solve? <!-- What are you trying to do, that you are unable to achieve with pytest as it currently stands? --> I'd like pytest to give the full output on test failures for debugging purposes (by specifying `-vv`) while still being able to print the durations of tests and fixtures that exceed a given threshold (by using `--durations-min`). * It's not documented neither in `pytest --help` nor in the [documentation](https://docs.pytest.org/en/stable/how-to/usage.html#profiling-test-execution-duration) that `--durations-min` has no effect if `-vv` is specified. I had to look at pytest's code to learn this: https://github.com/pytest-dev/pytest/blob/3ef3c2d83498f550e8e678e209c6739dccfabe55/src/_pytest/runner.py#L93 The documentation only says the default behavior is equivalent to `--durations-min 0.005` to when `-vv` is not specified. It does not say custom `--durations-min` values have no effect if `-vv` is specified. So, if this issue is not implemented, it is at least a documentation bug. * It's asymmetric/inconsistent that `--durations` still has effect if `-vv` specified, but `--durations-min` does not. * It's unexpected that a more specific option like `--durations-min` is overridden by a less specific option like `--verbose`. The options currently work like this, depending if they're specified (Y) or not (N) or if it doesn't matter whether they're specified or not (*): | `--durations=N` | `--durations-min=X` | `-vv` | Behavior| |-|-|-|-| |N|*|*|No durations are displayed| |Y|N|N|Top _N_ durations with duration &ge; 0.005s are displayed| |Y|Y|N|Top _N_ durations with duration &ge; _X_ are displayed| |Y|*|Y|Top _N_ durations are displayed| #### Describe the solution you'd like <!-- A clear and concise description of what you want to happen. --> If `--durations-min` is explicitly specified, it should have precedence over `-vv`. The options could work like this: | `--durations=N` | `--durations-min=X` | `-vv` | Behavior| |-|-|-|-| |N|*|*|No durations are displayed| |Y|N|N|Top _N_ durations with duration &ge; 0.005s are displayed| |Y|N|Y|Top _N_ durations are displayed| |Y|Y|*|Top _N_ durations with duration &ge; _X_ are displayed| <!-- Provide examples of real-world use cases that this would enable and how it solves the problem described above. --> #### Alternative Solutions <!-- Have you tried to workaround the problem using a pytest plugin or other tools? Or a different approach to solving this issue? Please elaborate here. --> Another possibility that would work for me is removing the feature that `-vv` changes the default value of `--durations-min`, i.e., the options would be decoupled. The previous behavior could be easily restored with `--durations-min=0`. The options would then work like this: | `--durations=N` | `--durations-min=X` | `-vv` | Behavior| |-|-|-|-| |N|*|*|No durations are displayed| |Y|N|*|Top _N_ durations with duration &ge; 0.005s are displayed| |Y|Y|*|Top _N_ durations with duration &ge; _X_ are displayed| #### Additional context <!-- Add any other context, links, etc. about the feature here. --> &mdash;
      author:
         url:https://github.com/JulianJvn
         type:Person
         name:JulianJvn
      datePublished:2024-11-04T12:08:01.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:2
      url:https://github.com/12938/pytest/issues/12938
      context:https://schema.org
      headline:`-vv` should not override `--durations-min`
      articleBody:<!-- Thanks for suggesting a feature! Quick check-list while suggesting features: --> #### What's the problem this feature will solve? <!-- What are you trying to do, that you are unable to achieve with pytest as it currently stands? --> I'd like pytest to give the full output on test failures for debugging purposes (by specifying `-vv`) while still being able to print the durations of tests and fixtures that exceed a given threshold (by using `--durations-min`). * It's not documented neither in `pytest --help` nor in the [documentation](https://docs.pytest.org/en/stable/how-to/usage.html#profiling-test-execution-duration) that `--durations-min` has no effect if `-vv` is specified. I had to look at pytest's code to learn this: https://github.com/pytest-dev/pytest/blob/3ef3c2d83498f550e8e678e209c6739dccfabe55/src/_pytest/runner.py#L93 The documentation only says the default behavior is equivalent to `--durations-min 0.005` to when `-vv` is not specified. It does not say custom `--durations-min` values have no effect if `-vv` is specified. So, if this issue is not implemented, it is at least a documentation bug. * It's asymmetric/inconsistent that `--durations` still has effect if `-vv` specified, but `--durations-min` does not. * It's unexpected that a more specific option like `--durations-min` is overridden by a less specific option like `--verbose`. The options currently work like this, depending if they're specified (Y) or not (N) or if it doesn't matter whether they're specified or not (*): | `--durations=N` | `--durations-min=X` | `-vv` | Behavior| |-|-|-|-| |N|*|*|No durations are displayed| |Y|N|N|Top _N_ durations with duration &ge; 0.005s are displayed| |Y|Y|N|Top _N_ durations with duration &ge; _X_ are displayed| |Y|*|Y|Top _N_ durations are displayed| #### Describe the solution you'd like <!-- A clear and concise description of what you want to happen. --> If `--durations-min` is explicitly specified, it should have precedence over `-vv`. The options could work like this: | `--durations=N` | `--durations-min=X` | `-vv` | Behavior| |-|-|-|-| |N|*|*|No durations are displayed| |Y|N|N|Top _N_ durations with duration &ge; 0.005s are displayed| |Y|N|Y|Top _N_ durations are displayed| |Y|Y|*|Top _N_ durations with duration &ge; _X_ are displayed| <!-- Provide examples of real-world use cases that this would enable and how it solves the problem described above. --> #### Alternative Solutions <!-- Have you tried to workaround the problem using a pytest plugin or other tools? Or a different approach to solving this issue? Please elaborate here. --> Another possibility that would work for me is removing the feature that `-vv` changes the default value of `--durations-min`, i.e., the options would be decoupled. The previous behavior could be easily restored with `--durations-min=0`. The options would then work like this: | `--durations=N` | `--durations-min=X` | `-vv` | Behavior| |-|-|-|-| |N|*|*|No durations are displayed| |Y|N|*|Top _N_ durations with duration &ge; 0.005s are displayed| |Y|Y|*|Top _N_ durations with duration &ge; _X_ are displayed| #### Additional context <!-- Add any other context, links, etc. about the feature here. --> &mdash;
      author:
         url:https://github.com/JulianJvn
         type:Person
         name:JulianJvn
      datePublished:2024-11-04T12:08:01.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:2
      url:https://github.com/12938/pytest/issues/12938
Person:
      url:https://github.com/JulianJvn
      name:JulianJvn
      url:https://github.com/JulianJvn
      name:JulianJvn
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:2
      interactionType:https://schema.org/CommentAction
      userInteractionCount:2

External Links {🔗}(3)

• What are the earnings of https://github.blog?
• What's the monthly money flow for https://docs.pytest.org/en/stable/how-to/usage.html#profiling-test-execution-duration?
• How much income does https://www.githubstatus.com/ have?

Analytics and Tracking {📊}

• Site Verification - Google

Libraries {📚}

• Clipboard.js
• D3.js
• GSAP
• 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