{"action":"created","issue":{"url":"https://api.github.com/repos/mirage/mirage-www/issues/422","labels_url":"https://api.github.com/repos/mirage/mirage-www/issues/422/labels{/name}","comments_url":"https://api.github.com/repos/mirage/mirage-www/issues/422/comments","events_url":"https://api.github.com/repos/mirage/mirage-www/issues/422/events","html_url":"https://github.com/mirage/mirage-www/issues/422","id":124230540,"number":422,"title":"Race condition in Travis deploy scripts?","user":{"login":"amirmc","id":121855,"avatar_url":"https://avatars.githubusercontent.com/u/121855?v=3","gravatar_id":"","url":"https://api.github.com/users/amirmc","html_url":"https://github.com/amirmc","followers_url":"https://api.github.com/users/amirmc/followers","following_url":"https://api.github.com/users/amirmc/following{/other_user}","gists_url":"https://api.github.com/users/amirmc/gists{/gist_id}","starred_url":"https://api.github.com/users/amirmc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/amirmc/subscriptions","organizations_url":"https://api.github.com/users/amirmc/orgs","repos_url":"https://api.github.com/users/amirmc/repos","events_url":"https://api.github.com/users/amirmc/events{/privacy}","received_events_url":"https://api.github.com/users/amirmc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-12-29T16:00:06Z","updated_at":"2015-12-29T16:37:41Z","closed_at":null,"body":"I *think* there's a race condition in the deploy scripts that push to `mirage-www-deployment`.  We currently build and deploy two unikernels and Travis does these in parallel. I just saw the following build failure for the `mirage.io` Xen build (in build number `#1001` — I restarted it so the full log might be lost now).  I did notice that the deployment repo had a new successful push for one of the unikernels.\r\n\r\n@mor1 @samoht Am I right about the above? Apart from restarting the failed build, is there anything else we could do?  I'm wondering about future scenarios where we might want to build/deploy for multiple backends but still push each one into the same repo.\r\n\r\n```\r\nWarning: Permanently added 'github.com' (RSA) to the list of known hosts.\r\nTo git@mir-deploy:mirage/mirage-www-deployment\r\n ! [rejected]        master -> master (fetch first)\r\nerror: failed to push some refs to 'git@mir-deploy:mirage/mirage-www-deployment'\r\nhint: Updates were rejected because the remote contains work that you do\r\nhint: not have locally. This is usually caused by another repository pushing\r\nhint: to the same ref. You may want to first integrate the remote changes\r\nhint: (e.g., 'git pull ...') before pushing again.\r\nhint: See the 'Note about fast-forwards' in 'git push --help' for details.\r\n```"},"comment":{"url":"https://api.github.com/repos/mirage/mirage-www/issues/comments/167826953","html_url":"https://github.com/mirage/mirage-www/issues/422#issuecomment-167826953","issue_url":"https://api.github.com/repos/mirage/mirage-www/issues/422","id":167826953,"user":{"login":"samoht","id":103693,"avatar_url":"https://avatars.githubusercontent.com/u/103693?v=3","gravatar_id":"","url":"https://api.github.com/users/samoht","html_url":"https://github.com/samoht","followers_url":"https://api.github.com/users/samoht/followers","following_url":"https://api.github.com/users/samoht/following{/other_user}","gists_url":"https://api.github.com/users/samoht/gists{/gist_id}","starred_url":"https://api.github.com/users/samoht/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/samoht/subscriptions","organizations_url":"https://api.github.com/users/samoht/orgs","repos_url":"https://api.github.com/users/samoht/repos","events_url":"https://api.github.com/users/samoht/events{/privacy}","received_events_url":"https://api.github.com/users/samoht/received_events","type":"User","site_admin":false},"created_at":"2015-12-29T16:37:41Z","updated_at":"2015-12-29T16:37:41Z","body":"Indeed, see #408"}}