No, the issue is reported by intel at 2018-08-30-97. 2018-08-24_11-22-14 and 2018-09-04_20-18-01 are references to builds of StarlingX upstream at Wind River systems. The text of the original report says the issue is not present in intel build 2018-08-22-76
2018-08-24 approximates the state of git repos for intel build 2018-08-25-81, since the dump of git repo HEADs is not available from intel. The attached commit-diff.txt is the list of commits since 2018-08-24_11-22-14 up to 2018-09-04_20-18-01.
I'm starting to get confused by all the build numbers :/
No, the issue is reported by intel at 2018-08-30-97. 2018-08-24_11-22-14 and 2018-09-04_20-18-01 are references to builds of StarlingX upstream at Wind River systems. The text of the original report says the issue is not present in intel build 2018-08-22-76
2018-08-24 approximates the state of git repos for intel build 2018-08-25-81, since the dump of git repo HEADs is not available from intel. The attached commit-diff.txt is the list of commits since 2018-08-24_11-22-14 up to 2018-09- 04_20-18- 01.
I'm starting to get confused by all the build numbers :/