build_env fails when called after changing the current directory to another git repo #12321

jdm · 2016-07-07T15:45:10Z

Specifically, when upgrading wptrunner we change the current directory to tests/wpt/harness, which contains its own .git which confuses build_env.

highfive · 2016-07-07T15:45:12Z

cc @wafflespeanut


        Avoid servo#12321 by creating environment before switching directories.


        Avoid servo#12321 by creating environment before switching directories.


        Avoid servo#12321 by creating environment before switching directories.

nox · 2017-10-04T11:16:39Z

That was fixed, AFAICT.

jdm added the L-python label Jul 7, 2016

jdm added a commit to jdm/servo that referenced this issue Jul 7, 2016

Avoid servo#12321 by creating environment before switching directories.

f8e4311

jdm added a commit to jdm/servo that referenced this issue Sep 13, 2016

Avoid servo#12321 by creating environment before switching directories.

ee454f8

jdm added a commit to jdm/servo that referenced this issue Oct 6, 2016

Avoid servo#12321 by creating environment before switching directories.

a2bc9d7

nox closed this Oct 4, 2017

servo / servo

build_env fails when called after changing the current directory to another git repo #12321

build_env fails when called after changing the current directory to another git repo #12321

jdm commented Jul 7, 2016 •

edited by KiChjang

highfive commented Jul 7, 2016

nox commented Oct 4, 2017

servo / servo

Join GitHub today

build_env fails when called after changing the current directory to another git repo #12321

build_env fails when called after changing the current directory to another git repo #12321

Comments

jdm commented Jul 7, 2016 • edited by KiChjang

highfive commented Jul 7, 2016

nox commented Oct 4, 2017

jdm commented Jul 7, 2016 •

edited by KiChjang