Thread overview
[phobos] sigh
Jan 15, 2014
Brad Roberts
Jan 15, 2014
David Nadlinger
Jan 15, 2014
David Nadlinger
Jan 15, 2014
Brad Roberts
Jan 16, 2014
David Nadlinger
January 15, 2014
So, master is broken.  There's a reason we have pull requests and testing of them.

Sigh,
Brad
_______________________________________________
phobos mailing list
phobos@puremagic.com
http://lists.puremagic.com/mailman/listinfo/phobos


January 15, 2014
On Wed, Jan 15, 2014 at 9:35 PM, Brad Roberts <braddr@puremagic.com> wrote:
> So, master is broken.  There's a reason we have pull requests and testing of them.

I pushed a fix to master to hopefully unstick the CI system.

Everybody, if you *really* need to push directly to master, please not only thoroughly check your changes locally beforehand, but also watch the buildbots afterwards.

Thanks,
David
_______________________________________________
phobos mailing list
phobos@puremagic.com
http://lists.puremagic.com/mailman/listinfo/phobos


January 15, 2014
On Wed, Jan 15, 2014 at 9:35 PM, Brad Roberts <braddr@puremagic.com> wrote:
> So, master is broken.

On a related note: Brad, does the auto tester have any sort of API to get the latest all-green commit for a given platform?

I'm currently building another CI-style tool for core D development (stay tuned for the announcement), and something like this would be really helpful to avoid wasting cycles when master is broken.

It wouldn't have to be something elaborate, just a simple HTTP endpoint that returns a JSON (or even text) file with the latest Git hashes.

David
_______________________________________________
phobos mailing list
phobos@puremagic.com
http://lists.puremagic.com/mailman/listinfo/phobos


January 15, 2014
On 1/15/14 1:56 PM, David Nadlinger wrote:
> On Wed, Jan 15, 2014 at 9:35 PM, Brad Roberts <braddr@puremagic.com> wrote:
>> So, master is broken.
>
> On a related note: Brad, does the auto tester have any sort of API to
> get the latest all-green commit for a given platform?
>
> I'm currently building another CI-style tool for core D development
> (stay tuned for the announcement), and something like this would be
> really helpful to avoid wasting cycles when master is broken.
>
> It wouldn't have to be something elaborate, just a simple HTTP
> endpoint that returns a JSON (or even text) file with the latest Git
> hashes.
>
> David

The tester doesn't currently track sha's of the master builds, so no.  It also makes no attempt to make sure that the runs on each platform are the same sha's.. it just tests whatever is tip at the time of the start of the run.  Eventually, when builds quiesce the tip sha will be the same across the platforms.  But for such an api, it'd need to have some concept of order of sha's, which isn't particularly easy.  Add in the multiple repos, and the story gets a little muddier.

Not that it can't be done, but I'm really not sure the gain is worth the effort.  It would be a lot easier to have an api (which already exists) that returns the state of the current build.  From there you could decide whether whatever operation you want to do is ok or should wait.

    http://d.puremagic.com/test-results/summary.json.ghtml

Currently, that api only works for projectid 1, which is "DMD master".  It's in my bug backlog to make it accept the projectid as a parameter (and later make it required rather than default to 1). It's currently used by one of the two greasemonkey github integration scripts.  It probably also ought to include another field per object to indicate that the build result has been marked deprecated, meaning that another newer build will start soon.

Later,
Brad

_______________________________________________
phobos mailing list
phobos@puremagic.com
http://lists.puremagic.com/mailman/listinfo/phobos


January 16, 2014
On Wed, Jan 15, 2014 at 11:32 PM, Brad Roberts <braddr@puremagic.com> wrote:
> Not that it can't be done, but I'm really not sure the gain is worth the effort.

Thanks a lot for the quick answer.

I see, it's probably not worth the effort then. I figured the system might already track SHA-1 hashes, as it also receives the client log.

Let's see if the issue becomes a problem. If so, I suppose I can still resort to scraping the build log pages every 15 minutes or so. ;)

Best,
David
_______________________________________________
phobos mailing list
phobos@puremagic.com
http://lists.puremagic.com/mailman/listinfo/phobos