#1393: Tag source tree with successful bootstraps
-------------------------+--------------------------------------------------
Reporter: guest | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Compiler | Version: 6.7
Severity: minor | Resolution:
Keywords: | Difficulty: Unknown
Os: Unknown | Testcase:
Architecture: Unknown |
-------------------------+--------------------------------------------------
Comment (by claus):
i've been bitten by that, too. but given the time needed for build tests,
the buildbots would have to tag the repos before starting their build, and
given the variation over platforms, each buildbot would need to do so..
overall, it might be easier for each buildbot to record what versions of
the repos it is using, and the commands needed to recreate its build
environment, precisely.
a step in the right direction would be to augment the 'Daily report for
HEAD' emails. they already summarise how each buildbot fares, by phase.
they should also list, for each buildbot, the date/# of the last
successfull build (perhaps even with a direct link to the last successful
buildbot report, as those are meant to include information on how to
reproduce the build environment)
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1393>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
