https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.45.2 2020-05-01T02:50:43+00:00 2020-05-01T02:50:43+00:00 mark markm@cs.wisc.edu 2020-05-01T02:50:43+00:00 urn:sha1:9e43b00d4fe2660573e40ec9125290b1d9974e44 2020-04-10T13:09:58+00:00 Guillaume Gomez guillaume1.gomez@gmail.com 2019-11-21T12:57:40+00:00 urn:sha1:38eb369fa4d06e55869a8fae62796a7b0085a5bd 2020-03-24T18:38:53+00:00 Santiago Pastorino spastorino@gmail.com 2020-03-10T20:22:25+00:00 urn:sha1:4387a8b96e4ae5b0c0450b284574d8307b4d5685 2019-12-10T14:30:09+00:00 Mark Rousskov mark.simulacrum@gmail.com 2019-11-23T23:08:49+00:00 urn:sha1:97d936423c914c4e3402bfecfd6943e1edf23815 2019-10-30T18:41:22+00:00 Pietro Albini pietro@pietroalbini.org 2019-10-30T18:41:22+00:00 urn:sha1:ca3468768d234af5de4fe7b578b701e3404a6dac Before this commit toolstates.json was stored in /tmp and it wasn't mounted outside the build container. That caused uploading the file in the upload-artifacts task to fail, as the file was missing on the host. Mounting /tmp/toolstates.json alone is not the best approach: if the file is missing when the container is started the Docker engine will create a *directory* named /tmp/toolstates.json. The Docker issue could be solved by pre-creating an empty file named /tmp/toolstates.json, but doing that could cause problems if bootstrap fails to generate the file and the toolstate scripts receive an empty JSON. The approach I took in this commit is to instead mount a /tmp/toolstate directory inside Docker, and create the toolstates.json file in it. That also required a small bootstrap change to ensure the directory is created if it's missing. 2019-07-28T09:11:06+00:00 Mazdak Farrokhzad twingoow@gmail.com 2019-07-28T09:11:06+00:00 urn:sha1:2826bdcfa6fecc656294534162fb5990d3d53cf5 Actually add rustc-guide to toolstate, don't fail builds for the guide cc @ehuss r? @kennytm 2019-07-25T09:51:08+00:00 Pietro Albini pietro@pietroalbini.org 2019-07-25T09:51:08+00:00 urn:sha1:b01b5b911f3bb209ee619055a154cd81ca0674be Unfortunately due to an Azure quirk the TOOLSTATE_REPO_ACCESS_TOKEN is not suitable to gate whether to push new commits to the repo, as if it's not defined on the Azure side it will actually be set to the literal `$(TOOLSTATE_REPO_ACCESS_TOKEN)`, which screws everything up. This instead adds another, non-secret environment variable to gate publishing: TOOLSTATE_PUBLISH. As non-secret environment variables behave correctly this fixes the issue. 2019-07-23T20:37:04+00:00 Mark Mansi markm@cs.wisc.edu 2019-07-23T20:33:41+00:00 urn:sha1:11a3b742d8dfae9c9d4858adc5417918e13d84a5 2019-07-23T20:36:51+00:00 Ralf Jung post@ralfj.de 2019-07-23T08:54:30+00:00 urn:sha1:82d18412d1478a5c2db8bf6ed6c32e4b1c668dfe 2019-07-23T20:36:51+00:00 Ralf Jung post@ralfj.de 2019-07-23T08:34:19+00:00 urn:sha1:9c48ed4eab3d2f6050803479f76db0aafecdd7c7