Define ExecuteBash in the Appveyor error block

When Appveyor fails before ExecuteBash is defined, it skips straight to the error block. But the error block wants ExecuteBash. So we should define it twice.

Example: https://ci.appveyor.com/project/nmathewson/tor/build/1.0.850/job/v5mws73je9sihmfn

changed milestone to %Tor: 0.3.5.x-final

added 035-backport 040-backport 041-backport 042-backport 042-can BugSmashFund actualpoints::0.1 component::core tor/tor consider-backport-after-ci-passes milestone::Tor: 0.3.5.x-final owner::teor points::0.1 priority::medium resolution::fixed reviewer::asn severity::normal status::closed tor-ci-fail-rarely type::defect version::tor 0.3.4.2-alpha labels

Anyone can fix this bug, but I'll try to to it on Monday.

See my PR:

• 0.3.5: https://github.com/torproject/tor/pull/1376

The test merges are all clean, the branches are here:

• https://github.com/teor2345/tor/branches/all?query=31884

Trac:
Status: assigned to needs_review
Keywords: N/A deleted, consider-backport-after-0423, BugSmashFund added
Version: Tor: unspecified to Tor: 0.3.4.2-alpha
Actualpoints: N/A to 0.1

Trac:
Reviewer: N/A to asn

LGTM!

Trac:
Status: needs_review to merge_ready

Merged to master, marking for backport.

Trac:
Milestone: Tor: 0.4.2.x-final to Tor: 0.4.1.x-final

This is a CI issue, so we can backport it as soon as CI passes,

Trac:
Keywords: consider-backport-after-0423 deleted, consider-backport-after-ci-passes added

Merged to 0.3.5 and forward.

Trac:
Milestone: Tor: 0.4.1.x-final to Tor: 0.3.5.x-final

Trac:
Resolution: N/A to fixed
Status: merge_ready to closed

closed

changed time estimate to 48m

added 48m of time spent

moved to tpo/core/tor#31884 (closed)