Page MenuHomePhabricator

Correctly detect new version of xhpast build
ClosedPublic

Authored by richardvanvelzen on May 19 2016, 10:52 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Apr 24, 3:43 AM
Unknown Object (File)
Wed, Apr 24, 3:43 AM
Unknown Object (File)
Wed, Apr 24, 3:43 AM
Unknown Object (File)
Wed, Apr 24, 3:43 AM
Unknown Object (File)
Fri, Apr 19, 2:28 AM
Unknown Object (File)
Fri, Apr 19, 2:28 AM
Unknown Object (File)
Fri, Apr 19, 2:28 AM
Unknown Object (File)
Fri, Apr 12, 9:14 AM
Subscribers

Details

Summary

When running lint after xhpast is updated, it tests whether the version is up-to-date. Because the version isn't reset before the test, it would think that the build failed, requiring a second run of lint

Test Plan

Downgraded xhpast, ran lint. Saw broken xhpast, but correct xhpast on second run. Applied patch, and got correct lint results regardless of version.

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

richardvanvelzen retitled this revision from to Correctly detect new version of xhpast build.
richardvanvelzen updated this object.
richardvanvelzen edited the test plan for this revision. (Show Details)
richardvanvelzen added a reviewer: epriestley.

Not really high-prio, but a minor annoyance after getting a fresh xhpast version.

epriestley edited edge metadata.
This revision is now accepted and ready to land.May 19 2016, 1:53 PM
chad added a reviewer: chad.
This revision was automatically updated to reflect the committed changes.