Skip to content

issues Search Results · repo:pandas-dev/asv-runner language:Python

Filter by

18 results
 (73 ms)

18 results

inpandas-dev/asv-runner (press backspace or delete to remove)

Commit Range Subsequent benchmarks may have skipped some commits. The link above lists the commits that are between the two benchmark runs where the regression was identified. - [ ] algorithms.Factorize.time_factorize ...
  • github-actions[bot]
  • 1
  • Opened 
    7 days ago
  • #50

Commit Range Subsequent benchmarks may have skipped some commits. The link above lists the commits that are between the two benchmark runs where the regression was identified. - [ ] frame_ctor.FromDictwithTimestamp.time_dict_with_timestamp_offsets ...
  • github-actions[bot]
  • Opened 
    18 days ago
  • #48

Commit Range Subsequent benchmarks may have skipped some commits. The link above lists the commits that are between the two benchmark runs where the regression was identified. - [ ] groupby.String.time_str_func ...
  • github-actions[bot]
  • 1
  • Opened 
    on Mar 21
  • #47

Commit Range Subsequent benchmarks may have skipped some commits. The link above lists the commits that are between the two benchmark runs where the regression was identified. - [ ] series_methods.Map.time_map ...
  • github-actions[bot]
  • 1
  • Opened 
    on Mar 20
  • #46

Commit Range Subsequent benchmarks may have skipped some commits. The link above lists the commits that are between the two benchmark runs where the regression was identified. - [ ] groupby.GroupByCythonAgg.time_frame_agg ...
  • github-actions[bot]
  • 3
  • Opened 
    on Feb 20
  • #45

Commit Range Subsequent benchmarks may have skipped some commits. The link above lists the commits that are between the two benchmark runs where the regression was identified. - [ ] groupby.Cumulative.time_frame_transform ...
  • github-actions[bot]
  • 1
  • Opened 
    on Feb 6
  • #42

Commit Range Subsequent benchmarks may have skipped some commits. The link above lists the commits that are between the two benchmark runs where the regression was identified. - [ ] groupby.GroupByCythonAggEaDtypes.time_frame_agg ...
  • github-actions[bot]
  • Opened 
    on Jan 3
  • #25

Commit Range Subsequent benchmarks may have skipped some commits. The link above lists the commits that are between the two benchmark runs where the regression was identified. - [ ] groupby.GroupByCythonAggEaDtypes.time_frame_agg ...
  • github-actions[bot]
  • Opened 
    on Jan 3
  • #24

Commit Range Subsequent benchmarks may have skipped some commits. The link above lists the commits that are between the two benchmark runs where the regression was identified. - [ ] groupby.GroupByCythonAgg.time_frame_agg ...
  • github-actions[bot]
  • Opened 
    on Jan 2
  • #23

Commit Range Subsequent benchmarks may have skipped some commits. The link above lists the commits that are between the two benchmark runs where the regression was identified. - [ ] groupby.GroupByCythonAgg.time_frame_agg ...
  • github-actions[bot]
  • Opened 
    on Jan 2
  • #22
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue search results · GitHub