From dev-return-2323-archive-asf-public=cust-asf.ponee.io@singa.incubator.apache.org Sun Oct 28 04:34:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 4D427180649 for ; Sun, 28 Oct 2018 04:34:05 +0100 (CET) Received: (qmail 93759 invoked by uid 500); 28 Oct 2018 03:34:04 -0000 Mailing-List: contact dev-help@singa.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@singa.incubator.apache.org Delivered-To: mailing list dev@singa.incubator.apache.org Received: (qmail 93748 invoked by uid 99); 28 Oct 2018 03:34:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Oct 2018 03:34:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id C9D8818CE98 for ; Sun, 28 Oct 2018 03:34:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id nSdKqPJyErFy for ; Sun, 28 Oct 2018 03:34:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id B69785F494 for ; Sun, 28 Oct 2018 03:34:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id ABA8EE1013 for ; Sun, 28 Oct 2018 03:34:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 23A8027764 for ; Sun, 28 Oct 2018 03:34:00 +0000 (UTC) Date: Sun, 28 Oct 2018 03:34:00 +0000 (UTC) From: "Ngin Yun Chuan (JIRA)" To: dev@singa.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SINGA-399) Rafiki cannot test rebuilt image MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SINGA-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16666273#comment-16666273 ] Ngin Yun Chuan commented on SINGA-399: -------------------------------------- Hi Zhu Lei, Regarding your email with the following issue: ``` I want to add a new function in the predictor.py code. However, after I modify the code and rebuild the Rafiki_predictor image from the predictor.Dockerfile and run the client_usage.py code, I find Rafiki does not run my new code instead it seems that Rafiki is still running the original predictor.py. ``` It's an issue we have encountered numerous times. Since Docker Hub also contains `rafikiai/predictor:0.0.4` (https://hub.docker.com/u/rafikiai/), when we run `scripts/start.sh` with a locally built `rafikiai/predictor:0.0.4`, it seems to use Docker Hub's version. Currently I have been resolving it by incrementing the version in `.env.sh` to the next version i.e. 0.0.5 in your working directory, as long as e.g. `rafikiai/predictor:0.0.5` has not been pushed to Docker Hub. In the future, we should update the scripts to allow use of locally-built images even with such a version conflict. > Rafiki cannot test rebuilt image > -------------------------------- > > Key: SINGA-399 > URL: https://issues.apache.org/jira/browse/SINGA-399 > Project: Singa > Issue Type: Bug > Reporter: Zhu Lei > Priority: Major > Attachments: rafiki-1.PNG, rafiki-2.PNG, rafiki-3.PNG, rafiki-4.PNG > > > After downloading the newest rafiki code, at commit 7b3b04e15c62233e515c4d82051cd5dfb799215f, with comments "Add more error handling to notify user of invalid train job; compact exceptions", I ran "bash ./scripts/build_images.sh" to build the new admin, advisor, predictor and worker images. I got the images shown in attached image 'rafiki-1.PNG'. Then I run "bash ./script/start.sh" to build the containers as shown in the attached image 'rafiki-2.PNG'. Finally when I ran the client-usage.py example. I got the error in attached image 'rafiki-3.PNG'. > And I find very surprising that the images of admin, advisor, predictor and worker I built just now, become some images built weeks ago, shown in attached image 'rafiki-4.PNG'. Could you kindly provide me some explanations on why this happens? I really do not understand why this happened. > And finally, when I run "bash ./script/stop.sh" and leave the swarm and repeat my previous procedure again, now there is no errors. The only thing difference between the two runs I think is only the images are different. So the current code of rafiki does not support newly build images, that is my speculation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)