aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/bin/export-to-postgresql-record
blob: 221d66e05713bbc1f97d4f10c41838ac31820bdb (plain) (blame) 
1
2
3
4
5
6
7
8

#!/bin/bash

#
# export perf data to a postgresql database. Can cover
# perf ip samples (excluding the tracepoints). No special
# record requirements, just record what you want to export.
#
perf record $@
generated by cgit v1.2.3 (git 2.39.1) at 2025-12-20 17:24:11 +0000
Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-30Second batchJunio C Hamano1-0/+5 Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-29Git 2.29.2v2.29.2Junio C Hamano3-2/+14 Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-27First batchJunio C Hamano1-0/+38 Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-26other small fixes for 2.29.2Junio C Hamano2-1/+23 Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-23rebase: fix broken email with --committer-date-is-author-dateJeff King2-5/+5 Commit 7573cec52c (rebase -i: support --committer-date-is-author-date, 2020-08-17) copied the committer ident-parsing code from builtin/am.c. And in doing so, it copied a bug in which we always set the email to an empty string. We fixed the version in git-am in the previous commit; this commit fixes the copied code. Reported-by: VenomVendor <info@venomvendor.com> Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-23am: fix broken email with --committer-date-is-author-dateJeff King2-3/+3 Commit e8cbe2118a (am: stop exporting GIT_COMMITTER_DATE, 2020-08-17) rewrote the code for setting the committer date to use fmt_ident(), rather than setting an environment variable and letting commit_tree() handle it. But it introduced two bugs: - we use the author email string instead of the committer email - when parsing the committer ident, we used the wrong variable to compute the length of the email, resulting in it always being a zero-length string This commit fixes both, which causes our test of this option via the rebase "apply" backend to now succeed. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-23t3436: check --committer-date-is-author-date result more carefullyJeff King1-7/+7 After running "rebase --committer-date-is-author-date", we confirm that the committer date is the same as the author date. However, we don't look at any other parts of the committer ident line to make sure we didn't screw them up. And indeed, there are a few bugs here. Depending on the rebase backend in use, we may accidentally use the author email instead of the committer's, or even an empty string. Let's teach our test_ctime_is_atime helper to check the committer name and email, which reveals several failing tests. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-22Git 2.29.1v2.29.1Junio C Hamano3-2/+13 Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-22t7102: prepare expected output inside test_expect_* blockJunio C Hamano1-123/+121 That way we can notice if there is a breakage/bug in the parts of the test that prepare the expected outcome, which is how modern tests are arranged. Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-22t7201: put each command on a separate lineCharvi Mendiratta1-8/+18 Modern practice is to avoid multiple commands per line, and instead place each command on its own line. Signed-off-by: Charvi Mendiratta <charvi077@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-22t7201: use 'git -C' to avoid subshellCharvi Mendiratta1-8/+2 Signed-off-by: Charvi Mendiratta <charvi077@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-22t7102,t7201: remove whitespace after redirect operatorCharvi Mendiratta2-21/+21 According to Documentation/CodingGuidelines, redirect operator is written with space before, but no space after them. Let's remove these whitespaces after redirect operators. Signed-off-by: Charvi Mendiratta <charvi077@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-21SKIP_DASHED_BUILT_INS: do not skip the bin/ programsJohannes Schindelin1-9/+6 The idea of the `SKIP_DASHED_BUILT_INS` option is to stop hard-linking the built-in commands as separate executables. The patches to do that specifically excluded the three commands `receive-pack`, `upload-archive` and `upload-pack`, though: these commands are expected to be present in the `PATH` in their dashed form on the server side of any fetch/push. However, due to an oversight by myself, even if those commands were still hard-linked, they were not installed into `bin/`. Noticed-by: Michael Forney <mforney@mforney.org> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Reviewed-by: Taylor Blau <me@ttaylorr.com> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-20t7102,t7201: remove unnecessary blank spaces in test bodyCharvi Mendiratta2-34/+0 t7102 and t7201 still follow the old style of having blank lines around test body, which is not consistence with our current practice. Let's remove those unnecessary blank lines. Signed-off-by: Charvi Mendiratta <charvi077@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-20t7101,t7102,t7201: modernize test formattingCharvi Mendiratta3-65/+56 Some tests in these scripts are formatted using a very old style: test_expect_success \ 'title' \ 'body line 1 && body line 2' Updating the formatting to the modern style: test_expect_success 'title' ' body line 1 && body line 2 ' Signed-off-by: Charvi Mendiratta <charvi077@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-20filter-branch doc: fix filter-repo typoChristian Couder1-1/+1 The name of the tool is 'git-filter-repo' not 'git-repo-filter'. Signed-off-by: Christian Couder <chriscool@tuxfamily.org> Reviewed-by: Elijah Newren <newren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-19Git 2.29v2.29.0Junio C Hamano1-1/+1 Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-18t7518: fix flaky grep invocationElijah Newren1-1/+1 t7518.1 added in commit 862e80a413 ("ident: handle NULL email when complaining of empty name", 2017-02-23), was trying to make sure that the test with an empty ident did not segfault and did not result in glibc quiety translating a NULL pointer into a name of "(null)". It did the latter by ensuring that a grep for "null" didn't appear in the output, but on one automatic CI run I observed the following output: fatal: empty ident name (for <runner@fv-az128-670.gcliasfzo2nullsdbrimjtbyhg.cx.internal.cloudapp.net>) not allowed Note that 'null' appears as a substring of the domain name, found within 'gcliasfzo2nullsdbrimjtbyhg'. Tighten the test by searching for "(null)" rather than "null". Signed-off-by: Elijah Newren <newren@gmail.com> Reviewed-by: Taylor Blau <me@ttaylorr.com> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-18t0000: use test_path_is_file instead of "test -f"Caleb Tillman1-1/+1 Signed-off-by: Caleb Tillman <caleb.tillman@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-18l10n: zh_CN: for git v2.29.0 l10n round 1 and 2Jiang Xin1-3432/+3788 Translate 124 new messages (5013t0f0u) for git 2.29.0. Reviewed-by: 依云 <lilydjwg@gmail.com> Reviewed-by: Fangyi Zhou <me@fangyi.io> Signed-off-by: Jiang Xin <worldhello.net@gmail.com> 2020-10-17git-gui: blame: prevent tool tips from sticking around after Command-TabStefan Haller1-0/+1 On Mac, tooltips are not automatically removed when a window loses focus. Furthermore, mouse-move events are only dispatched to the active window, which means that if we Command-tab to another application while a tool tip is showing, the tool tip will stay there forever (in front of other applications). So we must hide it manually when we lose focus. Do this unconditionally here (i.e. without if {[is_MacOSX]}); it shouldn't hurt on other platforms, even though they don't seem to have this problem. Signed-off-by: Stefan Haller <stefan@haller-berlin.de> Signed-off-by: Pratyush Yadav <me@yadavpratyush.com> 2020-10-15Git 2.29-rc2v2.29.0-rc2Junio C Hamano1-1/+1 Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-15l10n: de.po: Update German translation for Git 2.29.0Matthias Rüster1-3452/+3817 Reviewed-by: Ralf Thielow <ralf.thielow@gmail.com> Reviewed-by: Phillip Szelat <phillip.szelat@gmail.com> Signed-off-by: Matthias Rüster <matthias.ruester@gmail.com> 2020-10-13l10n: vi(5013t): Updated translation for v2.29.0 rd2Tran Ngoc Quan1-3432/+3869 Signed-off-by: Tran Ngoc Quan <vnwildman@gmail.com> 2020-10-12ci: make the "skip-if-redundant" check more defensiveJohannes Schindelin1-27/+31 In 7d78d5fc1a9 (ci: skip GitHub workflow runs for already-tested commits/trees, 2020-10-08), we added a check that determines whether there is already a workflow run for the given commit (or at least tree), and if found, skips the current run. We just worked around an issue with this check where older runs might unexpectedly miss the `head_commit` attribute. Let's be even more defensive by catching all kinds of exceptions, logging them as warnings, and continue the run without skipping it (after all, if the check fails, we _want_ to continue with the run). This commit is best viewed with the diff option `-w` because it increases the indentation level of the GitHub Action script by two spaces, surrounding it by a `try ... catch` construct. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-12ci: work around old records of GitHub runsJohannes Schindelin1-1/+1 Apparently older GitHub runs at least _sometimes_ lack information about the `head_commit` (and therefore the `ci-config` check will fail with "TypeError: Cannot read property 'tree_id' of null") in the check added in 7d78d5fc1a9 (ci: skip GitHub workflow runs for already-tested commits/trees, 2020-10-08). Let's work around this by adding a defensive condition. Reported-by: Philippe Blain <levraiphilippeblain@gmail.com> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-12line-log: handle deref_tag() returning NULLRené Scharfe1-1/+1 Signed-off-by: René Scharfe <l.s.r@web.de> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-12blame: handle deref_tag() returning NULLRené Scharfe2-3/+5 Signed-off-by: René Scharfe <l.s.r@web.de> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-12grep: handle deref_tag() returning NULLRené Scharfe1-0/+11 deref_tag() can return NULL. Exit gracefully in that case instead of blindly dereferencing the return value. .name shouldn't ever be NULL, but grep_object() handles that case explicitly, so let's be defensive here as well and show the broken object's ID if it happens to lack a name after all. Signed-off-by: René Scharfe <l.s.r@web.de> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-12worktree: teach `list` to annotate locked worktreeRafael Silva3-3/+17 The "git worktree list" shows the absolute path to the working tree, the commit that is checked out and the name of the branch. It is not immediately obvious which of the worktrees, if any, are locked. "git worktree remove" refuses to remove a locked worktree with an error message. If "git worktree list" told which worktrees are locked in its output, the user would not even attempt to remove such a worktree, or would realize that "git worktree remove -f -f <path>" is required. Teach "git worktree list" to append "locked" to its output. The output from the command becomes like so: $ git worktree list /path/to/main abc123 [master] /path/to/worktree 456def (detached HEAD) /path/to/locked-worktree 123abc (detached HEAD) locked Helped-by: Junio C Hamano <gitster@pobox.com> Helped-by: Eric Sunshine <sunshine@sunshineco.com> Signed-off-by: Rafael Silva <rafaeloliveira.cs@gmail.com> Reviewed-by: Eric Sunshine <sunshine@sunshineco.com> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-12Makefile: remove the unused variable TAR_DIST_EXTRA_OPTSRené Scharfe1-3/+0 Signed-off-by: René Scharfe <l.s.r@web.de> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-12Makefile: use git init/add/commit/archive for dist-docRené Scharfe1-3/+11 Reduce the dependency on external tools by generating the distribution archives for HTML documentation and manpages using git commands instead of tar. This gives the archive entries the same meta data as those in the dist archive for binaries. Signed-off-by: René Scharfe <l.s.r@web.de> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-10-12l10n: pt_PT: make on po/pt_PT.poDaniel Santos1-5136/+14811 Pull from the language Coordenator repository and `make` done at the top-level directory. Signed-off-by: Daniel Santos <hello@brighterdan.com> 2020-10-12l10n: Portuguese translation team has changed. Wohoo!Daniel Santos1-3/+2 I am excited. Because I like a lot languages, and because I believe this is the way to contribute to a large number of Portuguese speaking person. Jiang Xin and last Portuguese team gave me the lead. Thank you very much. Honored to be a part of such a project. Signed-off-by: Daniel Santos <hello@brighterdan.com> 2020-10-11l10n: bg.po: Updated Bulgarian translation (5013t)Alexander Shopov1-3579/+4205 Signed-off-by: Alexander Shopov <ash@kambanaria.org> 2020-10-11l10n: sv.po: Update Swedish translation (5013t0f0u)Peter Krefting1-3429/+3843 Signed-off-by: Peter Krefting <peter@softwolves.pp.se> 2020-10-11l10n: it.po: update the Italian translationAlessandro Menti1-141/+141 Update the Italian translation for Git 2.29.0, round 2. Signed-off-by: Alessandro Menti <alessandro.menti@alessandromenti.it> 2020-10-10l10n: tr: v2.29.0 round 2Emir Sarı1-129/+131 Signed-off-by: Emir Sarı <bitigchi@me.com> 2020-10-10l10n: zh_TW.po: v2.29.0 round 2 (2 untranslated)pan934121-3425/+3892 Signed-off-by: pan93412 <pan93412@gmail.com> 2020-10-10l10n: fr: v2.29.0 rnd 2Jean-Noël Avila1-142/+174 Signed-off-by: Jean-Noël Avila <jn.avila@free.fr> 2020-10-10l10n: git.pot: v2.29.0 round 2 (1 new, 1 removed)Jiang Xin1-116/+116 Generate po/git.pot from v2.29.0-rc1 for git v2.29.0 l10n round 2. Signed-off-by: Jiang Xin <worldhello.net@gmail.com>