{"push_id":1148561092,"size":7,"distinct_size":6,"ref":"refs/heads/musl","head":"4b88d8f7fff386ef57c0981de0b0697240794d75","before":"c66e8102104578ea71bbc2abf3c439b1b7586c9a","commits":[{"sha":"247629d1d4d73c6fc85c390b0feb0cf2bd4530cf","author":{"name":"Kareem Khazem","email":"cc9495de901e52b2bd5873814db8d39eb2b12531@karkhaz.com"},"message":"Allow user to specify toolchain to post-process\n\nThe user can now optionally specify a list of toolchains to\npost-process, instead of post-processing the results of all toolchains\n(which remains the default). This is because post-processing it taking a\nlarge amount of main memory, and running the post-processing one\ntoolchain at a time can help the machine to not thrash.","distinct":false,"url":"https://api.github.com/repos/karkhaz/tuscan/commits/247629d1d4d73c6fc85c390b0feb0cf2bd4530cf"},{"sha":"0674cda324025841253aeabb08a8cb4ab1d9eba3","author":{"name":"Kareem Khazem","email":"cc9495de901e52b2bd5873814db8d39eb2b12531@karkhaz.com"},"message":"Adding Bear\n\nThe Bear tool for tracing subprocess executions has been added to\ntuscan. This addition is based on the unchanged Bear upstream; tuscan\ndoes not use bear as-is, but will use it when we incorporate some\nadditional features into bear.","distinct":true,"url":"https://api.github.com/repos/karkhaz/tuscan/commits/0674cda324025841253aeabb08a8cb4ab1d9eba3"},{"sha":"78d0e236c44e26a5d2c7df98f5ff2ab84e2b6c1d","author":{"name":"Kareem Khazem","email":"cc9495de901e52b2bd5873814db8d39eb2b12531@karkhaz.com"},"message":"Removing compiler-classification code from bear\n\nThe bear tool has been stripped of code that classifies executions as\nbeing compiler calls. We wish to be informed about every subprocess that\nis executed, and will do our own analysis at a later stage.\n\nBear now produces a flat list of exec-ed subprocesses as output.","distinct":true,"url":"https://api.github.com/repos/karkhaz/tuscan/commits/78d0e236c44e26a5d2c7df98f5ff2ab84e2b6c1d"},{"sha":"f91f52fdfab114c0707d30e81c82655aa560acc1","author":{"name":"Kareem Khazem","email":"cc9495de901e52b2bd5873814db8d39eb2b12531@karkhaz.com"},"message":"Bear now logs return codes of execed processes\n\nThere are now two kinds of record generated from the bear tool: those\nemitted when a process is execed, and those emitted when a process\nexits.\n\nThe records are discriminated by the new \"kind\" field, which shall be\nset to either \"EXEC\" or \"EXIT\". \"EXIT\" records contain the return code,\nPID, and parent PID of the exiting process.","distinct":true,"url":"https://api.github.com/repos/karkhaz/tuscan/commits/f91f52fdfab114c0707d30e81c82655aa560acc1"},{"sha":"afb8b1f5b5ab2ab6dcb81cd578de9fdecd5f5d78","author":{"name":"Kareem Khazem","email":"cc9495de901e52b2bd5873814db8d39eb2b12531@karkhaz.com"},"message":"Bear now logs timestamps for execed processes\n\nThis is so that we can order processes in the order they were executed.\nTimestamps are generated at the exec site, rather than at the log site,\nsince the log function is protected by a mutex.","distinct":true,"url":"https://api.github.com/repos/karkhaz/tuscan/commits/afb8b1f5b5ab2ab6dcb81cd578de9fdecd5f5d78"},{"sha":"ffc620d6823e652395995c0ec8727aef0b446a43","author":{"name":"Kareem Khazem","email":"cc9495de901e52b2bd5873814db8d39eb2b12531@karkhaz.com"},"message":"Bear is called on each build\n\nThe bear tool is now used to wrap each invocation of makepkg when\nattempting to build packages. The output is stored as part of the\nJSON result structure.","distinct":true,"url":"https://api.github.com/repos/karkhaz/tuscan/commits/ffc620d6823e652395995c0ec8727aef0b446a43"},{"sha":"4b88d8f7fff386ef57c0981de0b0697240794d75","author":{"name":"Kareem Khazem","email":"cc9495de901e52b2bd5873814db8d39eb2b12531@karkhaz.com"},"message":"Addition of musl toolchain\n\nA clang+llvm+libcxx+musl toolchain is now supported, in addition to the\nupstream and android toolchains.\n\nThe following changes have been made to the build infrastructure in\norder to support this change:\n\n- Toolchain-specific files for the install_bootstrap stage and\n  make_package stage are now located in the directory\n  $TOOLCHAIN/{install_bootstrap,make_package}, rather than being located\n  directly under $TOOLCHAIN. This is because musl requires a slightly\n  different Dockerfile for its install_bootstrap stage than the other\n  toolchains, so each toolchain can now specify its own Dockerfile for\n  the install_bootstrap stage.\n\n- The `copy_files` field in deps.yaml files now supports globbing, in\n  order to copy all files in a directory without knowing what they are\n  called. This is because some of the toolchains have a Python setup\n  script, while the musl toolchain uses a shell script.","distinct":true,"url":"https://api.github.com/repos/karkhaz/tuscan/commits/4b88d8f7fff386ef57c0981de0b0697240794d75"}]}
{"actor":{"display_login":"karkhaz"}}