Allure reports loading forever

[KristofKuli]

Dear Support,

The generated Allure reports are more than 100MB in size and after successful publishing, we can't see them as it loads forever. Is there any size limitation for Allure? We have checked the network logs and this is what we can see:

ColumnNumber: 67893
​
fileName: "https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js"
​
lineNumber: 1
​
message: "u.value[0] is undefined"
​
name: "TypeError"
​
stack: "740/n</</</</<@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:67893\n740/p</u/</<@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:66894\n740/p</u/<@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:66999\ns@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:65692\npromise callback*a@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:65857\ns@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:65689\npromise callback*a@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:65857\ns@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:65689\npromise callback*a@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:65857\ns@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:65689\npromise callback*a@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:65857\ns@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:65689\npromise callback*a@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:65857\n740/a</<@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:65868\n740/a<@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:65635\n740/n</</<@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:67180\n@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:59951\n584/r</e.prototype.invokeMethod@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:56930\n584/r</e.prototype.onMessage@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:57647\n584/r</e/this._handleMessageReceived@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:60930\nEventListener.handleEvent*e@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:61175\n584/r<@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:61445\n584@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:64884\nr@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:76599\n740@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:67017\nr@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:76599\n@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:76967\n@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:76975\n@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:158\n@https://qameta.gallerycdn.vsassets.io/extensions/qameta/allure-azure-pipelines/1.0.6/1707134962806/dist/main.js:1:223\n"
​
toString: function i()​
<prototype>: Object { … }

[epszaw]

Hey there! Will investigate the problem and give you feedback as soon as possible!

[epszaw]

In new version (1.0.7) of the extension, the problem should be solved. Please, try the latest version

[KristofKuli]

Hi @epszaw,

We have tried with the latest version, but we are still receiving error.

[epszaw]

That's very interesting because it can't find any allure report attachment (which actually has been attached, hasn't it?). We can have problem with attachment size limit. As you said, your report is huge. Could you tell me the report file size? Could you generate it locally?

[KristofKuli]

Locally it works without issues. The allure-report folder is around 100-130 MB.

[epszaw]

Unfortunately, there is a size limit of 60mb for attachments in Azure DevOps, but the extension works with a single file report. I'll try to research another way to upload attachments as soon as possible, but the current extension, unfortunately, doesn't cover your case.

[epszaw]

Good news! I did the fix. It's available since version 1.1.0 (the latest one at this moment).
On these screenshots, you can see difference between my 100 tests report (it's only ~10mb):

And my 1000 tests report (divided on multiple chunks):

Hope the solution will solve your problem.

[KristofKuli]

Hi Konstantin,

So far it's working. We will keep testing it today and you let you know about the result on Monday.

[KristofKuli]

Hi Konstantin,

I can confirm that extension is working properly with version 1.1.0. Thank you for the quick help!

[epszaw]

Glad to hear that! No problem :)