[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Eli Bendersky added the comment: I think this issue can be closed, since Martin's touch step runs on the bots successfully, and the ASDL dependencies in .hgtouch were fixed. -- resolution: -> fixed stage: -> committed/rejected status: open -> closed __

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Antoine Pitrou added the comment: > I still see the current situation better than the previous one, where > this > was scattered around PEPs, Wikis and just random web pages. Having it > all > in the same repository is not ideal from a taxonomical point of view, > perhaps, but as a single collect

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Nick Coghlan added the comment: Where to document the infrastructure setup (including the buildbots) is up to Noah/infrastructure-sig, as the devguide just covers CPython development, while the PSF infrastructure team covers a lot more than that. A pointer from the devguide docs to the appropr

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Martin v. Löwis added the comment: Documenting the pydotorg setup is a field of ongoing discussions. If you ask three people involved, you get three answers where this should be documented, with no chance for consensus. >From an infrastructure point of view, it is up to the infrastructure head

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Eli Bendersky added the comment: +nick,guido,benjamin: in case you're interested in the discussion that takes place in the most recent messages of this issue -- nosy: +benjamin.peterson, gvanrossum, ncoghlan ___ Python tracker

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Eli Bendersky added the comment: On Tue, Oct 1, 2013 at 7:00 AM, Antoine Pitrou wrote: > > Antoine Pitrou added the comment: > > > I'm not sure a separate document is right here because that's one > > more repository to have. The devguide already contains sections for > > somewhat more esoteric

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Antoine Pitrou added the comment: > I'm not sure a separate document is right here because that's one > more repository to have. The devguide already contains sections for > somewhat more esoteric things like compiler internals guide, > coverity scans. Besides, section 18 already has some materia

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Eli Bendersky added the comment: I'm not sure a separate document is right here because that's one more repository to have. The devguide already contains sections for somewhat more esoteric things like compiler internals guide, coverity scans. Besides, section 18 already has some material abou

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Antoine Pitrou added the comment: > I was talking to Antoine about this the other day, and maybe there's > sense to create an "infrastructure" section in the devguide that > will explain how to log into the buildbot server and look at the > configuration. IMHO it would make more sense to create

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Eli Bendersky added the comment: I've updated the devguide about `make touch`. As for the buildbot configuration, I agree we shouldn't document a static snapshot and also there's the passwords problem. I was talking to Antoine about this the other day, and maybe there's sense to create an "in

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Roundup Robot added the comment: New changeset 56ed149e597a by Eli Bendersky in branch 'default': Mention 'make touch' in the devguide. http://hg.python.org/devguide/rev/56ed149e597a -- ___ Python tracker _

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Martin v. Löwis added the comment: "make touch" (or "hg touch") certainly should be mentioned. Details of the buildbot configuration need not. Publishing the buildbot configuration file might be useful, except that it also contains all the builder passwords, which should not be published. If t

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Eli Bendersky added the comment: With your fix, `make touch` now behaves as expected. Also, I can see the step added to the bots (e.g. http://buildbot.python.org/all/builders/AMD64%20Ubuntu%20LTS%203.x/builds/2597/steps/shell/logs/stdio) Thanks, I think the issue is resolved then. We should no

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Martin v. Löwis added the comment: I have now updated the master.cfg to make buildbottouch a separate build step. -- ___ Python tracker ___ __

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Roundup Robot added the comment: New changeset 86eff5c4e698 by Martin v. Löwis in branch '3.3': Issue #19106: Add buildbottouch target. http://hg.python.org/cpython/rev/86eff5c4e698 -- ___ Python tracker __

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Roundup Robot added the comment: New changeset 477246839224 by Martin v. Löwis in branch '3.3': Issue #19106: Touch generated files to be 1s newer than their youngest source. http://hg.python.org/cpython/rev/477246839224 -- nosy: +python-dev ___ Pytho

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Eli Bendersky added the comment: LGTM -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.or

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Martin v. Löwis added the comment: Here is a patch that backdates outputs 1s after their youngest input (and sleeps if necessary to avoid producing files in the future). With that, I get lap-le:3k loewis$ touch Parser/asdl_c.py ;date;make touch;date Mo 30 Sep 2013 15:29:21 CEST hg --config ext

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Martin v. Löwis added the comment: I see two solutions, both involving to track the newest timestamp that needs to pass. a) touch the file to have a time stamp in the future. make might complain, though. b) sleep until a second has passed, then touch (actually, sleep of 100ms multiple times un

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Eli Bendersky added the comment: The problem in this case is different, actually. It's the comparison: if o_time <= i_time: # generated file is older, touch need_touch = True In check_rule. The script is pretty quick so when it touches both Python-ast.h and .c t

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Eli Bendersky added the comment: Ooh, I think that's because the "# try processing all rules in topological order" in do_touch doesn't actually topo-sort. -- ___ Python tracker

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

Eli Bendersky added the comment: .hgtouch fixed in ac19ff225280 (I specified the issue number incorrectly so this one wasn't notified). Curiously, `make touch` seems to think there's still things to do even after the first round of "touching": $ touch Parser/asdl_c.py $ make touch hg --confi

[issue19106] Prepare .hgtouch and Tools/hg/hgtouch.py to run on the bots

New submission from Eli Bendersky: Background: we'd like to enable running 'make touch' on the bots before 'make -jN', to avoid problems with scripts that auto-generate code for the Python build (bootstrapping). pydev thread: https://mail.python.org/pipermail/python-dev/2013-September/128992.h