Deploy issue after update from 2.1.2 to 2.1.3

[andidhouse]

Exact same system / template everything.
We never faced any problem with deploying on our system nor our template.

Now after upgrade from 2.1.2 to 2.1.3 and running:

hp bin/magento setup:static-content:deploy de_DE && php bin/magento setup:static-content:deploy

One error in the luma theme
One error in our custom theme

how can we debug this and why is there no headline of showing which theme is involved. You can just guess at the moment that 4 themes are deployed and the order is 1.2.3.4 or?

[andidhouse]

Deploy seems very buggy at the moment. When we run it several times errors occur in a totally different number on all! themes. no matter in production or developer mode.

@andidhouse can you share your opinion on 2.1.3 thus far. I'm reluctant to even bother testing after all the patching and workarounds I had to apply to get 2.1.2 live.

[andidhouse]

@jupiter01 shure:

In our opinion (tested today) 2.1.3 is not a big step forward but introduces new bugs. So i would recommend not to use it at the moment as only some bugs where "half-fixed" and again some new stuff is implemented which causes in our opinion again problems an new bugs.

We are still testing but for now it seems like the system has even more bugs like 2.1.2.

Thanks

[vkorotun]

@andidhouse You may try to run command with the following parameters:
bin/magento setup:static-content:deploy -j 0 -vvv
So with very verbose logging you may get more clarity on the file failed to deploy.

("-j 0" - will run your command in one thread)

[andidhouse]

@vkorotun here is the result

Screen one is the command:
php bin/magento setup:static-content:deploy -vvv

Screen two is the command:
php bin/magento setup:static-content:deploy de_DE -vvv

Both show one error - Screen one shows the error and screen two shown no error description?
So what kind of bug is this?

[guillaume-netapsys]

I'm getting the same kind of error using Redis as my cache system.
If I disable Redis and use classic cache system, everything seems to be back to normal.
So for the moment, I can't deploy with Redis, so it could be great to have more info or a patch to fix this issue.
Thank you.

[andidhouse]

jep @guillaume-netapsys think it is a redis problem.

@magento-team Can you pls check this now!

One more bug introduced in 2.1.3 - testing is very bad guys! You introduce more bugs in the versions then fixing them :-/.

[andidhouse]

@vkorotun can you pls test your 2.1.3 system using redis cache. Seems to be the problem.
I am really tired of finding bugs in new versions from stuff that worked before...

[guvra]

I can confirm that:

• the bug occurs when using redis as the cache backend
• the command stops crashing after adding the parameter --jobs=0 (or -j 0)

Working workaround:

bin/magento setup:static-content:deploy fr_FR --jobs=0

[andidhouse]

@vkorotun and now?

[andidhouse]

Are we left once again alone with this major bug from magento side? A solution published in any form in month is not acceptable at all for a bug like this.