![\"\"](\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F694899%2F0e2abb51b17934ed0b3fb3d6d203e4e1%2Ferror.png?generation=1564824250717847&alt=media\")
I submitted the results from two kernels with an archive of generated images but got the error, see the screenshot below.
\n\n
The images are in JPEG format and submitted as a ZIP archive. The previous submissions were done without any issues, and I use the same snippet to generate the submission. However, this time I am getting the error, and it doesn't elaborate any details.
\n\nAlso, see an example of the generated image from the archive. It is 64x64, 3 channels, i.e., meeting the requirements.
\n\n![\"\"](\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F694899%2F296ea12687ee8d28bb22cba31d3a47b1%2F9426.png?generation=1564824514049241&alt=media\")
Did anybody have a similar issue before?
", "messages": [ { "id": "591185", "postDate": "08/03/2019 09:30:35", "content": "I submitted the results from two kernels with an archive of generated images but got the error, see the screenshot below.
\n\n
The images are in JPEG format and submitted as a ZIP archive. The previous submissions were done without any issues, and I use the same snippet to generate the submission. However, this time I am getting the error, and it doesn't elaborate any details.
\n\nAlso, see an example of the generated image from the archive. It is 64x64, 3 channels, i.e., meeting the requirements.
\n\n
Did anybody have a similar issue before?
", "rawMarkdown": "I submitted the results from two kernels with an archive of generated images but got the error, see the screenshot below.\n\n\n\nThe images are in JPEG format and submitted as a ZIP archive. The previous submissions were done without any issues, and I use the same snippet to generate the submission. However, this time I am getting the error, and it doesn't elaborate any details.\n\nAlso, see an example of the generated image from the archive. It is 64x64, 3 channels, i.e., meeting the requirements.\n\n\n\nDid anybody have a similar issue before?", "votes": null }, { "id": "591236", "postDate": "08/03/2019 11:21:18", "content": "Yep, today may 3 submissions all failed.
", "rawMarkdown": "Yep, today may 3 submissions all failed.", "votes": null }, { "id": "591315", "postDate": "08/03/2019 13:38:58", "content": "It's been for a couple of days for me, some working.
", "rawMarkdown": "It's been for a couple of days for me, some working.", "votes": null }, { "id": "591340", "postDate": "08/03/2019 14:21:05", "content": "Would be great if the lost submissions could be compensated :)
", "rawMarkdown": "Would be great if the lost submissions could be compensated :)", "votes": null }, { "id": "591538", "postDate": "08/03/2019 21:55:01", "content": "That's happening also in other kernels competitions. Kaggle has probably some issues with GPUs.\nHope they'll manage to find a solution 😅
", "rawMarkdown": "That's happening also in other kernels competitions. Kaggle has probably some issues with GPUs.\nHope they'll manage to find a solution 😅", "votes": null }, { "id": "591588", "postDate": "08/04/2019 01:06:45", "content": "Same problem. But I download the output of the failed kernel and test the FID score in my local pc, I got the right score ( 54.0 ). Hence it must be the Kaggle kernel ' bug.
", "rawMarkdown": "Same problem. But I download the output of the failed kernel and test the FID score in my local pc, I got the right score ( 54.0 ). Hence it must be the Kaggle kernel ' bug.", "votes": null }, { "id": "591607", "postDate": "08/04/2019 02:20:41", "content": "Still can't submit my output files
", "rawMarkdown": "Still can't submit my output files", "votes": null }, { "id": "591634", "postDate": "08/04/2019 03:56:11", "content": "Yes, I have same problem...and there seems to be something wrong with Kaggle Kernel(because I can't now submit my old kernel that I could submit before)
", "rawMarkdown": "Yes, I have same problem...and there seems to be something wrong with Kaggle Kernel(because I can't now submit my old kernel that I could submit before)", "votes": null }, { "id": "591724", "postDate": "08/04/2019 06:45:28", "content": "Yeah, I've submitted 3 times without any luck, from the different kernels.
", "rawMarkdown": "Yeah, I've submitted 3 times without any luck, from the different kernels.", "votes": null }, { "id": "591725", "postDate": "08/04/2019 06:47:42", "content": "I believe that now most of the participants train on the GPU, even tree-based methods, as soon as many libraries support it :)
", "rawMarkdown": "I believe that now most of the participants train on the GPU, even tree-based methods, as soon as many libraries support it :)", "votes": null }, { "id": "591726", "postDate": "08/04/2019 06:48:45", "content": "So then we can only wait :|
", "rawMarkdown": "So then we can only wait :|", "votes": null }, { "id": "593066", "postDate": "08/06/2019 06:49:27", "content": "Try to reduce the size of logs. My kernel failed every run without any output errors when I printed training score on every 50th iteration. It became OK when I started to print score on every epoch.
", "rawMarkdown": "Try to reduce the size of logs. My kernel failed every run without any output errors when I printed training score on every 50th iteration. It became OK when I started to print score on every epoch.", "votes": null } ], "comments": [ { "id": 591236, "author_name": "adnil8130", "author_url": "", "post_date": "08/03/2019 11:21:18", "content": "Yep, today may 3 submissions all failed.
", "votes": null, "replies": [] }, { "id": 591315, "author_name": "javiermzll", "author_url": "", "post_date": "08/03/2019 13:38:58", "content": "It's been for a couple of days for me, some working.
", "votes": null, "replies": [] }, { "id": 591340, "author_name": "purplejester", "author_url": "", "post_date": "08/03/2019 14:21:05", "content": "Would be great if the lost submissions could be compensated :)
", "votes": null, "replies": [] }, { "id": 591538, "author_name": "raimonds1993", "author_url": "", "post_date": "08/03/2019 21:55:01", "content": "That's happening also in other kernels competitions. Kaggle has probably some issues with GPUs.\nHope they'll manage to find a solution 😅
", "votes": null, "replies": [ { "id": 591725, "author_name": "purplejester", "author_url": "", "post_date": "08/04/2019 06:47:42", "content": "I believe that now most of the participants train on the GPU, even tree-based methods, as soon as many libraries support it :)
", "votes": null, "replies": [] } ] }, { "id": 591588, "author_name": "qinhui1999", "author_url": "", "post_date": "08/04/2019 01:06:45", "content": "Same problem. But I download the output of the failed kernel and test the FID score in my local pc, I got the right score ( 54.0 ). Hence it must be the Kaggle kernel ' bug.
", "votes": null, "replies": [ { "id": 591724, "author_name": "purplejester", "author_url": "", "post_date": "08/04/2019 06:45:28", "content": "Yeah, I've submitted 3 times without any luck, from the different kernels.
", "votes": null, "replies": [] } ] }, { "id": 591607, "author_name": "adiachen", "author_url": "", "post_date": "08/04/2019 02:20:41", "content": "Still can't submit my output files
", "votes": null, "replies": [] }, { "id": 591634, "author_name": "kanbac5", "author_url": "", "post_date": "08/04/2019 03:56:11", "content": "Yes, I have same problem...and there seems to be something wrong with Kaggle Kernel(because I can't now submit my old kernel that I could submit before)
", "votes": null, "replies": [] }, { "id": 591726, "author_name": "purplejester", "author_url": "", "post_date": "08/04/2019 06:48:45", "content": "So then we can only wait :|
", "votes": null, "replies": [] }, { "id": 593066, "author_name": "titart", "author_url": "", "post_date": "08/06/2019 06:49:27", "content": "Try to reduce the size of logs. My kernel failed every run without any output errors when I printed training score on every 50th iteration. It became OK when I started to print score on every epoch.
", "votes": null, "replies": [] } ], "raw_markdown_by_id": { "591185": "I submitted the results from two kernels with an archive of generated images but got the error, see the screenshot below.\n\n\n\nThe images are in JPEG format and submitted as a ZIP archive. The previous submissions were done without any issues, and I use the same snippet to generate the submission. However, this time I am getting the error, and it doesn't elaborate any details.\n\nAlso, see an example of the generated image from the archive. It is 64x64, 3 channels, i.e., meeting the requirements.\n\n\n\nDid anybody have a similar issue before?", "591236": "Yep, today may 3 submissions all failed.", "591315": "It's been for a couple of days for me, some working.", "591340": "Would be great if the lost submissions could be compensated :)", "591538": "That's happening also in other kernels competitions. Kaggle has probably some issues with GPUs.\nHope they'll manage to find a solution 😅", "591588": "Same problem. But I download the output of the failed kernel and test the FID score in my local pc, I got the right score ( 54.0 ). Hence it must be the Kaggle kernel ' bug.", "591607": "Still can't submit my output files", "591634": "Yes, I have same problem...and there seems to be something wrong with Kaggle Kernel(because I can't now submit my old kernel that I could submit before)", "591724": "Yeah, I've submitted 3 times without any luck, from the different kernels.", "591725": "I believe that now most of the participants train on the GPU, even tree-based methods, as soon as many libraries support it :)", "591726": "So then we can only wait :|", "593066": "Try to reduce the size of logs. My kernel failed every run without any output errors when I printed training score on every 50th iteration. It became OK when I started to print score on every epoch." }, "source": "meta" }