profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/wanders/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

spaam/svtplay-dl 564

Small command-line program to download videos from some streaming sites.

wanders/blowrak 3

Blowrak keyboard layout

wanders/llvm 3

Mirror of official llvm git repository located at http://llvm.org/git/llvm. Updated hourly.

wanders/scu 3

Simple C Unit Test Framework

wanders/chrome-buildbot-autoscroll 2

Chrome extension to automatically scroll log files.

wanders/dotfiles-emacs 2

My emacs-init.org file that creates my init.el

wanders/zappa-alg 2

Application Level Gateway for telia "zappa"

wanders/android-bankdroid 1

A swedish banking application for your Android device.

wanders/buildbot-extras 1

Extra buildsteps and stuff for buildbot

pull request commentgoogle/llvm-premerge-checks

Clang tidy non utf8

@googlebot I fixed it.

wanders

comment created time in 2 months

push eventwanders/llvm-premerge-checks

Anders Waldenborg

commit sha 6f8ab385264d6afc7833f8ef0dcc84d54e7d2423

fix "clang-format/tidy" mixup in doc comment [NFC]

view details

Anders Waldenborg

commit sha 27f4acc5d44c815c9b317620fad9bc20d6e1e692

make clang_tidy_report handle diffs text files with invalid utf-8 "git diff" handles text files encoded that is not valid UTF-8 (e.g using ISO-8859-1) as text files and produces a diff of those (rather saying "Binary files a/x and b/x differ"). This means that the diff output may contain such characters. Files that did would cause clang_tidy_report.py do hit an UnicodeDecodeError when reading the diff, including if it was on removed lines and regardless if it was in the ignore file. By specifying errors mode "replace" for decode() method the bytes that are not a valid utf-8 encoding are replaced with the unicode replacement question mark (U+FFFD). When parsing the diff clang-tidy-diff is only looking at filenames and line numbers of the diff, so this shouldn't be a problem if it doesn't get the exact same byte sequence inside the actual change.

view details

push time in 2 months

PR opened google/llvm-premerge-checks

Clang tidy non utf8

See commit messages for details.

+2 -2

0 comment

1 changed file

pr created time in 2 months

push eventwanders/llvm-premerge-checks

Mikhail Goncharov

commit sha 19e290d0cb85b8383f082ec1d8a19773912b7190

store builds in runnings state and check them later That removes a wrong assumption that everything interesting is located within first few pages. Should also reduce API load a bit (as we will not load additional 5+ pages just in case.

view details

Mikhail Goncharov

commit sha ff4e998ef49f3250163686318ad84dd6120f722b

update buildkite monitoring

view details

Mikhail Goncharov

commit sha 4ec41ed8a884b1dd0d13a9808bbf18c6fb788405

enable flang

view details

Thomas Lively

commit sha 75ca275b109e53cc268c8ada60970e780a320fcd

Ignore clang/lib/Headers/wasm_simd128.h See https://reviews.llvm.org/D106500 for an example of the spurious positives I would like to ignore.

view details

Mikhail Goncharov

commit sha 1b116862e60b6dd867b6601ff7556c6450eb4d8c

Fix modified projects resolution when there are unmapped changes for #325

view details

Mikhail Goncharov

commit sha c1b5c95071e161e74f348cdcf2a14a892802f3be

Ignore changes in 'utils' Blaze build check should be done via separate pipeline For #325

view details

Nikita Popov

commit sha 6d1a03c400e984151e6b3d71952fb61ba930d236

Disable openmp tests libarcher tests (part of openmp) have been broken for the past few weeks, and nobody seems to care. As such, disable the openmp project. I hope this is the right place to do so.

view details

Mikhail Goncharov

commit sha f7058aaa51c5472d9ecf292e0875e66c4c8b56e0

add post-checkout to run git prune fix #321

view details

Mikhail Goncharov

commit sha 6c2410440e62258fee6d59dd42a352a30c2083e3

Run bazel builds in premerge if user is a member of "bazel_build" https://reviews.llvm.org/project/view/107/ or modified /utils/bazel/* For #328

view details

Mikhail Goncharov

commit sha 0522d2b402733685a8187882104c064888d3dd2f

Revert "Disable openmp tests" This reverts commit 6d1a03c400e984151e6b3d71952fb61ba930d236. Offending https://reviews.llvm.org/D105719 was reverted upstream.

view details

Geoffrey Martin-Noble

commit sha c47e555d0f4982fc6fc976f1d5ea9879ce234fbd

Correctly skip project classification for utils/ `project` is a list here, not a string.

view details

Geoffrey Martin-Noble

commit sha 8bc6bb7d5d11ec6b46d24584a9cb418e3efd2e50

Switch Bazel premerge checks to use llvm-bazel-premerge queue I created a new queue for the pre-merge checks so that they won't compete for resources with the post-merge build already running. Obviously that creates some inefficiency, but is a simple way to make sure neither build gets starved (in particular, we know that the current setup of 4 agents running on a single 32-core VM is enough to handle the commit traffic on the main branch whereas pre-merge testing volume is likely to be more unpredictable.

view details

Mikhail Goncharov

commit sha 49be688a27c7eb867446a1ad12aa7b5cd1ac2122

script to sync fork llvm-premerge-tests/llvm-project - uniformly append env variables - resolve current HEAD and pass it as BUILDKITE_COMMIT to script generators. Add it as ph_commit_sha.

view details

Anders Waldenborg

commit sha 07bf31c16a85b85b2030e8546cafb816b38326ab

fix "clang-format/tidy" mixup in doc comment [NFC]

view details

Anders Waldenborg

commit sha 32e61d641ff80b2537ab2f9edb556544a2a2101b

make clang_tidy_report handle diffs text files with invalid utf-8 "git diff" handles text files encoded that is not valid UTF-8 (e.g using ISO-8859-1) as text files and produces a diff of those (rather saying "Binary files a/x and b/x differ"). This means that the diff output may contain such characters. Files that did would cause clang_tidy_report.py do hit an UnicodeDecodeError when reading the diff, including if it was on removed lines and regardless if it was in the ignore file. By specifying errors mode "replace" for decode() method the bytes that are not a valid utf-8 encoding are replaced with the unicode replacement question mark (U+FFFD). When parsing the diff clang-tidy-diff is only looking at filenames and line numbers of the diff, so this shouldn't be a problem if it doesn't get the exact same byte sequence inside the actual change.

view details

push time in 2 months