afaik there is no way to just let it "build again". Only some commit would trigger it. Well, I may just change the changelog for upcoming release with the info on amber-cli...
[hidden email] wrote:
>
>
>
> On Tue, Apr 15, 2014 at 9:34 AM, Herby Vojčík <
[hidden email]
> <mailto:
[hidden email]>> wrote:
>
> It was on the branch cli-extract, where all unnecessary was
> deleted, so tests failed.
> On the main branch, all should work as usual.
>
>
>
> It is because that's the status shown on the amber github page icon.
> Which isn't good looking.
>
> Phil
>
>
>
[hidden email] <mailto:
[hidden email]> wrote:
>
>
> sh: 1: ./bin/amber: not found
>
> npmERR!Test failed. See above for more details.
>
>
>
> npmERR!not okcode 0
>
>
>
> Phil
>
> --
> You received this message because you are subscribed to the
> Google Groups "amber-lang" group.
> To unsubscribe from this group and stop rece
iving emails from
om it, send
> an email to
[hidden email]
> <mailto:
[hidden email]>.
> For more options, visit
https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[hidden email].
For more options, visit
https://groups.google.com/d/optout.
Locked
