{"push_id":3035873337,"size":9,"distinct_size":1,"ref":"refs/heads/memModul","head":"f1e665742185d25ac595429ce1141c9f60d51960","before":"e29a1a6bfaf66c137213f34a09c5b9633f93bb5a","commits":[{"sha":"04529b35c37aa36f5be78618378be8286c0ffdef","author":{"name":"Martin Pitt","email":"54669547a225ff20cba8b75a4adca540eef25858@piware.de"},"message":"bots: Install libvirt-dbus on ubuntu-stable\n\nUbuntu 18.10 has libvirt-dbus now [1], so install and test it.\n\nAs libvirt-dbus is the main mode of operation now, invert the install\nlogic to default to installing it, and blacklisting it on releases that\ndon't have it yet. This will avoid forgetting to install it on newer\nreleases.\n\nThis exposes wrong socket permissions of libvirt-dbus in Ubuntu 18.10,\nreported as https://launchpad.net/bugs/1802005. Work around that by\nexplicitly chowning the socket in the tests, so that we cover the\nfunctionality and avoid further regressions.\n\n[1] https://packages.ubuntu.com/cosmic/libvirt-dbus","distinct":false,"url":"https://api.github.com/repos/skobyda/cockpit/commits/04529b35c37aa36f5be78618378be8286c0ffdef"},{"sha":"e1598b501e2575c53d230bd2e57226adf5eb1625","author":{"name":"Martin Pitt","email":"54669547a225ff20cba8b75a4adca540eef25858@piware.de"},"message":"bots: Install firewalld on Debian/Ubuntu images\n\nEnable the corresponding tests.\n\nThis exposes a bug with the Debian 8 docker.io backport when running on\nDebian 9: Port forwarding in a container fails with\n\n    iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 3380 ! -i docker0 -j DNAT --to-destination 172.17.0.8:3380:\n    iptables: No chain/target/match by that name.\n\nAs this is a totally unsupported package and thus nowhere to report a\nbug to, just add a hack to disable firewalld for this case.\n\nAlso disable firewalld for the libvirt tests, as we don't configure any\nrules to allow traffic on the virbr0 bridge. This causes DHCP\nrequests/responses to get blocked, and thus images take very long to\nboot waiting for network configuration.\n\nThis exposes that known issue #9722 also affects debian-testing, so copy\nthe naughty override.\n\nCloses #10512","distinct":false,"url":"https://api.github.com/repos/skobyda/cockpit/commits/e1598b501e2575c53d230bd2e57226adf5eb1625"},{"sha":"72193a364244a68533b52a960006b9e98840f9cd","author":{"name":"Cockpituous","email":"6cf1b27d05f26c1b90d056413683f40d3d33baae@cockpit-project.org"},"message":"images: Update debian-stable image","distinct":false,"url":"https://api.github.com/repos/skobyda/cockpit/commits/72193a364244a68533b52a960006b9e98840f9cd"},{"sha":"b55c31f1aa454e1a699158b110f1cff2621fbfd9","author":{"name":"Cockpituous","email":"6cf1b27d05f26c1b90d056413683f40d3d33baae@cockpit-project.org"},"message":"images: Update debian-testing image","distinct":false,"url":"https://api.github.com/repos/skobyda/cockpit/commits/b55c31f1aa454e1a699158b110f1cff2621fbfd9"},{"sha":"b47b1845f2953e040dec559ce41c86f04cb0f8c8","author":{"name":"Cockpituous","email":"6cf1b27d05f26c1b90d056413683f40d3d33baae@cockpit-project.org"},"message":"images: Update ubuntu-1804 image","distinct":false,"url":"https://api.github.com/repos/skobyda/cockpit/commits/b47b1845f2953e040dec559ce41c86f04cb0f8c8"},{"sha":"4fa2652aba9b0c1dbbbafb65233aebd179fb8ee2","author":{"name":"Cockpituous","email":"6cf1b27d05f26c1b90d056413683f40d3d33baae@cockpit-project.org"},"message":"images: Update ubuntu-stable image","distinct":false,"url":"https://api.github.com/repos/skobyda/cockpit/commits/4fa2652aba9b0c1dbbbafb65233aebd179fb8ee2"},{"sha":"d72741fd06dcb66e2be44a72666aefcf633dadfb","author":{"name":"Martin Pitt","email":"54669547a225ff20cba8b75a4adca540eef25858@piware.de"},"message":"bots: Move fedora-i386 image to Fedora 29\n\nABRT still does not work on i386, but this isn't due to a too old\nversion any more -- it's just generally broken:\n\n    abrt-dump-journal-core[428]: Failed to obtain all required information from journald\n\nSo adjust the skip message.\n\nCloses #10536","distinct":false,"url":"https://api.github.com/repos/skobyda/cockpit/commits/d72741fd06dcb66e2be44a72666aefcf633dadfb"},{"sha":"fc9ff32aff3c6245796ccc176e2ff100efe7584c","author":{"name":"Cockpituous","email":"6cf1b27d05f26c1b90d056413683f40d3d33baae@cockpit-project.org"},"message":"images: Update fedora-i386 image","distinct":false,"url":"https://api.github.com/repos/skobyda/cockpit/commits/fc9ff32aff3c6245796ccc176e2ff100efe7584c"},{"sha":"f1e665742185d25ac595429ce1141c9f60d51960","author":{"name":"Simon Kobyda","email":"4431e4d5c11679b57d448bfd18482866452e91b3@redhat.com"},"message":"machines: Memory: Add option to change memory and maximum memory\n\nWhile 'Memory' can be changed during runtime, 'Max Memory' can be\nonly updated when machine is not running. However value of 'Memory'\ncannot be bigger than 'Max Memory' and value of 'Max Memory' cannot be\nsmaller than 'Memory'. So my solution is to have 'Max Memory' greyed out\nwhen machine is not running.\n\nSo when user wants to increase 'Memory' of over the limit of 'Max Memory'\nof the running machine, he must shut down the machine to be able to also\nincrease 'Max Memory'.\n\nThis however brings futher question, how to design components composing\nof options of both categories: those which can be changed during runtime,\nand those which can be changed only when machine is offline, while options\nare mutually restrictive towards each other.\n\nSigned-off-by: Simon Kobyda <skobyda@redhat.com>","distinct":true,"url":"https://api.github.com/repos/skobyda/cockpit/commits/f1e665742185d25ac595429ce1141c9f60d51960"}]}
{"actor":{"display_login":"skobyda"}}